Arcade
Arcade.dev is the MCP runtime for production AI agent deployments. The Arcade Engine — a hosted or self-hostable API surface — handles OAuth user authorization, manages user tokens, and exposes 7,000+ pre-built integrations as Model Context Protocol tools that agent frameworks like LangChain, OpenAI Agents, CrewAI, AG2, Google ADK, Vercel AI, Mastra, and TanStack AI can call. This profile catalogs the public Arcade Engine API (39 endpoints across Admin, Authorization, Tools, LLM, Operations, Hooks, Gateways, and Plugins), the ArcadeAI GitHub org's SDKs, the arcade-mcp framework, and the public schemas repo.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Arcade the way a machine reads it — 136 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Arcade scores 57.3/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Arcade
Each block below is one kind of artifact we hold for Arcade. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Arcade Public Schemas
The ArcadeAI/schemas repo on GitHub publishes versioned JSON Schemas for the Arcade engine configuration (1.0 and 2.0) and the worker HTTP contracts (1.0) — tool_definition, exe...
Arcade MCP Framework
The arcade-mcp open-source Python framework — "MCP Server Framework and Tool Development library for building custom capabilities into agents." Provides the `arcade` CLI (login,...
Arcade Integration Catalog
The Arcade integration catalog — 145 MCP servers across Arcade Optimized, Arcade Unoptimized, Verified, Community, and Auth Provider designations, with 37 additional "Coming Soo...
Arcade Admin API
The Admin API from Arcade — 14 operation(s) for admin.
Arcade Authorization API
The Authorization API from Arcade — 4 operation(s) for authorization.
Arcade Gateways API
The Gateways API from Arcade — 3 operation(s) for gateways.
Arcade Hooks API
The Hooks API from Arcade — 3 operation(s) for hooks.
Arcade LLM API
The LLM API from Arcade — 1 operation(s) for llm.
Arcade Operations API
The Operations API from Arcade — 3 operation(s) for operations.
Arcade Plugins API
The Plugins API from Arcade — 2 operation(s) for plugins.
Arcade Tools API
The Tools API from Arcade — 9 operation(s) for tools.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Arcade API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Arcade Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Arcade Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Arcade Finops
FINOPSFeatures 11
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
MCP Runtime
Hosted and self-hostable Model Context Protocol runtime that turns tool definitions into multi-user, authorized invocations for agents.
Managed OAuth Authorization
Built-in OAuth and identity-provider flows across 30+ named auth providers plus a generic OAuth 2.0 provider; per-user tokens managed without service-account workarounds.
Tool Catalog
145 MCP servers across Arcade Optimized, Unoptimized, Verified, Community, and Auth Provider designations, with 37 more 'Coming Soon'.
Agent-Framework Integrations
First-class adapters for LangChain, OpenAI Agents, CrewAI, AG2, Google ADK, Vercel AI, Mastra, and TanStack AI.
Evaluations
`arcade evals` CLI runs scripted tool-calling evals to gate releases on behavior, not just compile-time checks.
Observability
Per-execution logs across the Engine plus dashboards; audit logs and compliance reporting are part of the Enterprise tier.
Hooks and Plugins
Pre- and post-call hooks plus pluggable verifiers and policy modules under /v1/hooks and /v1/plugins.
Custom User Verifiers
Customer-owned verification flows (e.g. Stytch, Supabase) gating tool execution via /v1/auth/validate_custom_verifier.
Scheduled Tools
Tools can be registered to fire on a schedule via /v1/scheduled_tools instead of synchronously from an agent.
Deployment Flexibility
Cloud, VPC, on-premises, or air-gapped — explicitly called out on the homepage.
Arcade Registry (beta)
Marketplace for publishing and monetizing agent-ready tools.
Scroll within the panel for all 11 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Arcade Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Arcade API Rules
SPECTRALArcade API Rules
SPECTRALJSON Schema 15
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Arcade Engine AuthProviderResponse
JSON SCHEMAArcade Engine AuthorizationResponse
JSON SCHEMAArcade Engine AuthorizeToolRequest
JSON SCHEMAArcade Engine ExecuteToolRequest
JSON SCHEMAArcade Engine ExecuteToolResponse
JSON SCHEMAArcade Engine GatewayResponse
JSON SCHEMAArcade Engine HookResponse
JSON SCHEMAArcade Engine PluginResponse
JSON SCHEMAArcade Engine SecretResponse
JSON SCHEMAArcade Engine ToolExecutionDetailResponse
JSON SCHEMAArcade Engine ToolResponse
JSON SCHEMAArcade Engine WorkerResponse
JSON SCHEMAArcade Execute Tool Request
JSON SCHEMAArcade Execute Tool Response
JSON SCHEMAArcade Tool Definition
JSON SCHEMAScroll within the panel for all 15 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Arcade Engine Auth Provider Response Structure
JSON STRUCTUREArcade Engine Authorization Response Structure
JSON STRUCTUREArcade Engine Authorize Tool Request Structure
JSON STRUCTUREArcade Engine Execute Tool Request Structure
JSON STRUCTUREArcade Engine Execute Tool Response Structure
JSON STRUCTUREArcade Engine Gateway Response Structure
JSON STRUCTUREArcade Engine Hook Response Structure
JSON STRUCTUREArcade Engine Plugin Response Structure
JSON STRUCTUREArcade Engine Secret Response Structure
JSON STRUCTUREArcade Engine Tool Execution Detail Structure
JSON STRUCTUREArcade Engine Tool Response Structure
JSON STRUCTUREArcade Engine Worker Response Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 56
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 56 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Multi-User AI Assistant
Agents that act on behalf of distinct end users — Gmail/Calendar/Slack/Salesforce assistants — without shared service credentials.
Production Agent Deployment
Moving agents from prototype to production with governed OAuth, evals, and observability per the May 2026 CISO governance post.
Enterprise MCP Gateway
An ingress in front of one or more workers within a project applying routing, headers, and policies.
Agent SRE
On-call reliability and runbook automation per Arcade's 'AI SRE with Claude Code' blog series.
Sales and Productivity Automation
Multi-step workflows across Salesforce, HubSpot, Attio, Slack, Linear, Jira, Asana, ClickUp, Notion, Google Workspace, and Microsoft Office.
Voice and Chat Assistants
WhatsApp / Telegram / Slack assistants powered by the toolkits and the Arcade Engine.
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
LangChain
First-class LangChain integration; partnership extended via LangSmith Fleet announcement on 2026-04-07.
OpenAI Agents
Python adapter via openai-agents-arcade for using Arcade tools inside the OpenAI Agents SDK.
CrewAI
Documented framework integration in docs.arcade.dev.
AG2
Framework support added in the 2026-04-10 changelog.
Google ADK
Adapter via google-adk-arcade Python library.
Vercel AI
arcade-vercel-ai-template demonstrating Arcade tools inside Vercel AI SDK chatbots.
Mastra
Documented framework integration.
TanStack AI
Documented framework integration.
Anthropic Claude Code
Multiple Claude Code routines and on-call workflows shipped from the Arcade blog through April–May 2026.
Auth Providers
Asana, Atlassian, Discord, Dropbox, GitHub, Google, HubSpot, Linear, LinkedIn, Microsoft, Notion, Reddit, Slack, Spotify, Twitch, X, Zoom, Airtable, Attio, Calendly, ClickUp, Fi...
Scroll within the panel for all 10 ·
Solutions 5
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Cloud Deployment
Arcade-hosted MCP servers, metered on the Growth plan at $0.05 per server-hour.
VPC Deployment
Deploy the Engine inside the customer's VPC — called out on the homepage as a supported topology.
On-Premises Deployment
Self-hosted Engine and workers for regulated environments.
Air-Gapped Deployment
Disconnected deployments for the highest-control environments.
Startup Program
Custom pricing for companies under 100 employees, nonprofits, and educational institutions via [email protected].
Resources
Every other property we hold for Arcade — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/arcade · machine-readable index on apis.io