Arcade.dev vs Descope Agentic Identity Hub

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.

Descope Agentic Identity Hub

Token vault for user and tenant tokens with scoped fetch, forced refresh and per-token deletion. No tool catalogue, so you write every provider call yourself.

Arcade.dev

1. Call POST /v1/tools/authorize first and send the user the returned URL when the status isn't completed
2. Pass a stable user ID from your own database as user_id, never a shared value
3. Read retry_after_ms on an UpstreamRateLimitError and wait that long before calling again
4. 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
5. Revoke a user's access with DELETE /v1/admin/user_connections/{id}

Descope Agentic Identity Hub

1. Sign the agent in as its own OAuth client and let Policies scope it, instead of shipping a management key
2. Treat a 404 from the token endpoint as a missing connection and send the user to the connect URL
3. Back off for the full window on a 429, 60 seconds for most management endpoints
4. Ask for a tenant token, not a user token, for organisation-wide API keys
5. Budget monthly active tokens, since every token fetched and used counts once a month