Niches · Agent auth & delegated access
Get consent from a user who isn't at the agent's screen
Four or more companies' docs show a full fit.
What counts as done
The service returns a consent URL or starts a push or CIBA request instead of failing, the agent relays it, and after the user approves the same request resumes with a token within one further call, with no browser on the agent's host.
How agents ask for it: send me the link to approve access
, the agent is running in a container and needs me to log in
, ask the user to connect their account then carry on
Does the job 4
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Amazon Bedrock AgentCore Identity A Amazon Web Services, Inc. | GetResourceOauth2Token returns authorizationUrl to stream to the caller, the agent calls again with the same session after consent, and session binding checks the consenting user at an HTTPS callback. A first-hand account reports it working for per-user Strava access. source |
| Keycard D Keycard Labs, Inc. | With authorization_url set, a run with a missing grant pauses through deferred tool approval carrying the URL to relay, and resume_results continues the same run once the user approves. Absent-user jobs instead need a prior grant and an impersonation policy. source |
| Nango B Nango Inc | With nango_create_connection enabled, a call to an unconnected integration fails with an error naming that tool, which returns a connect or reconnect link to relay; once the user authorises, the session's tools run on the new credentials without a new session. source |
| Vercel Connect BB Vercel Inc. | startAuthorization returns a consent URL valid 15 minutes to 24 hours, with deviceCode for a headless process and a webhook when the flow finishes; the agent then requests the token again. source |
Does the job, with a limit 6
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. | Embedded user authorization lets the application build the authorize URL and send it to the person anywhere, with outcome returned to its redirect_uri. No CIBA, push or URL elicitation, and the gateway path opens a browser on the client. source |
| Arcade.dev B Arcade AI, Inc. | The authorize call returns a short-link URL to relay, /v1/auth/status waits for completion and the tool then runs, with a user verifier checking who consented. A first-hand account hit an authorisation error following the LangChain interrupt guide, fixed in the docs a day later. source |
| Auth0 for AI Agents (Token Vault) BB Okta, Inc. | CIBA starts a Guardian push or email approval from the backend and the agent polls /token until approved. CIBA is unavailable on Free and email is a paid add-on; connecting a new third-party account still runs through a browser. source |
| Descope Agentic Identity Hub A Descope, Inc. | The Agent Auth SDK has a CibaProvider for push approval, get_connect_url to relay and wait_for_connection to poll until the user finishes. The README says pip and npm install, but both registries return not found, so it installs from GitHub. source |
| Scalekit AgentKit BB ScaleKit, Inc. | get_authorization_link returns a one-time URL to relay, and the agent polls the account or waits for the ACTIVE webhook before calling the tool. Links last five minutes by default, the expiry blocker this use case names. source |
| WorkOS Pipes and Agents B WorkOS, Inc. | A missing grant returns not_installed or needs_reauthorization, and get-authorize-url builds a URL the agent can relay; the next token call then succeeds. The URL is a separate call, no push or CIBA exists, and WorkOS's own MCP server accepts no API key for headless runs. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Clerk MCP server B Clerk, Inc. | Sign-in opens a browser from the AI client; no relayable consent request, push or CIBA is offered. source |
| Cloudflare Workers OAuth Provider A Cloudflare, Inc. | Consent runs in the developer's own /authorize handler in the user's browser; no relayable request, elicitation, push or CIBA is provided. source |
| Microsoft Entra Agent ID BB Microsoft Corporation | Agents are excluded from interactive flows, and consent for agent identities is granted by admins or inherited from the blueprint, not relayed to a user at runtime; no CIBA is documented here. source |
| Stytch Connected Apps B Twilio Inc. | Consent runs in the browser during the authorisation code flow, explicitly for loopback and custom-scheme clients; no relayable request, push or CIBA is offered. source |
What stops agents finishing
- MCP endpoint is OAuth-only and accepts no API key, so a headless agent cannot start
- consent URL can be completed by a different user than the one who asked
- consent link expires before the user sees it
Around it
Before: agent-auth.connect-user-account. After: human-in-the-loop.approve-action.
Where this comes from
Weight 11 of 100 in Agent auth & delegated access: 5 of 33 accounts (headless WorkOS benchmark, Claude Code containers, Cloudflare reauth, AgentCore consent URL); listing notes on AgentCore, Arcade, Scalekit and Vercel describe the same step
The same as data: /api/v1/use-cases/agent-auth.out-of-band-consent.json, or the MCP tool get_use_case with id agent-auth.out-of-band-consent. 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.