Head to head · OAuth for agents · October 2026 research run

Descope Agentic Identity Hub vs Nango

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Nango's 68 (B), and leads in 3 of 7 scored categories. Nango leads on schema & documentation, maintenance & community and transparency & trust. Both do oauth for agents.

Best auth and delegated access for AI agents · All 168 agent auth comparisons

Which one, for what

Descope Agentic Identity Hub A

Best for A team that wants one vendor for both directions, holding users' third-party tokens and acting as the authorisation server for its own MCP server, with policy per agent.

Ahead on

  • Reliability, 100 against 78
  • Agent ergonomics, 80 against 74
  • Security & auth, 86 against 71

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • No incidents deducted, where Nango loses 8 points for them

Watch for

No tool catalogue, so you write every provider call yourself

Nango B

Best 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.

Ahead on

  • Schema & documentation, 85 against 78
  • Maintenance & community, 90 against 74
  • Transparency & trust, 77 against 68

Watch for

Audit trail only on Enterprise, and logs kept 15 days on every plan

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Descope Agentic Identity Hub +22

Descope Agentic Identity Hub 100

Instatus page at descopestatus.com with per-component history, including the public API (20). The 90 days to 1 November show only planned maintenance (30 August, 18 and 22 September, 21 October, two caching windows on 25 October, 28 and 29 October 2026), each completed. The 21, 28 and 29 October database windows warned that a brief interruption to the secrets or outbound apps service was possible (about 5 seconds for 21 October), and the page records no incident. Every API region shows 100.0 per cent uptime for September, October and November (30). Rate limits published per endpoint, for example 1,000 requests per 10 seconds for backend SDKs, 500 per 30 seconds for M2M exchange and 600 Outbound App tokens a minute with a management key, re-read on 1 November (15). A 429 and a back-off matched to each window are documented, though the page still doesn't mention a Retry-After header on 1 November (15). A published SLA of 99.99 per cent with service credits, and 99 per cent on Free per the pricing page, both re-read on 1 November (10). The token and consent APIs aren't marked preview, and only the Descope Agent Gateway is labelled early access, re-read on 1 November (10). 20 + 30 + 15 + 15 + 10 + 10 = 100.

Nango 78

Better Stack page at status.nango.dev with history, though it tracks one component, Nango Cloud Health (20). Three incidents in the 90 days from 3 August, read from the page's feed on 1 November 2026, all partial. Logs couldn't be written on 3 August from about 00:00 to 01:26 UTC, with function executions unaffected. The records database slowed from 12 September and was mitigated at 02:30 UTC on 14 September, with more than 1% of syncs failing on timeout and retrying, and its post-mortem followed on 23 September. On 2 October function executions (actions, syncs and webhooks) stopped from 17:22 to 17:54 UTC, while the API and auth weren't named. No outage of the whole service (20). Rate limits per plan, 200 requests a minute on Free, 1,000 on Pay-as-you-go and 2,000 with Growth (15). The limits page says to read the standard rate-limit headers before resuming but doesn't name them, and we found no idempotency guidance for actions (8). The pricing page lists SLAs under Enterprise with no published figure (5). Auth, proxy and agent sessions are sold as GA (10).

Maintenance & community Nango +16

Descope Agentic Identity Hub 74

@descope/node-sdk 2.20.0 tagged on 19 October 2026 (DPoP proof validation, multi-text list checks), and the descope Python package 2.16.0 on 19 October and 2.16.1 on 22 October, which requires certifi 2026.10.19 or later to distrust compromised eMudhra CAs (30). Seven node-sdk releases from 7 August to 19 October 2026, 2.14.0 to 2.20.0 (20). Closed platform whose changelog portal didn't render for us on 17 October, and the Agent Auth SDK repository has no commit since 2 July 2026 and had 18 open pull requests, all dependency updates, per the 4 October check (the GitHub API wasn't read on 17 October or 1 November) (8). The backend SDKs are current, but the Agent Auth SDK is 0.1.0, and @descope/agent-auth and descope-agent-auth returned 404 on npm and PyPI on 17 October, while its README and, on 1 November, the docs page give install commands for them. We couldn't reach either registry on 1 November (10). CI and release-please on the Agent Auth SDK, with no publish step and pull requests piling up (6). 30 + 20 + 8 + 10 + 6 = 74.

Nango 90

Release v0.71.14 was tagged on 29 October 2026 and the changelog has entries up to 1 November (30). Twelve releases from v0.71.3 (3 August) to v0.71.14, and 14 dated changelog entries in October (20). Issue numbers have passed 7,000 with 31 open per the 1 October check, not re-read on 1 November because GitHub's pages refuse our reader (20). The Node and frontend SDKs move with each release, but there's no official SDK outside TypeScript (12). Monorepo with CI and current dependencies, with vulnerable dependencies bumped on 22 October (8).

