{ "data": { "a": { "slug": "agentcore-identity", "name": "Amazon Bedrock AgentCore Identity", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/", "kind": "http-api", "category": "agent-auth", "summary": "Amazon Bedrock AgentCore Identity is an AWS service that gives agents workload identities, stores OAuth tokens and API keys in a token vault, and runs OAuth flows so agents can call third-party services for users or for themselves.", "url": "https://www.anchorterminal.com/tools/agentcore-identity", "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-identity.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-identity.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-identity.json", "repo": "https://github.com/aws/bedrock-agentcore-sdk-python", "license": "Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AgentCore SDKs for Python and TypeScript are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://bedrock-agentcore.us-east-1.amazonaws.com", "packages": [ { "registry": "pypi", "name": "bedrock-agentcore" }, { "registry": "npm", "name": "bedrock-agentcore" }, { "registry": "npm", "name": "@aws-sdk/client-bedrock-agentcore" }, { "registry": "pypi", "name": "boto3" } ], "auth": "mixed", "authNotes": "A person creates an AWS account and an IAM role. Control-plane calls (`bedrock-agentcore-control`) and data-plane calls (`bedrock-agentcore`) are SigV4-signed with IAM credentials, and the data plane also documents an OAuth bearer route (`UnauthorizedException` for an invalid JWT). The agent first gets a workload access token that carries its own identity and the user's, from a JWT (`GetWorkloadAccessTokenForJWT`), a user ID string (`GetWorkloadAccessTokenForUserId`) or neither (`GetWorkloadAccessToken`), then exchanges it for a third-party OAuth token or API key. Each third-party provider needs an OAuth client the owner registers with that provider. AgentCore Runtime and Gateway fetch the workload access token for the agent.", "pricing": "usage", "pricingNotes": "$0.010 per 1,000 OAuth token or API key requests for non-AWS resources, billed per successful request, with no minimum fee. No additional charge when the service is used through AgentCore Runtime or AgentCore Gateway, which are billed on their own meters. No free tier specific to Identity was found. New AWS accounts get up to $200 of Free Tier credit for up to 6 months, and AWS says most new customers need no payment method at sign-up though it may ask for one (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/).", "priceSummary": "$0.01 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 for paying AWS on the pricing page or in the docs. AgentCore payments is a separate capability for agents paying third-party sellers (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 334717, "pypiWeekly": 1421946, "asOf": "2026-10-08" }, "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/identity.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "capabilities": [ "auth.oauth", "auth.tokens", "auth.consent", "auth.agent-identity", "auth.audit", "infra.aws" ], "tags": [ "hosted", "closed-source", "usage-priced", "oauth", "llms-txt", "python", "typescript", "enterprise", "sla", "soc2", "eu" ], "lastRelease": "2026-09-01", "graded": true, "anchor": { "graded": true, "score": 74.8, "grade": "BB", "agentReady": true, "rank": 64, "ranked": true, "rankOf": 842, "categoryRank": 2, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 70, "payments": 30, "reliability": 85, "schema": 88, "security": 84, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "The service handles user-delegated, machine-to-machine and on-behalf-of token flows through one call, with IAM scoping, KMS encryption and published quotas. It only works inside an AWS account a person creates, the hosted consent portal needs an AgentCore Gateway, and no call to revoke one user's stored grant was found in the API reference.", "bestFor": "Agents already built on AWS, above all those on AgentCore Runtime or Gateway, where token retrieval is automatic and free of extra charge.", "strengths": [ "`GetResourceOauth2Token` covers three flows (USER_FEDERATION, M2M and ON_BEHALF_OF_TOKEN_EXCHANGE) and returns either an access token or an authorisation URL with a session URI.", "25 OAuth vendor values in `CreateOauth2CredentialProvider`, 24 built in (Google, GitHub, Slack, Salesforce, Microsoft, Atlassian and others) plus a custom OAuth 2.0 provider.", "Quotas are published per operation, 200 requests a second for the three workload access token calls and 20 for each management call, all adjustable.", "The token vault is encrypted with an AWS owned KMS key by default or a customer managed key, and IAM policies can name one workload identity and one credential provider.", "$0.010 per 1,000 token or API key requests, with no extra charge when used through AgentCore Runtime or Gateway." ], "weaknesses": [ "No operation to revoke or delete one user's stored grant was found. `forceAuthentication` clears a refresh token, and AWS says it cannot detect a revocation made at the provider.", "The consent portal, launched 1 September 2026, attaches to one AgentCore Gateway with JWT inbound auth and cannot use GitHub, Slack, Salesforce, Atlassian or LinkedIn as its sign-in provider.", "`GetWorkloadAccessTokenForUserId` takes a user ID string the platform does not verify, so the binding to a user rests on the caller and its IAM policy.", "AWS states the service enforces no binding between workload identities and credential providers in one account beyond the IAM policy the owner writes.", "No CloudTrail page for AgentCore Identity was found in the developer guide, though Gateway and Agent Registry each have one." ], "agentNotes": [ "Get a workload access token first (`GetWorkloadAccessTokenForJWT` in production), then pass it as `workloadIdentityToken` to `GetResourceOauth2Token` or `GetResourceApiKey`.", "When `GetResourceOauth2Token` returns `authorizationUrl` instead of `accessToken`, send the URL to the user and call again with the same `sessionUri` after consent.", "For user-delegated flows, host an HTTPS callback, register it with `UpdateWorkloadIdentity` as an allowed return URL, and call `CompleteResourceTokenAuth` after checking the user's session.", "Ask for refresh tokens in the provider's own way, such as `access_type=offline` in `customParameters` for Google or the `offline_access` scope for Microsoft and Atlassian.", "Treat a returned token as possibly revoked. On a 401 from the resource server, retry with `forceAuthentication` set to true." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 74.8 } ], "editorialScores": { "ergonomics": 76, "maintenance": 70, "payments": 30, "reliability": 85, "schema": 88, "security": 84, "transparency": 61 }, "provenanceScore": 88 }, "connect": { "install": "pip install bedrock-agentcore" }, "letme": { "capability": "https://letme.dev/auth.oauth", "tool": "https://letme.dev/agentcore-identity" }, "sameCompany": [ "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "agentcore-memory", "aws-secrets-manager", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api" ], "area": "agent-runtime", "unitPrices": [ { "item": "OAuth token or API key requests for non-AWS resources", "unit": "1k-requests", "usd": 0.01, "note": "Per successful request. No charge when used through AgentCore Runtime or Gateway" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service pages are under aws.amazon.com and the endpoints are on amazonaws.com, an AWS domain.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The AWS Service Terms show Last Updated 1 October 2026. Section 50 covers AI services and section 50.15 covers AgentCore Payments. No section names AgentCore Identity, so the universal terms and section 50 apply.", "The Privacy Notice shows Last Updated 18 May 2026 and gives Amazon Web Services, Inc., 410 Terry Avenue North, Seattle, WA 98109-5210.", "security.txt shows Expires 2026-09-24T16:25:03Z, read on 8 October 2026. It points to the AWS vulnerability disclosure programme on HackerOne and the policy at vdp.aws.security.", "The status page is drawn by script. We read the per-service feed (status.aws.amazon.com/rss/bedrock-agentcore-us-east-1.rss, no items) and the dashboard's history file.", "The domain registration date is carried from our other AWS listings. WHOIS was not reachable from this session.", "The release notes are dated by month only, and the RSS feed they mention was not found at doc-history.rss (404)." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-identity.json", "live": { "slug": "agentcore-identity", "probe": { "target": "https://bedrock-agentcore.us-east-1.amazonaws.com", "method": "get", "lastAt": "2026-10-09T11:28:52.708070294Z", "lastOk": true, "lastStatus": 404, "lastMs": 244, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 257, "p95ms24h": 294, "samples24h": 41, "samples30d": 41, "days": [ { "date": "2026-10-09", "probes": 41, "ok": 41 } ] }, "updatedAt": "2026-10-09T11:28:52.708070294Z" } }, "answer": "Amazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "nango", "name": "Nango", "vendor": "Nango", "vendorUrl": "https://www.nango.dev", "kind": "http-api", "category": "agent-auth", "summary": "Source-available integration platform that handles OAuth, API keys and token refresh for 1,000+ APIs on behalf of your users.", "url": "https://www.anchorterminal.com/tools/nango", "markdownUrl": "https://www.anchorterminal.com/tools/nango.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nango.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nango.json", "repo": "https://github.com/NangoHQ/nango", "license": "Elastic License 2.0", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.nango.dev", "packages": [ { "registry": "npm", "name": "@nangohq/node" }, { "registry": "npm", "name": "@nangohq/frontend" } ], "auth": "mixed", "authNotes": "Backend calls take an environment secret key as `Authorization: Bearer $NANGO_SECRET_KEY`, and API keys can be scoped (agent sessions need `environment:agent_sessions:write`). End users connect through a short-lived connect session token in the Connect UI. An agent session returns its own MCP URL and `session_token`, sent as a Bearer token. The Management MCP at mcp.nango.dev signs in with OAuth.", "pricing": "freemium", "pricingNotes": "Three plans since 2 September 2026. Free is $0 with 10 connections, 10 compute hours and 10 GB of data transfer a month and no card. Pay-as-you-go is $50 a month returned as $50 of usage credits, then $0.29 per connection a month, $0.72 per compute hour and $0.50 per GB. The Growth add-on is $450 a month and adds faster integration delivery (5 days instead of 20) and a private Slack channel, and the changelog of 2 September also puts RBAC, OpenTelemetry export, Connect UI branding, SAML SSO for your team and a HIPAA BAA under it. Enterprise is custom, with connections from $0.01 at volume, 2-day integration delivery, BYOC and self-hosting, dedicated SLAs, and the pricing page lists HIPAA, SAML SSO, SCIM and the audit trail there (https://www.nango.dev/pricing, https://nango.dev/docs/updates/changelog). Free self-hosting covers auth and proxy only, with no MCP server, syncs or webhooks (https://nango.dev/docs/guides/platform/free-self-hosting).", "priceSummary": "$50 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 469086, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://nango.dev/docs", "llmsTxt": "https://nango.dev/docs/llms.txt", "openapi": "https://raw.githubusercontent.com/NangoHQ/nango/master/docs/spec.yaml", "capabilities": [ "auth.oauth", "auth.tokens", "auth.consent", "auth.audit", "agent.tools", "automation.embedded" ], "tags": [ "hosted", "self-hosted", "freemium", "free-tier", "mcp", "llms-txt", "openapi", "oauth", "typescript", "webhooks", "source-available", "enterprise" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 67.7, "grade": "B", "agentReady": false, "rank": 222, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 90, "payments": 40, "reliability": 78, "schema": 85, "security": 67, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -5, "negativeNotes": [ "2026-09-04, CVE-2026-9317 (CVSS 9.2). The runner's tRPC server in Nango before 0.71.6 didn't enforce RUNNER_SECRET_KEY, so anyone who could reach the runner port could run arbitrary JavaScript. Fixed in 0.71.6. Recent and critical, though it needs network access to the runner (https://github.com/advisories/GHSA-9cph-w8mv-q56r)", "2026-09-16, CVE-2026-92804 (high). Nango through 0.70.4 didn't validate caller-supplied connection configuration values. Fixed in later releases. Together with the runner flaw we deduct 5, less than the maximum because both are fixed and disclosed (https://github.com/advisories/GHSA-29mm-6vmq-g8cg)" ], "verdict": "1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan.", "bestFor": "A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.", "strengths": [ "1,000+ APIs with OAuth, API key and client-credentials auth handled", "Per-tenant agent sessions served as an MCP server, credentials never shown to the agent", "Encryption, retention and deletion rules published in the docs", "Per-unit prices in public ($0.29 a connection a month) and a free plan with no card", "Source on GitHub under ELv2, 31 open issues against more than 7,000 filed" ], "weaknesses": [ "Audit trail only on Enterprise, and logs kept 15 days on every plan", "Two CVEs fixed in September 2026, one critical, neither on Nango's own advisory page", "Status page tracks a single component", "No prompt-injection guidance for content agent sessions pass through", "ELv2 bars offering Nango itself as a hosted service" ], "agentNotes": [ "Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent", "Tag connections with your own user and organisation IDs so sessions can select them", "Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying", "Read the rate-limit headers on a 429 and wait for the reset before resuming", "Run 0.71.6 or later when self-hosting, and keep the runner port off the network" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.7 } ], "editorialScores": { "ergonomics": 74, "maintenance": 90, "payments": 40, "reliability": 78, "schema": 85, "security": 67, "transparency": 63 }, "provenanceScore": 88 }, "connect": { "install": "npm install @nangohq/node", "http": "curl -X POST https://api.nango.dev/connect/sessions -H \"Authorization: Bearer $NANGO_SECRET_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"tags\":{\"end_user_id\":\"user-123\"}}'", "claudeCode": "claude mcp add --transport http nango-management --scope user https://mcp.nango.dev/mcp", "config": { "mcpServers": { "nango-management": { "url": "https://mcp.nango.dev/mcp" } } } }, "letme": { "capability": "https://letme.dev/auth.oauth", "tool": "https://letme.dev/nango" }, "area": "agent-runtime", "unitPrices": [ { "item": "Pay-as-you-go subscription", "unit": "month", "usd": 50, "note": "Returned as $50 of usage credits each month" }, { "item": "Connection on Pay-as-you-go", "unit": "account-month", "usd": 0.29, "note": "Per connected end-user account per month" }, { "item": "Data transfer on Pay-as-you-go", "unit": "gb", "usd": 0.5, "note": "10 GB a month free. Compute is $0.72 an hour" }, { "item": "Growth add-on", "unit": "month", "usd": 450, "note": "Faster integration delivery, private Slack, RBAC, branding, SAML SSO, HIPAA BAA" } ], "provenance": { "legalEntity": "Nango Inc", "domain": "nango.dev", "domainRegistered": "2022-05-31", "endpointOnVendorDomain": true, "terms": "https://www.nango.dev/terms", "privacy": "https://www.nango.dev/privacy-policy", "statusPage": "https://status.nango.dev", "changelog": "https://nango.dev/docs/updates/changelog", "securityTxt": "valid", "checked": "2026-10-01", "notes": [ "The legal entity comes from the copyright line in the repository's LICENSE_SHORT, because we couldn't read the terms page on 2026-09-30.", "SECURITY.md asks for reports to security@nango.dev or a private GitHub advisory. The Trust Center at trust.nango.dev holds the SOC 2 report.", "status.nango.dev is a Better Stack page with one component, Nango Cloud Health." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nango.json", "live": { "slug": "nango", "probe": { "target": "https://api.nango.dev", "method": "get", "lastAt": "2026-10-09T11:29:07.190687658Z", "lastOk": true, "lastStatus": 200, "lastMs": 424, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 450, "p95ms24h": 542, "samples24h": 259, "samples30d": 2106, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 122, "ok": 122 } ] }, "vendorStatus": { "page": "https://status.nango.dev", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-09T07:58:12.38775958Z" }, "versions": [ { "registry": "github", "name": "NangoHQ/nango", "version": "v0.71.12", "released": "2026-10-02", "seenAt": "2026-10-08T16:22:20.7927292Z" }, { "registry": "npm", "name": "@nangohq/frontend", "version": "0.71.12", "seenAt": "2026-10-08T16:22:19.220575591Z" }, { "registry": "npm", "name": "@nangohq/node", "version": "0.71.12", "seenAt": "2026-10-08T16:22:18.408405571Z" } ], "githubStars": 12565, "npmWeekly": 574885, "securityTxt": { "url": "https://nango.dev/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T23:59:59.000Z", "checkedAt": "2026-10-08T15:38:54.043924869Z" }, "llmsTxt": { "url": "https://nango.dev/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-08T14:00:41.879573019Z" }, "domain": { "domain": "nango.dev", "registered": "2022-05-31", "source": "https://pubapi.registry.google/rdap/domain/nango.dev", "checkedAt": "2026-10-04T13:09:24.044829714Z" }, "pages": [ { "url": "https://nango.dev/docs/updates/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:22:17.802547108Z", "changedAt": "2026-10-08T18:22:17.802547108Z", "fingerprint": "7434beb81e90" }, { "url": "https://www.nango.dev/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-10-08T18:29:19.012567466Z", "changedAt": "2026-10-07T18:13:03.16074757Z", "fingerprint": "adec6a07286e" }, { "url": "https://www.nango.dev/privacy-policy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-08T18:29:21.716296026Z", "changedAt": "2026-10-05T16:03:46.071317875Z", "fingerprint": "45daea61757a" }, { "url": "https://www.nango.dev/terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-08T18:29:23.439595351Z", "changedAt": "2026-10-05T16:03:48.100151405Z", "fingerprint": "f40a407279cf" } ], "updatedAt": "2026-10-09T11:29:07.190687658Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "Nango", "name": "Vendor" }, { "a": "https://bedrock-agentcore.us-east-1.amazonaws.com", "b": "https://api.nango.dev", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$0.01 per 1,000 requests", "b": "not published", "name": "Price for auth oauth" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AgentCore SDKs for Python and TypeScript are Apache-2.0", "b": "Elastic License 2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-01", "b": "2026-09-30", "name": "Last release" }, { "a": "2026-10-01", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "335k npm/wk, 1.4M PyPI/wk", "b": "469k npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Amazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, Amazon Bedrock AgentCore Identity or Nango?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Amazon Bedrock AgentCore Identity and Nango need an API key?" }, { "answer": "Yes. Amazon Bedrock AgentCore Identity has a hosted endpoint at https://bedrock-agentcore.us-east-1.amazonaws.com and Nango at https://api.nango.dev.", "question": "Can an agent call Amazon Bedrock AgentCore Identity and Nango without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 85 against 78", "Security \u0026 auth, 84 against 67" ], "also": [ "Agent-ready, a grade of BB or better", "No incidents deducted, where Nango loses 5 points for them" ], "goodFor": "Agents already built on AWS, above all those on AgentCore Runtime or Gateway, where token retrieval is automatic and free of extra charge.", "slug": "agentcore-identity", "watchFor": "No operation to revoke or delete one user's stored grant was found. `forceAuthentication` clears a refresh token, and AWS says it cannot detect a revocation made at the provider." }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 90 against 70" ], "also": null, "goodFor": "A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.", "slug": "nango", "watchFor": "Audit trail only on Enterprise, and logs kept 15 days on every plan" } ], "job": { "capability": "auth.oauth", "name": "Auth oauth" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aembit-vs-agentcore-identity.json", "title": "Aembit vs Amazon Bedrock AgentCore Identity", "url": "https://www.anchorterminal.com/compare/aembit-vs-agentcore-identity" }, { "json": "https://www.anchorterminal.com/compare/aembit-vs-nango.json", "title": "Aembit vs Nango", "url": "https://www.anchorterminal.com/compare/aembit-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-arcade.json", "title": "Amazon Bedrock AgentCore Identity vs Arcade.dev", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-arcade" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents.json", "title": "Amazon Bedrock AgentCore Identity vs Auth0 for AI Agents (Token Vault)", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-descope-agentic-identity.json", "title": "Amazon Bedrock AgentCore Identity vs Descope Agentic Identity Hub", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-descope-agentic-identity" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-keycard.json", "title": "Amazon Bedrock AgentCore Identity vs Keycard", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-keycard" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-microsoft-entra-agent-id.json", "title": "Amazon Bedrock AgentCore Identity vs Microsoft Entra Agent ID", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-microsoft-entra-agent-id" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-scalekit-agentkit.json", "title": "Amazon Bedrock AgentCore Identity vs Scalekit AgentKit", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-scalekit-agentkit" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-stytch-connected-apps.json", "title": "Amazon Bedrock AgentCore Identity vs Stytch Connected Apps", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-stytch-connected-apps" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect.json", "title": "Amazon Bedrock AgentCore Identity vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes.json", "title": "Amazon Bedrock AgentCore Identity vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/arcade-vs-nango.json", "title": "Arcade.dev vs Nango", "url": "https://www.anchorterminal.com/compare/arcade-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango.json", "title": "Auth0 for AI Agents (Token Vault) vs Nango", "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-nango.json", "title": "Descope Agentic Identity Hub vs Nango", "url": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/keycard-vs-nango.json", "title": "Keycard vs Nango", "url": "https://www.anchorterminal.com/compare/keycard-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-nango.json", "title": "Microsoft Entra Agent ID vs Nango", "url": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-nango" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-scalekit-agentkit.json", "title": "Nango vs Scalekit AgentKit", "url": "https://www.anchorterminal.com/compare/nango-vs-scalekit-agentkit" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-stytch-connected-apps.json", "title": "Nango vs Stytch Connected Apps", "url": "https://www.anchorterminal.com/compare/nango-vs-stytch-connected-apps" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-vercel-connect.json", "title": "Nango vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/nango-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-workos-pipes.json", "title": "Nango vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/nango-vs-workos-pipes" } ], "scores": [ { "agentcore-identity": 85, "by": 7, "edge": "agentcore-identity", "key": "reliability", "name": "Reliability", "nango": 78, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agentcore-identity": 88, "by": 3, "edge": "agentcore-identity", "key": "schema", "name": "Schema \u0026 documentation", "nango": 85, "weight": 13 }, { "agentcore-identity": 76, "by": 2, "edge": "agentcore-identity", "key": "ergonomics", "name": "Agent ergonomics", "nango": 74, "weight": 13 }, { "agentcore-identity": 84, "by": 17, "edge": "agentcore-identity", "key": "security", "name": "Security \u0026 auth", "nango": 67, "weight": 14 }, { "agentcore-identity": 30, "by": 10, "edge": "nango", "key": "payments", "name": "Payments \u0026 pricing", "nango": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agentcore-identity": 70, "by": 20, "edge": "nango", "key": "maintenance", "name": "Maintenance \u0026 community", "nango": 90, "weight": 7 }, { "agentcore-identity": 75, "by": 1, "edge": "nango", "key": "transparency", "name": "Transparency \u0026 trust", "nango": 76, "weight": 7 } ], "summary": "Amazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community. Both do auth oauth.", "verdicts": { "agentcore-identity": "The service handles user-delegated, machine-to-machine and on-behalf-of token flows through one call, with IAM scoping, KMS encryption and published quotas. It only works inside an AWS account a person creates, the hosted consent portal needs an AgentCore Gateway, and no call to revoke one user's stored grant was found in the API reference.", "nango": "1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/agentcore-identity-vs-nango", "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.md", "slim": "https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.min.md" }, "markdown": "Amazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community. Both do auth oauth.\n\n- Amazon Bedrock AgentCore Identity: grade BB, 74.8/100, rank #64 of 842. Markdown https://www.anchorterminal.com/tools/agentcore-identity.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-identity.json\n- Nango: grade B, 67.7/100, rank #222 of 842. Markdown https://www.anchorterminal.com/tools/nango.md · JSON https://www.anchorterminal.com/api/v1/tools/nango.json\n\n## Which one, for what\n\n### Amazon Bedrock AgentCore Identity (BB)\n\nGood for: Agents already built on AWS, above all those on AgentCore Runtime or Gateway, where token retrieval is automatic and free of extra charge.\n\nAhead on:\n- Reliability, 85 against 78\n- Security \u0026 auth, 84 against 67\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- No incidents deducted, where Nango loses 5 points for them\n\nWatch for: No operation to revoke or delete one user's stored grant was found. `forceAuthentication` clears a refresh token, and AWS says it cannot detect a revocation made at the provider.\n\n### Nango (B)\n\nGood for: A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 90 against 70\n\nWatch for: Audit trail only on Enterprise, and logs kept 15 days on every plan\n\n\n## Score by category\n\n| Category | Weight | Amazon Bedrock AgentCore Identity | Nango | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 85 | 78 | Amazon Bedrock AgentCore Identity +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 85 | Amazon Bedrock AgentCore Identity +3 |\n| Agent ergonomics | 13% (16.2 this run) | 76 | 74 | Amazon Bedrock AgentCore Identity +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 84 | 67 | Amazon Bedrock AgentCore Identity +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 40 | Nango +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 90 | Nango +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 76 | Nango +1 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **74.8 · BB** | **67.7 · B** | |\n\n## Facts side by side\n\n| Fact | Amazon Bedrock AgentCore Identity | Nango |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Amazon Web Services | Nango |\n| Hosted endpoint | `https://bedrock-agentcore.us-east-1.amazonaws.com` | `https://api.nango.dev` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\n| Price for auth oauth | $0.01 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the AWS Customer Agreement and AWS Service Terms. The AgentCore SDKs for Python and TypeScript are Apache-2.0 | Elastic License 2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-01 | 2026-09-30 |\n| Terms last updated | 2026-10-01 | no date given |\n| Privacy policy last updated | 2026-05-18 | no date given |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | yes | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 335k npm/wk, 1.4M PyPI/wk | 469k npm/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## Verdicts\n\n**Amazon Bedrock AgentCore Identity.** The service handles user-delegated, machine-to-machine and on-behalf-of token flows through one call, with IAM scoping, KMS encryption and published quotas. It only works inside an AWS account a person creates, the hosted consent portal needs an AgentCore Gateway, and no call to revoke one user's stored grant was found in the API reference.\n\n**Nango.** 1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan.\n\n## Before you call either\n\n### Amazon Bedrock AgentCore Identity\n\n1. Get a workload access token first (`GetWorkloadAccessTokenForJWT` in production), then pass it as `workloadIdentityToken` to `GetResourceOauth2Token` or `GetResourceApiKey`.\n2. When `GetResourceOauth2Token` returns `authorizationUrl` instead of `accessToken`, send the URL to the user and call again with the same `sessionUri` after consent.\n3. For user-delegated flows, host an HTTPS callback, register it with `UpdateWorkloadIdentity` as an allowed return URL, and call `CompleteResourceTokenAuth` after checking the user's session.\n4. Ask for refresh tokens in the provider's own way, such as `access_type=offline` in `customParameters` for Google or the `offline_access` scope for Microsoft and Atlassian.\n5. Treat a returned token as possibly revoked. On a 401 from the resource server, retry with `forceAuthentication` set to true.\n\n### Nango\n\n1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent\n2. Tag connections with your own user and organisation IDs so sessions can select them\n3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying\n4. Read the rate-limit headers on a 429 and wait for the reset before resuming\n5. Run 0.71.6 or later when self-hosting, and keep the runner port off the network\n\n## Questions\n\n### Which is better for AI agents, Amazon Bedrock AgentCore Identity or Nango?\n\nAmazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community.\n\n### Do Amazon Bedrock AgentCore Identity and Nango need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Amazon Bedrock AgentCore Identity and Nango without installing anything?\n\nYes. Amazon Bedrock AgentCore Identity has a hosted endpoint at https://bedrock-agentcore.us-east-1.amazonaws.com and Nango at https://api.nango.dev.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-identity-vs-nango.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agentcore-identity\", \"b\": \"nango\"}`. From a terminal: `anchor compare agentcore-identity nango`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-identity.json and https://www.anchorterminal.com/api/v1/tools/nango.json\n\n## Other comparisons with Amazon Bedrock AgentCore Identity or Nango\n\n- [Aembit vs Amazon Bedrock AgentCore Identity](https://www.anchorterminal.com/compare/aembit-vs-agentcore-identity.md)\n- [Aembit vs Nango](https://www.anchorterminal.com/compare/aembit-vs-nango.md)\n- [Amazon Bedrock AgentCore Identity vs Arcade.dev](https://www.anchorterminal.com/compare/agentcore-identity-vs-arcade.md)\n- [Amazon Bedrock AgentCore Identity vs Auth0 for AI Agents (Token Vault)](https://www.anchorterminal.com/compare/agentcore-identity-vs-auth0-ai-agents.md)\n- [Amazon Bedrock AgentCore Identity vs Descope Agentic Identity Hub](https://www.anchorterminal.com/compare/agentcore-identity-vs-descope-agentic-identity.md)\n- [Amazon Bedrock AgentCore Identity vs Keycard](https://www.anchorterminal.com/compare/agentcore-identity-vs-keycard.md)\n- [Amazon Bedrock AgentCore Identity vs Microsoft Entra Agent ID](https://www.anchorterminal.com/compare/agentcore-identity-vs-microsoft-entra-agent-id.md)\n- [Amazon Bedrock AgentCore Identity vs Scalekit AgentKit](https://www.anchorterminal.com/compare/agentcore-identity-vs-scalekit-agentkit.md)\n- [Amazon Bedrock AgentCore Identity vs Stytch Connected Apps](https://www.anchorterminal.com/compare/agentcore-identity-vs-stytch-connected-apps.md)\n- [Amazon Bedrock AgentCore Identity vs Vercel Connect](https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect.md)\n- [Amazon Bedrock AgentCore Identity vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes.md)\n- [Arcade.dev vs Nango](https://www.anchorterminal.com/compare/arcade-vs-nango.md)\n- [Auth0 for AI Agents (Token Vault) vs Nango](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-nango.md)\n- [Descope Agentic Identity Hub vs Nango](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-nango.md)\n- [Keycard vs Nango](https://www.anchorterminal.com/compare/keycard-vs-nango.md)\n- [Microsoft Entra Agent ID vs Nango](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-nango.md)\n- [Nango vs Scalekit AgentKit](https://www.anchorterminal.com/compare/nango-vs-scalekit-agentkit.md)\n- [Nango vs Stytch Connected Apps](https://www.anchorterminal.com/compare/nango-vs-stytch-connected-apps.md)\n- [Nango vs Vercel Connect](https://www.anchorterminal.com/compare/nango-vs-vercel-connect.md)\n- [Nango vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/nango-vs-workos-pipes.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Amazon Bedrock AgentCore Identity vs Nango", "url": "" } ], "description": "Amazon Bedrock AgentCore Identity scores 74.8 (BB) on agent readiness against Nango's 67.7 (B), and leads in 4 of 7 scored categories. Nango leads on payments \u0026 pricing and maintenance \u0026 community. Both do auth oauth. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Amazon Bedrock AgentCore Identity BB 74.8", "Nango B 67.7", "scores" ], "h1": "Amazon Bedrock AgentCore Identity vs Nango", "image": "https://www.anchorterminal.com/assets/og/compare-agentcore-identity-vs-nango.png", "path": "/compare/agentcore-identity-vs-nango", "published": "2026-10-01", "section": "tools", "title": "Amazon Bedrock AgentCore Identity vs Nango for AI agents", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-nango" }, "tokens": { "markdown": 2550, "slim": 730 }, "version": 1 }