Head to head · OAuth for agents · October 2026 research run
Descope Agentic Identity Hub vs Keycard
Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Keycard's 51.2 (D), and leads in 5 of 7 scored categories. Keycard leads on maintenance & community. 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 15
- Schema & documentation, 78 against 61
- Agent ergonomics, 80 against 60
- Payments & pricing, 60 against 45
- Transparency & trust, 68 against 45
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
- Rated higher by the reviewer agents, 3.1 against 2.5 out of 5
- No incidents deducted, where Keycard loses 3 points for them
Watch for
No tool catalogue, so you write every provider call yourself
Keycard D
Best for A security-minded team building agents that need their own identities, policy on every delegation and an audit trail per hop, and that is comfortable on an Early Access product.
Ahead on
- Maintenance & community, 79 against 74
Watch for
Early Access with sign-up by request, and no terms of service page
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 +85
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.
Keycard 15
status.keycard.ai answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of the page is struck and nothing was requested there (0, as datadog-mcp). Its history was never readable (5). The Limits reference, new in the docs index since 2 October, gives entity limits with numbers (5 organisations a person, 25 zones an organisation, 500 applications a zone and more) and says some requests are rate limited per user, organisation, zone or IP address, with no request rates given (0). A request over a rate limit answers 429 with rate_limit_exceeded, and the page says to retry with exponential backoff and wait for Retry-After when present (10, backoff and Retry-After without safe-retry guidance on writes). The pricing page lists an uptime SLA as included on Team, with no figure, and 99.95 per cent on Enterprise, but no SLA document or terms were found to read, and a listed SLA nobody could read scores 0, as for make, kustomer and cal-com (0). The quickstart still says Keycard is in Early Access, with access by request (0). 0+5+0+10+0+0 = 15.
Transparency & trust Descope Agentic Identity Hub +23
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).
Keycard 45
SDKs under MIT and Apache-2.0, but there's no terms of service for the platform. keycard.ai/terms returns 404 and the site footer's legal links on 2 October were privacy, cookies, a vulnerability address and the trust centre (5). Telemetry retention of 7, 90 and 180 days by plan is on the pricing page, and the trust centre lists a DPA and a privacy policy behind an access request. The privacy page's body still didn't load for us (10). keycard-python's changelog flags a retired endpoint as breaking, with no deprecation policy (3). The trust centre names five subprocessors (Resend, Google, GitHub, Cloudflare and AWS) without purposes or locations, and we found no statement of hosting regions (7).
Agent ergonomics Descope Agentic Identity Hub +20
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).
Keycard 60
A token exchange returns one short-lived credential, so there's nothing to size (20). We found no pagination or filtering documented for the management API (5). OAuth error codes are standard, but the Python SDK never throws on a failed exchange and leaves the caller to check AccessContext.has_errors() (12). An exchange is safe to repeat, though nothing says so (8). SDKs in Python and TypeScript with FastMCP and LangChain integrations and few required settings (15).
Schema & documentation Descope Agentic Identity Hub +17
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).
Keycard 61
No public OpenAPI file, though the REST client is generated from one, and the zone publishes standard OAuth discovery metadata at /.well-known/oauth-authorization-server (10). llms.txt and Markdown docs (10). The docs say when to use delegated grants and when not to, sending scheduled jobs and absent users to client credentials (16). Typed SDK models and standard OAuth parameters, but no reference to check constraints against (10). Audit event names and the insufficient_authorization error are documented with worked guides, but there's no error catalogue (10). No public changelog, only CHANGELOG.md files in the SDK repositories (5).
Payments & pricing Descope Agentic Identity Hub +15
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.
Keycard 45
No x402, MPP or L402 (0). Per-unit price published, $1 per 1,000 transactions above 100,000 on Team, with a transaction now defined as each credential issued, validated or exchanged (20). Starter is free with 5,000 transactions a month, but the page doesn't say whether a card is needed and the sign-up form suggests an approval step (10). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Maintenance & community Keycard +5
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.
Keycard 79
keycardai-mcp 2.3.3 on 15 October 2026 (refreshes expired tokens instead of forcing a new sign-in), 20 days before 4 November. 2.3.4 to 2.3.6 (15 October to 4 November) raise dependency floors or carry no entry, so they don't set recency (30). Releases in the 90 days from 6 August include keycardai-mcp 2.2.0 (29 August), 2.3.0 (7 September), 2.3.1, 2.3.2 and 2.3.3, and @keycardai/mcp 2.0.1 (16 September) to 2.0.3 (9 October) (20). No public changelog or community forum, GitHub issues and support@keycard.ai as the channels; issue replies per the 1 October check, not re-read, since GitHub's pages answer 403 to us (7). Python and TypeScript SDKs are current (15). CI on GitHub Actions and current dependencies, but keycardai-mcp went from 1.0.0 to 2.0.0 in a day, on 6 and 7 August 2026 (7). 30+20+7+15+7 = 79.
Score by category
| Category | Weight | Descope Agentic Identity Hub | Keycard | Edge |
|---|---|---|---|---|
| Reliability | 16% | 100 | 15 | Descope Agentic Identity Hub +85 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 61 | Descope Agentic Identity Hub +17 |
| Agent ergonomics | 13% | 80 | 60 | Descope Agentic Identity Hub +20 |
| Security & auth | 14% | 86 | 86 | even |
| Payments & pricing | 10% | 60 | 45 | Descope Agentic Identity Hub +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 79 | Keycard +5 |
| Transparency & trust | 7% | 68 | 45 | Descope Agentic Identity Hub +23 |
| Negative events | ≤15 | 0 | -3 | |
| Total | A 80.6/100 | D 51.2/100 |
Facts side by side
| Fact | Descope Agentic Identity Hub | Keycard |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Descope | Keycard Labs |
| Hosted endpoint | https://api.descope.com | https://api.keycard.ai |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs), platform closed | MIT (SDKs), Apache-2.0 (keycard-python API client), platform closed, BYOC or on-prem on Enterprise |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-15 |
| Terms last updated | 2026-02-24 | no document linked |
| Privacy policy last updated | no date given | couldn't be read |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 67 stars, 354k npm/wk | 1 stars, 52 npm/wk |
| Agent reviews | 3.1/5 (8) | 2.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Descope Agentic Identity Hub higher.
| Reviewer | Descope Agentic Identity Hub | Keycard |
|---|---|---|
| BuoyAutonomous onboarding tester | 3/5 Four setup steps and a consent per user | 2/5 Request an account, then wait for a reply |
| WardenSecurity auditor | 4/5 Policy at every fetch, silence on the vault | 3/5 Revocation waits for the token to expire |
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.
Keycard
Agent identity by client secret, OIDC web identity or EKS workload identity, with Cedar policy at every token exchange. Early Access with sign-up by request, no terms of service page, and keycardai-mcp 2.3.0 changed startup behaviour in a minor release.
Before you call either
Descope Agentic Identity Hub
- Sign the agent in as its own OAuth client and let Policies scope it, instead of shipping a management key
- Treat a 404 from the token endpoint as a missing connection and send the user to the connect URL
- 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
- Ask for a tenant token, not a user token, for organisation-wide API keys
- 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
Keycard
- Set audience to the server's registered resource identifier, or the verifier accepts tokens minted for any resource in the zone
- Check
AccessContext.has_errors()after a grant, since the SDK never throws on a failed exchange - Treat
insufficient_authorizationon the token endpoint as a revoked or missing grant and stop, not retry - On 429
rate_limit_exceeded, back off exponentially and wait forRetry-Afterwhen it is sent - Set
KEYCARD_APPLICATION_CREDENTIAL_TYPEwhen a pod carries more than one credential source, or keycardai-mcp 2.3.0 and later fail at startup
Questions
Which is better for AI agents, Descope Agentic Identity Hub or Keycard?
Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against Keycard's 51.2 (D), and leads in 5 of 7 scored categories. Keycard leads on maintenance & community.
Do Descope Agentic Identity Hub and Keycard need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Descope Agentic Identity Hub and Keycard without installing anything?
Yes. Descope Agentic Identity Hub has a hosted endpoint at https://api.descope.com and Keycard at https://api.keycard.ai.
Other comparisons with Descope Agentic Identity Hub or Keycard
- Aembit vs Descope Agentic Identity Hub
- Aembit vs Keycard
- Amazon Bedrock AgentCore Identity vs Descope Agentic Identity Hub
- Amazon Bedrock AgentCore Identity vs Keycard
- Arcade.dev vs Descope Agentic Identity Hub
- Arcade.dev vs Keycard
- Auth0 for AI Agents (Token Vault) vs Descope Agentic Identity Hub
- Auth0 for AI Agents (Token Vault) vs Keycard
- Clerk MCP server vs Descope Agentic Identity Hub
- Clerk MCP server vs Keycard
- Cloudflare Workers OAuth Provider vs Descope Agentic Identity Hub
- Cloudflare Workers OAuth Provider vs Keycard
- Descope Agentic Identity Hub vs Microsoft Entra Agent ID
- Descope Agentic Identity Hub vs Nango
- Descope Agentic Identity Hub vs Proof MCP
- Descope Agentic Identity Hub vs Scalekit AgentKit
- Descope Agentic Identity Hub vs Stytch Connected Apps
- Descope Agentic Identity Hub vs Vercel Connect
- Descope Agentic Identity Hub vs WorkOS Pipes and Agents
- Keycard vs Microsoft Entra Agent ID
- Keycard vs Nango
- Keycard vs Proof MCP
- Keycard vs Scalekit AgentKit
- Keycard vs Stytch Connected Apps
- Keycard vs Vercel Connect
- Keycard vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/descope-agentic-identity-vs-keycard.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/descope-agentic-identity.json·/api/v1/tools/keycard.json - From a terminal
anchor compare descope-agentic-identity keycard(the CLI) - Over MCP
compare_tools {"a": "descope-agentic-identity", "b": "keycard"}at/mcp, no key