Arcade.dev vs Scalekit AgentKit

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.

Scalekit AgentKit

500+ connectors, including remote MCP servers over OAuth 2.1 with DCR. No rate limits or idempotency documented for Scalekit's own API.

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}

Scalekit AgentKit

1. Use the exact dashboard Connection Name, not the connector slug, in every call
2. Call POST /api/v1/tools:search with top_k instead of listing every tool
3. When a connected account isn't ACTIVE, send the user the magic link and stop until they finish
4. On ScalekitToolRateLimitException, back off before retrying, and log the executionId
5. Mint a fresh virtual MCP session token per user per run and let it expire