Arcade.dev vs WorkOS Pipes and Agents

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.

WorkOS Pipes and Agents

Agent identity with per-session revocation and token lifetimes set per blueprint. 21 incidents on the status page since 3 July 2026, several over an hour.

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}

WorkOS Pipes and Agents

1. Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token
2. Branch on active in the response and send the user to reconnect on needs_reauthorization
3. Wait for Retry-After on a 429, or back off with jitter when it's missing
4. Use lower-case provider slugs such as github or slack
5. Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry