{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/agent-auth.connect-user-account/",
    "json": "https://www.anchorterminal.com/niches/agent-auth.connect-user-account/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/agent-auth.connect-user-account/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/agent-auth.connect-user-account/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 10 | 16 | 25 | 12 |\n\n## What counts as done\n\nAfter one consent, the agent gets a valid token or a proxied call for that user and provider, bound to the right user ID, with the granted scopes returned, and the first API call succeeds.\n\nMeasured, for our own tests: the first API call succeeds within 2 calls of the consent completing.\n\nHow agents ask for it: connect my Gmail so the agent can read it; let the agent post to our Slack as me; give each customer's agent access to their HubSpot; link my GitHub account\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **WorkOS Pipes and Agents (WorkOS, Inc.)**: After the user connects through the authorize URL or Pipes widget, POST /data-integrations/{slug}/token with user_id returns active, a refreshed access token, its scopes and missing_scopes. Custom OAuth credentials and custom providers are supported.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Aembit (Aembit, Inc.)**: MCP User-Based Access Token stores and refreshes each user's tokens and proxies calls through the MCP Identity Gateway, keyed to the IdP-verified user. Covers MCP servers only, no granted-scope list is returned, and the managed gateway is set up through Aembit.\n- **Amazon Bedrock AgentCore Identity (Amazon Web Services, Inc.)**: GetResourceOauth2Token returns the user's token for built-in or custom OAuth providers after consent. The ForUserId path takes an unverified user string, granted scopes are not returned, and AWS says a returned token may already be revoked.\n- **Arcade.dev (Arcade AI, Inc.)**: tools.authorize returns status, url, scopes and user_id, then the tool runs with only user_id. Arcade's default OAuth apps accept only members of your Arcade project, so real users need your own OAuth app and a custom user verifier first.\n- **Auth0 for AI Agents (Token Vault) (Okta, Inc.)**: After the Connected Accounts flow, a Token Vault exchange returns the provider access token with its scopes and expiry for that Auth0 user. Free allows 2 Token Vault connections and Essentials 3 without the add-on, and Auth0 must be the identity provider.\n- **Descope Agentic Identity Hub (Descope, Inc.)**: Connections vault each user's provider tokens and the agent fetches them with that user's own access token under policy, or gets ConnectionAuthorizationRequired with a connect URL. The provider token is handed to the agent, and the Agent Auth SDK is still not on PyPI or npm.\n- **Keycard (Keycard Labs, Inc.)**: A tool exchanges the user's Keycard token for a short-lived upstream token on every call, and grants record the approved scopes per provider. A failed exchange lands on AccessContext rather than raising, so code that skips has_errors() calls on with nothing; sign-up is by request during Early Access.\n- **Microsoft Entra Agent ID (Microsoft Corporation)**: An agent gets user-delegated tokens through the OBO flow for Microsoft Graph, Azure and APIs registered in Entra. There is no store of third-party grants such as Gmail or Slack, and agent identities cannot run interactive consent themselves (AADSTS82014).\n- **Nango (Nango Inc)**: A connect session links the user's account, and an agent session exposes that tenant's connections as an MCP server through the proxy, so the agent never sees raw credentials; a first-hand account reports a year of stable use. Free stops at 10 connections.\n- **Scalekit AgentKit (ScaleKit, Inc.)**: An authorization link activates the user's connected account, then tools run with identifier plus connection name across 672 connectors. User verification starts at None, where anyone holding the link activates the account, so a custom verifier is needed before real users.\n- **Vercel Connect (Vercel Inc.)**: getToken with a user subject returns a short-lived provider token, and UserAuthorizationRequiredError leads to startAuthorization for consent; the app never sees refresh tokens. The user ID comes from the calling deployment, and Hobby includes only 500 token requests a month.\n\n- not this job: Clerk MCP server (Clerk, Inc.): The server signs the agent in to the developer's own Clerk workspace only; it holds no third-party provider grants for end users.\n- not this job: Cloudflare Workers OAuth Provider (Cloudflare, Inc.): It is an authorisation and resource server for the developer's own API or MCP server; upstream providers appear only as sign-in options, with no store of users' third-party grants for an agent to call.\n- not this job: Stytch Connected Apps (Twilio Inc.): Connected Apps makes your project an authorisation server for clients calling your app; it has no outbound vault for users' third-party tokens.\n\n## What stops agents finishing\n\n- provider not in the catalogue and no generic OAuth connector\n- free tier caps connections (Auth0 Token Vault: 2 on Free)\n- default OAuth app only accepts the vendor project's own members\n- consent needs a person in a browser at the moment of the request\n\n## Around it\n\nBefore: chat.user-asks, crm.find-account. After: email.read-inbox, messaging.post-message, crm.update-record.\n\n## Where this comes from\n\nWeight 25 of 100 in Agent auth \u0026 delegated access: 12 of 33 accounts (MCP production thread, Nango, Auth0, Arcade, AgentCore, tenant-routing comments); the most described job, scaled from overlapping counts\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/agent-auth.connect-user-account.json, or the MCP tool get_use_case with id agent-auth.connect-user-account. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Connect an agent to a user's account in a third-party app",
        "url": ""
      }
    ],
    "description": "Connect an agent to a user's account in a third-party app: 1 companies fully do it, 10 with a limit, 16 carry the tag. Every listing in Agent auth \u0026 delegated access with the reason and a source.",
    "facts": null,
    "h1": "Connect an agent to a user's account in a third-party app",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/agent-auth.connect-user-account/",
    "published": "",
    "section": "agents",
    "title": "Connect an agent to a user's account in a third-party app | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/agent-auth.connect-user-account/"
  },
  "tokens": {
    "markdown": 1650,
    "slim": 330
  },
  "version": 1
}
