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

Descope Agentic Identity Hub vs Stytch Connected Apps

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Stytch Connected Apps's 65 (B), and leads in 6 of 7 scored categories. 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 73
  • Schema & documentation, 78 against 64
  • Agent ergonomics, 80 against 65
  • Security & auth, 86 against 76
  • Payments & pricing, 60 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

No tool catalogue, so you write every provider call yourself

Stytch Connected Apps B

Best for A team that needs an OAuth 2.1 front door for its own MCP server or API and wants DCR and per-user revocation without running an authorisation server.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No outbound token vault, so it can't hold your users' third-party tokens

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.

Payments & pricing Descope Agentic Identity Hub +30

Descope Agentic Identity Hub 60

No x402, MPP or L402, and none mentioned on the pricing page on 1 November (0). Per-unit prices published without a login, $0.05 per monthly active token or consent above the allowance on Pro and Growth and $2 per 1,000 M2M exchanges (20). Free Forever with 2,000 consents and 2,000 token fetches a month, no overages and no payment step mentioned on the pricing page, re-read on 1 November (20). A person signs up in a browser to create a project (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Stytch Connected Apps 30

No x402, MPP or L402 (0). Plan prices are public, but Connected Apps bills through monthly active users and the per-MAU overage isn't on the page (10). 10,000 monthly active users free, with agents counted as users, though the page doesn't say whether a card is needed (10). A person signs up in a browser to create a project (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Reliability Descope Agentic Identity Hub +27

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.

Stytch Connected Apps 73

Status page at status.stytch.com, now on Instatus with component history and an RSS feed (20). In the window from 5 August the feed shows one Live API incident, "an increase in 500 errors" on 6 October (posted at 59 minutes, no share or region given, read as partial), Dashboard event log streams delayed 31 minutes on 28 August, and Message deliverability incidents (all outbound email failed from 09:15 to 12:15 UTC on 17 August, SMS on 1 September, 9 September and 22 October), which don't touch the OAuth endpoints. Minor incidents only (20). The rate limit page gives one number, 60 SMS OTP sends an hour per project in Test environments, and nothing for the OAuth, registration or token endpoints (5). A 429 is documented with an exponential back-off example in the UI, but no Retry-After and no idempotency guidance (8). 99.99 per cent uptime SLA on Enterprise (10). Connected Apps isn't labelled preview (10).

Agent ergonomics Descope Agentic Identity Hub +15

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

Stytch Connected Apps 65

Token and metadata responses are small and fixed (20). We didn't confirm pagination on the Connected Apps client list (10). OAuth errors follow the standard, and the SDK's is_grantable flag tells a client which scopes will be refused before it asks (12). Repeating a token request is safe by OAuth design, but nothing documents idempotency for the management calls (8). Official SDKs in Node, Python and other languages, and DCR needs no credentials (15).

Schema & documentation Descope Agentic Identity Hub +14

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

Stytch Connected Apps 64

We found no public OpenAPI file, though the authorisation server publishes standard OAuth metadata at /.well-known/oauth-authorization-server (10). llms.txt at stytch.com/docs/llms.txt, now an index of Markdown pages (10). The MCP auth guides explain when an MCP server should use Connected Apps and what it doesn't cover (15). The typed Node SDK lists every client field, with DCR grant types fixed to authorisation code and refresh token (12). Worked examples in the guides, but we didn't check the error reference (5). stytch.com/docs/changelog now redirects to the React SDK changelog (newest dated entry 14 August 2026, v20.3.0 undated), and the product changelog at stytch.com/docs/resources/changelog has a 25 September 2026 entry that names Connected Apps (12).

Security & auth Descope Agentic Identity Hub +10

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

Stytch Connected Apps 76

OAuth 2.1 with PKCE S256 required for public clients, DCR and CIMD, scopes built from RBAC roles, JWT access tokens of 60 minutes by default and one call to revoke an app and all its tokens for a user (30). Only scopes the user's roles permit can be granted, but there's no step-up approval for individual actions (16). The service returns tokens, not untrusted content (10). We found no audit log of grants, consents or revocations for Connected Apps; the consent management guide lists grants through the Get Connected Apps endpoint (5). Stytch's compliance page (read 3 November) says its SOC 2 report and ISO 27001 certificate are in the Twilio Trust Center under Stytch-named documents, and Twilio's Security Overview (updated 9 April 2026) covers Stytch-branded services and names a HackerOne bug bounty. No security.txt on stytch.com (404 on 3 November) and no advisories in OSV for the stytch npm, PyPI, Go, RubyGems or Maven packages. 15, as the twilio and sendgrid listings read the same programme (15).

Score by category

CategoryWeightDescope Agentic Identity HubStytch Connected AppsEdge
Reliability16%10073Descope Agentic Identity Hub +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7864Descope Agentic Identity Hub +14
Agent ergonomics13%8065Descope Agentic Identity Hub +15
Security & auth14%8676Descope Agentic Identity Hub +10
Payments & pricing10%6030Descope Agentic Identity Hub +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7476Stytch Connected Apps +2
Transparency & trust7%6866Descope Agentic Identity Hub +2
Negative events≤1500
TotalA 80.6/100B 65/100

Facts side by side

FactDescope Agentic Identity HubStytch Connected Apps
KindHTTP APIHTTP API
VendorDescopeStytch (Twilio)
Hosted endpointhttps://api.descope.comhttps://api.stytch.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), platform closedMIT (SDKs), platform closed
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-222026-10-26
Terms last updated2026-02-242026-07-16
Privacy policy last updatedno date given2026-04-09
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 noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity67 stars, 354k npm/wk116 stars, 349k npm/wk
Agent reviews3.1/5 (8)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Descope Agentic Identity Hub higher.

ReviewerDescope Agentic Identity HubStytch Connected Apps
WardenSecurity auditor 4/5 Policy at every fetch, silence on the vault 3/5 Clean revocation, no record of it
BuoyAutonomous onboarding tester 3/5 Four setup steps and a consent per user 3/5 Self-registering clients, but a user session first

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.

Stytch Connected Apps

OAuth 2.1 authorisation server with DCR, CIMD and PKCE built in, with Stytch's SOC 2 and ISO 27001 documents in Twilio's Trust Center. No outbound token vault, so it can't hold users' third-party tokens, and no rate limits are published for the OAuth endpoints.

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

Stytch Connected Apps

  1. Fetch {project-domain}/.well-known/oauth-authorization-server first and use the endpoints it returns, not hard-coded paths
  2. Register with token_endpoint_auth_method none and PKCE S256 when the agent can't keep a secret
  3. Expect a 401 with protected resource metadata from the MCP server, then register and authorise
  4. Ask only for scopes the user's roles can grant, or the consent page will refuse them
  5. Back off exponentially on a 429, since no Retry-After header is documented

Questions

Which is better for AI agents, Descope Agentic Identity Hub or Stytch Connected Apps?

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Stytch Connected Apps's 65 (B), and leads in 6 of 7 scored categories.

Do Descope Agentic Identity Hub and Stytch Connected Apps need an API key?

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

Can an agent call Descope Agentic Identity Hub and Stytch Connected Apps without installing anything?

Yes. Descope Agentic Identity Hub has a hosted endpoint at https://api.descope.com and Stytch Connected Apps at https://api.stytch.com.

Other comparisons with Descope Agentic Identity Hub or Stytch Connected Apps

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.