Niches · Agent auth & delegated access
Keep an agent's tokens valid through a long or unattended run
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A run that spans at least two access-token lifetimes and two concurrent sessions completes with no re-consent and no 401 reaching the agent, and a refresh failure produces a typed reauth signal within one call.
How agents ask for it: why does the MCP connection expire every day
, keep the agent connected overnight
, refresh the token without asking me again
Does the job, with a limit 13
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Aembit BB Aembit, Inc. | The gateway refreshes upstream tokens per user, but the agent-to-gateway refresh token works once and relies on the MCP client refreshing; expiry shows as McpSessionExpiredOrRevoked in events, not as a typed reauth signal to the agent. source |
| Amazon Bedrock AgentCore Identity A Amazon Web Services, Inc. | Stored refresh tokens are used automatically and an expired refresh falls back to a new authorization URL. Nothing addresses concurrent sessions, and AWS warns returned tokens may be invalid, so the agent can still meet a 401 and retry with forceAuthentication. source |
| Arcade.dev B Arcade AI, Inc. | Provider configs carry a refresh_request, so Arcade refreshes for the tool, and a missing grant shows as status not completed with a URL. Rotation and two sessions refreshing at once are not covered in the docs read. source |
| Auth0 for AI Agents (Token Vault) BB Okta, Inc. | Auth0 refreshes the provider token from the vault on each exchange, but Token Vault does not support Auth0 refresh token rotation, and an open SDK issue says exchange errors are swallowed, so a failure may not arrive as a typed signal. source |
| Cloudflare Workers OAuth Provider A Cloudflare, Inc. | Refresh tokens rotate with the previous one valid until its replacement is used, and grants last 30 days by default. An open issue reports rotation state racy under concurrent refresh on KV, so two sessions refreshing together can break. source |
| Descope Agentic Identity Hub A Descope, Inc. | Descope refreshes vaulted tokens and the docs say to fetch on every tool run instead of caching; a missing connection raises a typed error with a connect URL. Concurrent sessions and rotation are not discussed. source |
| Keycard D Keycard Labs, Inc. | Credentials are exchanged fresh per call, grants show as refreshable, and an expired subject token pauses a Pydantic AI run with a sign-in URL. Refresh behaviour across two sessions and token lifetimes is not documented. source |
| Microsoft Entra Agent ID BB Microsoft Corporation | Autonomous agents mint tokens by client credentials whenever needed, and refresh_token is supported for background OBO work. No typed reauth signal for a failed refresh is described, and Microsoft calls hand-written exchanges error-prone. source |
| Nango B Nango Inc | Nango refreshes tokens before expiry, at least every 24 hours, and sends refresh-failure and recovery webhooks. Open issue 6136 reports GitHub App connections break about 8 hours after the first refresh because the rotated refresh token is never stored. source |
| Scalekit AgentKit BB ScaleKit, Inc. | Scalekit stores and refreshes tokens; an account that cannot refresh moves to EXPIRED and a connected_account.status_updated webhook fires. The next tool call still fails until the user reauthorises, and concurrent sessions are not discussed. source |
| Stytch Connected Apps B Twilio Inc. | offline_access yields refresh tokens; public clients rotate them with replay detection, confidential clients do not rotate. Two sessions sharing one public grant risk replay detection, and no reauth signal beyond a 401 is described. source |
| Vercel Connect BB Vercel Inc. | Connect holds the refresh token and the SDK refreshes cached tokens 30 seconds before expiry; a lost grant raises NoValidTokenError or UserAuthorizationRequiredError. Behaviour with two concurrent sessions is not described, and a provider-rejected cached token must be evicted by the caller. source |
| WorkOS Pipes and Agents B WorkOS, Inc. | Pipes refreshes OAuth tokens on each fetch and returns active false with needs_reauthorization when a grant breaks, a typed signal. Concurrent-session behaviour is not described, and on the inbound side an account shows Claude Code never refreshing AuthKit tokens. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Clerk MCP server B Clerk, Inc. | It keeps only its own Clerk sign-in, which the client stores; nothing in the docs covers refresh for long runs or other providers. source |
What stops agents finishing
- provider issues no refresh token (GitHub OAuth apps)
- refresh-token rotation with concurrent sessions invalidates the other session
- stored rotated refresh token never updated (Nango issue 6136)
- client does not call refresh on expiry, so the user reconnects daily
Around it
Before: agent-auth.connect-user-account. After: notifications.push.
Where this comes from
Weight 19 of 100 in Agent auth & delegated access: 9 of 33 accounts; Claude Code MCP issues alone carry four, with Cloudflare and Nango refresh bugs
The same as data: /api/v1/use-cases/agent-auth.keep-session-alive.json, or the MCP tool get_use_case with id agent-auth.keep-session-alive. Other jobs in this category: /api/v1/niches?category=agent-auth.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.