Niches · Agent auth & delegated access

Find out a scope was refused or a connection is missing, and recover

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
14companies, fit with a limit
15companies carry the tag
9share of the category's work
4first-hand accounts

What counts as done

The call that needs the missing scope returns a typed error naming the scope or the connection state and a reconnect URL, never a silent empty result or a swallowed exception, and the agent stops retrying after one such answer.

How agents ask for it: why can't the agent see my calendar, which permissions did I grant, reconnect with write access

Does the job, with a limit 14

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.

ListingWhy
Aembit BB
Aembit, Inc.
Consent failures come back to redirect_uri as access_denied with a named description, including declined consent. No per-call error naming a missing scope with a reconnect URL is documented. source
Amazon Bedrock AgentCore Identity A
Amazon Web Services, Inc.
Gateway answers 403 with error="insufficient_scope" and the scope for inbound calls. For outbound grants no typed refused-scope error is documented; the advice is to retry with forceAuthentication on a 401. source
Arcade.dev B
Arcade AI, Inc.
Authorization responses name the scopes and status, and a tool run that needed authorization is recorded as such. The docs show checking with authorize before execute; a typed missing-scope error from execute itself is not shown. source
Auth0 for AI Agents (Token Vault) BB
Okta, Inc.
The exchange returns granted scopes and a 401 when no connected account is found. Auth0 AI SDK issue 175, still open, reports Token Vault exchange errors swallowed inside the SDK, which this use case names as a blocker. source
Clerk MCP server B
Clerk, Inc.
whoami shows granted permissions and a tool returns a permission error when a scope or role is missing, but the fix is to sign out and reconnect, no reconnect URL is returned, and every connection asks for write scopes with no read-only set. source
Cloudflare Workers OAuth Provider A
Cloudflare, Inc.
Resource servers can answer 403 insufficient_scope naming every required scope, and 401 challenges point at the metadata. The handler must call insufficientScope itself, since requiredScopes is advertised, not enforced. source
Descope Agentic Identity Hub A
Descope, Inc.
Users may decline a scope when the MCP server allows it, and an unlinked account raises ConnectionAuthorizationRequired with a connect URL. No error naming a specific missing scope is documented; a tenant mismatch returns a plain 404 Token not found. source
Keycard D
Keycard Labs, Inc.
The token endpoint returns insufficient_authorization for a missing or revoked grant and access_denied for a policy refusal, and denials are readable in the Console. The SDK never throws, so an agent sees the error only if the server checks AccessContext. source
Microsoft Entra Agent ID BB
Microsoft Corporation
Entra returns named AADSTS errors, such as 82014 for interactive consent on an agent and 50013 for a wrong-audience assertion. No agent-specific missing-scope error with a reconnect URL is documented. source
Nango B
Nango Inc
A 403 such as a missing scope fails that tool only, and a 401 tells the agent the connection needs reconnecting; the reconnect link requests current scopes. The link comes from a separate meta-tool that is off by default, not in the error itself. source
Scalekit AgentKit BB
ScaleKit, Inc.
Users can clear optional scopes, and tool calls needing them fail with the app's own permission error, a 403 passed through. No Scalekit error names the missing scope or returns a reconnect link. source
Stytch Connected Apps B
Twilio Inc.
The consent page refuses scopes the user's roles cannot grant, and MCP servers answer 401 with resource metadata. No error naming a missing scope for a later call is documented; enforcement is left to the resource server. source
Vercel Connect BB
Vercel Inc.
Auth failures are typed: UserAuthorizationRequiredError, ConnectorInstallationRequiredError, NoValidTokenError and 403s naming the missing project link. No error that names a refused provider scope is documented. source
WorkOS Pipes and Agents B
WorkOS, Inc.
The token response lists granted scopes and missing_scopes and a typed needs_reauthorization error, so a refused scope is visible. The reconnect URL is not in that response; it needs a get-authorize-url call. source

What stops agents finishing

  • errors swallowed inside the SDK
  • rejection happens in the user's browser after redirect, invisible to the service
  • write scopes requested on every connection with no read-only option (Clerk MCP)

Around it

Before: agent-auth.connect-user-account. After: agent-auth.out-of-band-consent.

Where this comes from

Weight 9 of 100 in Agent auth & delegated access: 4 of 33 accounts (Auth0 swallowed errors, Arcade auth error, Nango CIMD dead end, Linear invalid client); buyer check 2 asks for it

The same as data: /api/v1/use-cases/agent-auth.refused-scope.json, or the MCP tool get_use_case with id agent-auth.refused-scope. Other jobs in this category: /api/v1/niches?category=agent-auth.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.