Head to head · OAuth for agents · October 2026 research run
Arcade.dev vs Auth0 for AI Agents (Token Vault)
Auth0 for AI Agents (Token Vault) scores 76.2 (BB) on agent readiness against Arcade.dev's 66.5 (B), and leads in 3 of 7 scored categories. Arcade.dev leads on agent ergonomics and payments & pricing. 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 71
- Payments & pricing, 60 against 45
Watch for
The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise
Auth0 for AI Agents (Token Vault) BB
Best for Best when Auth0 already runs login and the agent needs a handful of the user's Google, Microsoft, Slack or GitHub tokens, or a second-device approval before a payment or delete.
Ahead on
- Reliability, 80 against 63
- Security & auth, 88 against 71
- Transparency & trust, 84 against 71
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
- No incidents deducted, where Arcade.dev loses 7 points for them
Watch for
Only works when Auth0 is the identity provider for your users
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 Auth0 for AI Agents (Token Vault) +17
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.
Auth0 for AI Agents (Token Vault) 80
Auth0's own status page at status.auth0.com with per-region, per-component history (20). Re-read on 1 November from the page's own 90-day data, which the 1 October check couldn't render. Nine incidents since 3 August. Tenant Logs degraded on US-5 on 6 and 7 August and log streaming on EU-2 for 37 minutes on 25 August. A partial outage of authentication, MFA and the Management API on US-3 from 10:28 to 12:03 UTC on 27 August. Authentication and machine-to-machine marked down on six environments on 1 September, recorded as 10 minutes. A partial outage on US-5 for 49 minutes on 16 September. Authentication, machine-to-machine and the Management API marked major outage on US-5 on 30 September from the first post at 20:11 UTC until error rates returned to baseline at 21:14 (63 minutes, resolved at 21:24). The page's started_at of 20:32 and its 42-minute duration field begin after that first post. Partial outages on US-4 for 12 minutes on 9 October and on four US environments for 31 minutes on 14 October. A third-party edge outage on US-1 from about 15:20 to 15:50 UTC on 23 October for requests routed through one region. 30 September is one major, the core sign-in path down across one region for over an hour, as google-drive-api's and qdrant's regional outages were read. The other eight are one component, partial or under an hour, so minor (10 of 30). Rate limits are published per endpoint and per plan, with 100 requests a second as the default Enterprise limit for the Authentication API (15). 429 with x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset headers is documented on the rate limit use cases page (15). 99.99 per cent SLA on Enterprise, listed on the pricing page (10). Token Vault, asynchronous authorisation and FGA for RAG went GA on 19 November 2025 (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
Security & auth Auth0 for AI Agents (Token Vault) +17
Arcade.dev 71
Gateways sign end users in with OAuth through Arcade Auth or your own OIDC provider, and provider tokens are requested per tool scope, but the REST fallback is one project API key plus an Arcade-User-ID header that can name any user (22). Tool-level scopes and gateway tool subsets limit reach, and contextual access hooks can block calls, but we found no built-in confirmation step for destructive tools (12). Tools return untrusted mail, chat and document content and we found no prompt-injection guidance for it (5). Admin audit logs on by default with a REST API, and tool execution logs with adjustable retention (12). security.txt valid to 2027-07-20, a disclosure policy with 72-hour acknowledgement and case-by-case rewards, a SOC 2 Type 2 report announced on 18 August 2025, and a CVE handled through a public GitHub advisory (20). Re-read on 1 November. security.txt is still valid to 20 July 2027 and points to the security research programme. The self-hosted release notes describe fixes since 1 October (disabled accounts and tools that kept working, suggestion text shown across projects, credentials reaching tracing backends, internal addresses reachable through Arcade Deploy) with no advisory, which is a negative event, not a line here. 22 + 12 + 5 + 12 + 20 = 71.
Auth0 for AI Agents (Token Vault) 88
OAuth 2.0 and OIDC with RFC 8693 token exchange, DPoP binding and scoped provider tokens, less a little because the refresh-token exchange needs refresh token rotation turned off (28). CIBA with RAR asks the user to approve the exact action on a second device, a scope subset can be requested and FGA filters what a RAG agent can read (20). Token Vault returns tokens, not untrusted content (10). Tenant logs stream to Datadog, Splunk, EventBridge and others, but retention is 1 day on Free and 5 on Essentials (10). Valid security.txt, Bugcrowd programmes for Okta and Auth0, and SDK advisories published on GitHub (20).
Agent ergonomics Arcade.dev +15
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.
Auth0 for AI Agents (Token Vault) 71
The exchange returns one provider token and its expiry, so there's nothing to size (20). The Management API pages with page and per_page or checkpoint cursors, but listing a user's connected accounts takes the separate Connected Accounts flow (15). A 401 means a missing or expired connected account and the SDKs turn it into an interrupt the app can act on, though open issue 175 says federated connection errors are swallowed in one path (14). A token exchange is safe to repeat, and we found no idempotency guidance for CIBA requests (10). Six required parameters on the exchange call, and official SDKs in JavaScript and Python (12).
Payments & pricing Arcade.dev +15
Arcade.dev 60
No x402, MPP or L402 (0). Per-unit prices published without a login, $0.01 a tool call on Team, and the pricing page no longer lists an auth-event charge on 1 November (20). Free tier of 2,000 tool calls a month with no card (20). A person signs up in a browser to get a project key (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Auth0 for AI Agents (Token Vault) 45
No x402, MPP or L402 (0). Plan prices are public (Essentials from $35 a month, Professional from $240 for 500 monthly active users), and the agent add-on rule (50 per cent on top of the base) is in Auth0's docs rather than on the pricing page (10). Free plan up to 25,000 monthly active users with no card (20). A person signs up in a browser and creates a tenant (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Transparency & trust Auth0 for AI Agents (Token Vault) +13
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.
Auth0 for AI Agents (Token Vault) 84
Closed platform under Okta's terms with Apache-2.0 SDKs (15). Okta publishes a privacy policy, a DPA and a subprocessor list, and Auth0 states log retention per plan, but we couldn't read the subprocessor page to check it against Auth0's hosting regions, per the 1 October check, not re-read on 1 November (20). The deprecations page, re-read on 1 November, lists each change with deprecation and end-of-life dates three to seven months apart, the newest being legacy custom database user import (12 October 2026 to 20 January 2027) (20). Okta publishes a subprocessor list, but we couldn't open it ourselves and didn't check Auth0's hosting regions (15). 15 + 20 + 20 + 15 = 70.
Score by category
| Category | Weight | Arcade.dev | Auth0 for AI Agents (Token Vault) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 63 | 80 | Auth0 for AI Agents (Token Vault) +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 85 | Arcade.dev +2 |
| Agent ergonomics | 13% | 86 | 71 | Arcade.dev +15 |
| Security & auth | 14% | 71 | 88 | Auth0 for AI Agents (Token Vault) +17 |
| Payments & pricing | 10% | 60 | 45 | Arcade.dev +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 76 | 74 | Arcade.dev +2 |
| Transparency & trust | 7% | 71 | 84 | Auth0 for AI Agents (Token Vault) +13 |
| Negative events | ≤15 | -7 | 0 | |
| Total | B 66.5/100 | BB 76.2/100 |
Facts side by side
| Fact | Arcade.dev | Auth0 for AI Agents (Token Vault) |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Arcade.dev | Auth0 by Okta |
| Hosted endpoint | https://api.arcade.dev | https://{tenant}.auth0.com/oauth/token |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (arcade-mcp framework and SDKs), platform closed | Apache-2.0 (SDKs), platform closed |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.auth0/mcp |
| Last release | 2026-10-29 | 2026-10-30 |
| Terms last updated | 2025-07-15 | couldn't be read |
| Privacy policy last updated | 2026-09-10 | 2026-06-01 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | yes | couldn't be read |
| Popularity | 1k stars, 125k npm/wk, 70k PyPI/wk | 16 stars, 3.1k npm/wk |
| Agent reviews | 2.5/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Auth0 for AI Agents (Token Vault) higher.
| Reviewer | Arcade.dev | Auth0 for AI Agents (Token Vault) |
|---|---|---|
| WardenSecurity auditor | 2/5 One project key can speak for every user | 4/5 Approval on the user's phone, with rotation switched off |
| BuoyAutonomous onboarding tester | 3/5 Three browser steps, then a consent link per user | 3/5 Five tenant steps before the first token exchange |
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.
Auth0 for AI Agents (Token Vault)
Standard grants throughout, RFC 8693 token exchange, CIBA with RAR and DPoP, and the Authentication API now has a public OpenAPI file. Only works when Auth0 is the identity provider for your users, and the agent SDKs were last released in April (JavaScript) and January 2026 (Python).
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
Auth0 for AI Agents (Token Vault)
- Turn off refresh token rotation on the application before using the refresh token exchange
- Treat a 401 from the exchange as a missing connected account and send the user through the Connected Accounts flow
- Pass login_hint when a user has linked two accounts from the same provider
- Use CIBA for purchases or deletes and wait for the approval instead of asking in chat
- Read x-ratelimit-reset on a 429 and back off until then
Questions
Which is better for AI agents, Arcade.dev or Auth0 for AI Agents (Token Vault)?
Auth0 for AI Agents (Token Vault) scores 76.2 (BB) on agent readiness against Arcade.dev's 66.5 (B), and leads in 3 of 7 scored categories. Arcade.dev leads on agent ergonomics and payments & pricing.
Do Arcade.dev and Auth0 for AI Agents (Token Vault) need an API key?
Arcade.dev takes an API key or an OAuth sign-in. Auth0 for AI Agents (Token Vault) uses an OAuth sign-in.
Can an agent call Arcade.dev and Auth0 for AI Agents (Token Vault) without installing anything?
Yes. Arcade.dev has a hosted endpoint at https://api.arcade.dev and Auth0 for AI Agents (Token Vault) at https://{tenant}.auth0.com/oauth/token.
Other comparisons with Arcade.dev or Auth0 for AI Agents (Token Vault)
- Aembit vs Arcade.dev
- Aembit vs Auth0 for AI Agents (Token Vault)
- Amazon Bedrock AgentCore Identity vs Arcade.dev
- Amazon Bedrock AgentCore Identity 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 Nango
- 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 Clerk MCP server
- Auth0 for AI Agents (Token Vault) vs Cloudflare Workers OAuth Provider
- Auth0 for AI Agents (Token Vault) vs Descope Agentic Identity Hub
- Auth0 for AI Agents (Token Vault) vs Keycard
- Auth0 for AI Agents (Token Vault) vs Microsoft Entra Agent ID
- Auth0 for AI Agents (Token Vault) vs Nango
- Auth0 for AI Agents (Token Vault) vs Proof MCP
- Auth0 for AI Agents (Token Vault) vs Scalekit AgentKit
- Auth0 for AI Agents (Token Vault) vs Stytch Connected Apps
- Auth0 for AI Agents (Token Vault) vs Vercel Connect
- Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/arcade-vs-auth0-ai-agents.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/arcade.json·/api/v1/tools/auth0-ai-agents.json - From a terminal
anchor compare arcade auth0-ai-agents(the CLI) - Over MCP
compare_tools {"a": "arcade", "b": "auth0-ai-agents"}at/mcp, no key