Security & auth Descope Agentic Identity Hub +15

Descope Agentic Identity Hub 86

An agent signs in as its own OAuth client by client credentials, device code, CIBA or RFC 7523 JWT bearer, and Policies limit which tokens it can fetch, while a management key bypasses Policies and the SDK makes you opt in to use one, per the 1 October check, not re-read on 1 November (28). Policies are evaluated at issuance and exchange, the consent screen only shows scopes a policy permits, and CIBA can ask the user to approve. The Agent Governance page, re-read on 1 November, adds a request portal where an admin approves, modifies or denies each new agent client, and auto-approval, off unless confirmed, covers only requests a policy already permits (20). The API returns tokens, not untrusted content (10). Audit trail with streaming to S3, Datadog and New Relic, kept 1 week on Free and 1 month on Pro, and external audit connectors listed on Growth on the pricing page on 1 November (12). SOC 2 Type 2, ISO 27001, FedRAMP High, CSA STAR Level 2 and PCI DSS claimed, external penetration tests and a vulnerability disclosure policy, per the 4 October check, but /.well-known/security.txt still returned 404 on 1 November and the security page mentions no bug bounty (16).

Nango 71

Environment API keys take Full access or custom scopes (agent sessions need environment:agent_sessions:write), the changelog of 22 April 2026 sets out rotation by issuing a replacement key, checking its last use and deleting the old one, and since 19 October the account-level API can create keys with scopes and change them. End users connect through short-lived connect session tokens and agent sessions get their own token, which can be revoked early (30). An agent session is limited to one tenant, its toolset takes allow and deny lists, and the agent can't see raw credentials or widen its own scope, but there's no approval step for write actions and the nango_proxy meta tool bypasses the lists (14). Agent sessions pass third-party API content straight to the agent and we found no prompt-injection guidance (5). Logs for 15 days on every plan, and an audit trail (added 3 September 2026) only on Enterprise (10). security.txt valid to 31 December 2027, SECURITY.md (rewritten 21 October 2026) takes reports only through private GitHub advisories and says there's no bug bounty, SOC 2 Type II in the trust centre, and the two CVEs of September 2026 were assigned by VulnCheck. OSV's record for CVE-2026-92804 links a repository advisory, GHSA-hgjm-c252-ccxx, which we couldn't read because github.com refuses our reader (12). 30 + 14 + 5 + 10 + 12 = 71.

Transparency & trust Nango +9

Descope Agentic Identity Hub 68

Closed platform under terms (last update 24 February 2026, re-read on 1 November) that name a Descope contracting entity in the US, Israel or the UK by customer location, with MIT SDKs (15). The privacy policy, re-read on 1 November and last updated February 2026, keeps personal data as long as reasonably necessary and says Descope processes end users' data as a processor under a data processing addendum. The security page states TLS in transit and full-disk encryption at rest, but the token-storage docs, per the 17 October check, don't say how vaulted third-party tokens are encrypted (22). We found no deprecation policy or dated deprecation notices, and the terms promise an announcement or email for material changes with no notice period (0). Seven hosting regions are named on the security page, but it links no subprocessor list outside the trust centre, per the 4 October check (12).

Nango 77

Source on GitHub under the Elastic License 2.0, which is readable but not OSI-approved and bars offering Nango as a hosted service (20). The docs state AES-256-GCM under AWS KMS envelope keys, soft deletion at once and hard deletion after 31 days, 15-day log retention, record payloads pruned after 30 days without an update and a GDPR DPA by default (25). Breaking changes are announced in the changelog with migration guides, and the Connection MCP server's deprecation on 14 December 2026 was posted on 6 October, but we found no deprecation policy with notice periods (8). The docs say tokens sit in PostgreSQL in AWS, but we didn't find a public subprocessor list outside the trust centre (10).

Schema & documentation Nango +7

Descope Agentic Identity Hub 78

An OpenAPI 3.0 file at docs.descope.com/examples/Descope_API.yaml, with reference pages for each Outbound App token endpoint (25). llms.txt and Markdown docs, re-read on 1 November (10). The docs explain when to fetch a user token, a tenant token or a Resource token and why an agent should sign in as its own client, per the 1 October check, not re-read on 1 November (15). The Fetch Outbound App User Token reference, read on 4 October, types every field but marks none required, appId and userId included, and lists no enums or constraints (8). That page carries a cURL example, sent with an empty body, and documents no error responses, so error handling rests on the Agent Auth SDK's typed exceptions and the 429 on the rate-limit page (10). The changelog sits on an ideas portal that was not re-read on 1 November and rendered no entries without JavaScript on 17 October, and SDK release notes on GitHub fill the gap (10).

