Head to head · OAuth for agents · October 2026 research run
Arcade.dev vs Nango
Nango scores 68 (B) on agent readiness against Arcade.dev's 66.5 (B), and leads in 3 of 7 scored categories. Arcade.dev leads on agent ergonomics. Both do oauth for agents.
Best auth and delegated access for AI agents · All 168 agent auth comparisons
Which one, for what
Best for A product whose agent acts in many users' SaaS accounts and wants the tools written and run for it, not only the tokens.
Ahead on
- Agent ergonomics, 86 against 74
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise
Nango B
Best for A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.
Ahead on
- Reliability, 78 against 63
- Maintenance & community, 90 against 76
- Transparency & trust, 77 against 71
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
Audit trail only on Enterprise, and logs kept 15 days on every plan
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability Nango +15
Arcade.dev 63
Atlassian Statuspage at status.arcade.dev with per-component history for the Engine API, Cloud API, Tools APIs and each provider integration (20). Three incidents from 3 August to 1 November, read from history.atom. On 29 October some tool authorisation links on Arcade Cloud returned a 502 for about five hours, later limited to a few MCP servers, while authorised tools kept running. On 6 and 7 October authorisation prompts hung in one client (Claude Cowork). On 7 October a Google authorisation report turned out to be a non-production environment. All partial, so minor only (20). The only rate limit with a number is 100 requests a minute on the audit-log API, nothing for the authorise or execute calls, per the 1 October check (5). Upstream rate limits come back as UpstreamRateLimitError with retry_after_ms and a documented wait-and-retry rule, but the OpenAPI file defines no 429 and no idempotency key, re-read on 1 November (8). Enterprise lists 24/7 SLA-backed support with no published uptime figure (5). The terms dated 15 July 2025 still call the service an early version under development, re-read on 1 November, so half marks for availability (5). 20 + 20 + 5 + 8 + 5 + 5 = 63.
Nango 78
Better Stack page at status.nango.dev with history, though it tracks one component, Nango Cloud Health (20). Three incidents in the 90 days from 3 August, read from the page's feed on 1 November 2026, all partial. Logs couldn't be written on 3 August from about 00:00 to 01:26 UTC, with function executions unaffected. The records database slowed from 12 September and was mitigated at 02:30 UTC on 14 September, with more than 1% of syncs failing on timeout and retrying, and its post-mortem followed on 23 September. On 2 October function executions (actions, syncs and webhooks) stopped from 17:22 to 17:54 UTC, while the API and auth weren't named. No outage of the whole service (20). Rate limits per plan, 200 requests a minute on Free, 1,000 on Pay-as-you-go and 2,000 with Growth (15). The limits page says to read the standard rate-limit headers before resuming but doesn't name them, and we found no idempotency guidance for actions (8). The pricing page lists SLAs under Enterprise with no published figure (5). Auth, proxy and agent sessions are sold as GA (10).
Maintenance & community Nango +14
Arcade.dev 76
arcade-mcp 1.17.1 on 29 October 2026, published to PyPI by the repository's release-on-version-change workflow, and self-hosted Arcade 1.11.4 on 28 October (30). In the last 90 days arcade-mcp moved to 1.15.2, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.17.0 and 1.17.1, and self-hosted Arcade shipped eleven dated releases from 1.9.5 (6 August) to 1.11.4 (20). Closed platform with a dated release-notes site, which replaced the docs changelog that stopped at 26 July 2026, a Discord community, and a GitHub repository where new issues are restricted. Issue reply times weren't re-read, since GitHub's pages answered 403 (10 of 15). The REST clients lag. arcadepy's newest tag is v1.10.0 of 6 November 2025 and @arcadeai/arcadejs's v2.4.1 of 21 April 2026, from clones on 1 November (8). CI workflows run on arcade-mcp, which supports Python 3.10 to 3.13 (8). 30 + 20 + 10 + 8 + 8 = 76.
Nango 90
Release v0.71.14 was tagged on 29 October 2026 and the changelog has entries up to 1 November (30). Twelve releases from v0.71.3 (3 August) to v0.71.14, and 14 dated changelog entries in October (20). Issue numbers have passed 7,000 with 31 open per the 1 October check, not re-read on 1 November because GitHub's pages refuse our reader (20). The Node and frontend SDKs move with each release, but there's no official SDK outside TypeScript (12). Monorepo with CI and current dependencies, with vulnerable dependencies bumped on 22 October (8).
Agent ergonomics Arcade.dev +12
Arcade.dev 86
Gateways expose a chosen subset of tools, and formatted_tools filters by toolkit with limit and offset, so context can be sized (20). limit and offset with user_id and provider_id filters on list endpoints, and the formatted_tools filter takes read_only, destructive and idempotent flags (20). RetryableToolError, ContextRequiredToolError and retry_after_ms tell an agent what to do next, though Arcade's own open issue 703 asks for more actionable messages (16). Each tool carries a behaviour block (read_only, destructive, idempotent, open_world) in the hosted API's schema, and arcade-mcp maps them to MCP's readOnlyHint, destructiveHint and idempotentHint, in the framework since February 2026, which the 1 October check missed. Retryable errors are marked as safe to retry, but REST writes take no idempotency key (15). Two required fields to authorise a tool, user_id and tool_name, and official SDKs in Python and TypeScript (15). 20 + 20 + 16 + 15 + 15 = 86.
Nango 74
An agent session serves only the tools for one tenant's tagged connections through its own MCP URL, with a proxy meta tool instead of hundreds of tool definitions (20). Records come back with cursors, and connections filter by tags and end user (20). A webhook fires when a token refresh fails and again on recovery, but we found no list of API error codes an agent can branch on (14). The proxy has a retries setting, and we found no idempotency keys for actions (10). Few required parameters, but the official server SDK is TypeScript only (10).
Transparency & trust Nango +6
Arcade.dev 71
Closed platform under terms that name Arcade AI, Inc. and California law, with the MIT arcade-mcp framework beside it (15). The Arcade Cloud page lists retention (logs and audit trails up to 1 year, training data up to 5 years) and AES-256 field encryption, but it says tool inputs and results become training data unless the organisation opts out, while the privacy policy of 10 September 2026 says content from connected third-party accounts isn't used to train models (15). No deprecation policy, and the terms say parts of the service may change or be removed with no stated notice (5). United States hosting is stated, and the privacy policy names 25 or more service providers as a partial list with the rest on request (12). The Arcade Cloud page and the privacy policy are per the 1 October check, not re-read on 1 November.
Nango 77
Source on GitHub under the Elastic License 2.0, which is readable but not OSI-approved and bars offering Nango as a hosted service (20). The docs state AES-256-GCM under AWS KMS envelope keys, soft deletion at once and hard deletion after 31 days, 15-day log retention, record payloads pruned after 30 days without an update and a GDPR DPA by default (25). Breaking changes are announced in the changelog with migration guides, and the Connection MCP server's deprecation on 14 December 2026 was posted on 6 October, but we found no deprecation policy with notice periods (8). The docs say tokens sit in PostgreSQL in AWS, but we didn't find a public subprocessor list outside the trust centre (10).
Score by category
| Category | Weight | Arcade.dev | Nango | Edge |
|---|---|---|---|---|
| Reliability | 16% | 63 | 78 | Nango +15 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 85 | Arcade.dev +2 |
| Agent ergonomics | 13% | 86 | 74 | Arcade.dev +12 |
| Security & auth | 14% | 71 | 71 | even |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 90 | Nango +14 |
| Transparency & trust | 7% | 71 | 77 | Nango +6 |
| Negative events | ≤15 | -7 | -8 | |
| Total | B 66.5/100 | B 68/100 |
Facts side by side
| Fact | Arcade.dev | Nango |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Arcade.dev | Nango |
| Hosted endpoint | https://api.arcade.dev | https://api.nango.dev |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (arcade-mcp framework and SDKs), platform closed | Elastic License 2.0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-29 | 2026-10-29 |
| Terms last updated | 2025-07-15 | no date given |
| Privacy policy last updated | 2026-09-10 | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 1k stars, 125k npm/wk, 70k PyPI/wk | 469k npm/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Nango higher.
| Reviewer | Arcade.dev | Nango |
|---|---|---|
| BuoyAutonomous onboarding tester | 3/5 Three browser steps, then a consent link per user | 4/5 Shared apps keep it to three steps |
| WardenSecurity auditor | 2/5 One project key can speak for every user | 3/5 A 9.2 in the runner, disclosed by someone else |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Arcade.dev
Consent flow, token storage and refresh, and tool execution in one service, so the model never holds a provider token. The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise, and October's self-hosted releases fixed several access-control flaws without an advisory.
Nango
Nango handles OAuth, API keys and token refresh for 1,000+ APIs and serves per-tenant agent sessions as MCP servers, with scoped API keys and public per-unit prices. The audit trail is Enterprise-only, logs are kept 15 days, and webhook verification changes in September and October 2026 took effect the day they were announced.
Before you call either
Arcade.dev
- Call
POST /v1/tools/authorizefirst and send the user the returned URL when the status isn't completed - Pass a stable user ID from your own database as user_id, never a shared value
- Read retry_after_ms on an UpstreamRateLimitError and wait that long before calling again
- Register your own OAuth app and a custom user verifier before real users sign in, because the default apps only accept members of your Arcade project
- Revoke a user's access with
DELETE /v1/admin/user_connections/{id} - Filter formatted_tools on
read_onlyordestructivebefore handing a toolkit to an agent that shouldn't write
Nango
- Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
- Leave
nango_proxyoff when a session relies on deny lists, because the proxy reaches any endpoint of a connected integration - Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
- Read the rate-limit headers on a 429 and wait for the reset before resuming
- Set webhook secrets on Gmail, GitHub App, Affinity, Fillout, ShipStation and Salesforce integrations, or their webhooks are rejected
Questions
Which is better for AI agents, Arcade.dev or Nango?
Nango scores 68 (B) on agent readiness against Arcade.dev's 66.5 (B), and leads in 3 of 7 scored categories. Arcade.dev leads on agent ergonomics.
Do Arcade.dev and Nango need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Arcade.dev and Nango without installing anything?
Yes. Arcade.dev has a hosted endpoint at https://api.arcade.dev and Nango at https://api.nango.dev.
Other comparisons with Arcade.dev or Nango
- Aembit vs Arcade.dev
- Aembit vs Nango
- Amazon Bedrock AgentCore Identity vs Arcade.dev
- Amazon Bedrock AgentCore Identity vs Nango
- Arcade.dev vs Auth0 for AI Agents (Token Vault)
- Arcade.dev vs Clerk MCP server
- Arcade.dev vs Cloudflare Workers OAuth Provider
- Arcade.dev vs Descope Agentic Identity Hub
- Arcade.dev vs Keycard
- Arcade.dev vs Microsoft Entra Agent ID
- Arcade.dev vs Proof MCP
- Arcade.dev vs Scalekit AgentKit
- Arcade.dev vs Stytch Connected Apps
- Arcade.dev vs Vercel Connect
- Arcade.dev vs WorkOS Pipes and Agents
- Auth0 for AI Agents (Token Vault) vs Nango
- Clerk MCP server vs Nango
- Cloudflare Workers OAuth Provider vs Nango
- Descope Agentic Identity Hub vs Nango
- Keycard vs Nango
- Microsoft Entra Agent ID vs Nango
- Nango vs Proof MCP
- Nango vs Scalekit AgentKit
- Nango vs Stytch Connected Apps
- Nango vs Vercel Connect
- Nango vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/arcade-vs-nango.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/arcade.json·/api/v1/tools/nango.json - From a terminal
anchor compare arcade nango(the CLI) - Over MCP
compare_tools {"a": "arcade", "b": "nango"}at/mcp, no key