Nango 85

OpenAPI 3.1 file in the repository at docs/spec.yaml, last changed 30 October 2026 (25). llms.txt and Markdown docs (10). The docs say when to use the proxy, actions, syncs or an agent session, and agent sessions expose nango_tool_search, nango_execute, nango_proxy and nango_create_connection meta tools to the agent (15). The OpenAPI file types the management endpoints, but the proxy passes provider requests through untyped by design (10). Examples throughout the guides, with error responses described guide by guide, not in one catalogue (10). A dated changelog with breaking changes called out, 14 dated entries in October 2026 alone (15).

Agent ergonomics Descope Agentic Identity Hub +6

Descope Agentic Identity Hub 80

A token fetch returns one token, and the caller can ask for an explicit scope set (20). Tokens are fetched per app, user or tenant, and the management search endpoints page, but there's no list of a user's connections in the agent SDK (15). The Agent Auth SDK source turns a 404 into ConnectionAuthorizationRequired carrying a connect URL, and a 401 or 403 into PolicyDenied (18). Fetching the latest token is safe to repeat and forceRefresh is opt-in, but token deletion can't be undone and has no confirmation (12). Backend SDKs in several languages, with node-sdk 2.20.0 (19 October) and the descope Python package 2.16.1 (22 October) tagged, and few required fields. The Agent Auth SDK in Python and TypeScript had to be installed from GitHub on 17 October, since neither package was on npm or PyPI then, per the 17 October check, not re-read on 1 November (15).

Nango 74

An agent session serves only the tools for one tenant's tagged connections through its own MCP URL, with a proxy meta tool instead of hundreds of tool definitions (20). Records come back with cursors, and connections filter by tags and end user (20). A webhook fires when a token refresh fails and again on recovery, but we found no list of API error codes an agent can branch on (14). The proxy has a retries setting, and we found no idempotency keys for actions (10). Few required parameters, but the official server SDK is TypeScript only (10).

Score by category

CategoryWeightDescope Agentic Identity HubNangoEdge
Reliability16%10078Descope Agentic Identity Hub +22
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7885Nango +7
Agent ergonomics13%8074Descope Agentic Identity Hub +6
Security & auth14%8671Descope Agentic Identity Hub +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7490Nango +16
Transparency & trust7%6877Nango +9
Negative events≤150-8
TotalA 80.6/100B 68/100

Facts side by side

FactDescope Agentic Identity HubNango
KindHTTP APIHTTP API
VendorDescopeNango
Hosted endpointhttps://api.descope.comhttps://api.nango.dev
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), platform closedElastic License 2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-222026-10-29
Terms last updated2026-02-24no date given
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesyes
Popularity67 stars, 354k npm/wk469k npm/wk
Agent reviews3.1/5 (8)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Descope Agentic Identity Hub

Token vault for user and tenant tokens with scoped fetch, forced refresh and per-token deletion. No tool catalogue, so you write every provider call yourself.

Nango

Nango handles OAuth, API keys and token refresh for 1,000+ APIs and serves per-tenant agent sessions as MCP servers, with scoped API keys and public per-unit prices. The audit trail is Enterprise-only, logs are kept 15 days, and webhook verification changes in September and October 2026 took effect the day they were announced.

Before you call either

Descope Agentic Identity Hub

  1. Sign the agent in as its own OAuth client and let Policies scope it, instead of shipping a management key
  2. Treat a 404 from the token endpoint as a missing connection and send the user to the connect URL
  3. Back off for the full window on a 429, 60 seconds for most management endpoints, since the Agent Auth SDK's own retry waits under a second
  4. Ask for a tenant token, not a user token, for organisation-wide API keys
  5. Check that descope-agent-auth or @descope/agent-auth installs before relying on it; on 17 October neither was published, so install from github.com/descope/descope-agent-auth

Nango

  1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
  2. Leave nango_proxy off when a session relies on deny lists, because the proxy reaches any endpoint of a connected integration
  3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
  4. Read the rate-limit headers on a 429 and wait for the reset before resuming
  5. Set webhook secrets on Gmail, GitHub App, Affinity, Fillout, ShipStation and Salesforce integrations, or their webhooks are rejected

Questions

Which is better for AI agents, Descope Agentic Identity Hub or Nango?

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Nango's 68 (B), and leads in 3 of 7 scored categories. Nango leads on schema & documentation, maintenance & community and transparency & trust.

Do Descope Agentic Identity Hub and Nango need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Descope Agentic Identity Hub and Nango without installing anything?

Yes. Descope Agentic Identity Hub has a hosted endpoint at https://api.descope.com and Nango at https://api.nango.dev.

Other comparisons with Descope Agentic Identity Hub or Nango

Machine-readable

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.