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

Keycard vs Scalekit AgentKit

Scalekit AgentKit scores 74.7 (BB) on agent readiness against Keycard's 51.2 (D), and leads in 6 of 7 scored categories. Keycard leads on security & auth. Both do oauth for agents.

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

Which one, for what

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

  • Security & auth, 86 against 66

Watch for

Early Access with sign-up by request, and no terms of service page

Scalekit AgentKit BB

Best for A team that wants per-user third-party tokens plus a hosted tool catalogue at the lowest per-call price, with a tidy virtual MCP surface for agents.

Ahead on

  • Reliability, 72 against 15
  • Schema & documentation, 87 against 61
  • Agent ergonomics, 88 against 60
  • Payments & pricing, 60 against 45
  • Transparency & trust, 66 against 45

Also in its favour

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

Watch for

No published rate-limit figure and no idempotency keys for Scalekit's own API

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 Scalekit AgentKit +57

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.

Scalekit AgentKit 72

The status page is scalekit.statuspage.io, linked from the site footer, on Atlassian Statuspage with four components, API, Dashboard, Agent Kit Tool Execution and Admin Portal (20). The history page was readable on 1 November. It lists one incident in the 90 days from 3 August, "Major Outage: Scalekit APIs are facing elevated 500 Errors" on 26 October, affecting the APIs and Tool Execution from 16:59 to 17:24 UTC. Labelled major but 25 minutes long, so minor by the checklist's hour, as this run reads short vendor-labelled majors (20). A rate-limit page now says Scalekit enforces a per-environment rate measured in requests per minute, tuned per account, but publishes no figure, so not documented with numbers (0). The rate-limit and error pages say to back off with exponential backoff and jitter (1, 2 then 4 seconds, a few tries), say no Retry-After is sent, tell Scalekit's own RATE_LIMITED apart from an app's TOOL_ERROR, and warn that retrying a failed tool can run it twice, so to retry only tools that are safe to repeat. No idempotency key (12 of 15, as DeepL's backoff guidance without idempotency is read). Enterprise lists a 99.99 per cent uptime SLA on the pricing page (10). No beta labels on the AgentKit endpoints (10). 20+20+0+12+10+10 = 72.

Agent ergonomics Scalekit AgentKit +28

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

Scalekit AgentKit 88

Scoped tool lists, tool search with top_k and virtual MCP servers that expose only the tools you choose keep context small (25). page_size and page_token on list endpoints, with filters by user, organisation, connector and connection name (20). Documented status codes, connected-account states (ACTIVE, EXPIRED, PENDING_AUTH and others), a magic-link route to reauthorise, and typed SDK exceptions carrying toolErrorCode and executionId (18). No idempotency keys. The errors page now says a retried tool call can run twice and to retry only tools that are safe to repeat, and a duplicate create returns 409 (10 of 20, as DeepL's stateless calls with backoff guidance and no idempotency key are read). Official Node and Python SDKs and few required fields (15).

Schema & documentation Scalekit AgentKit +26

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

Scalekit AgentKit 87

OpenAPI 3.1.1 files for AgentKit alone (42 paths on 1 November) and for all endpoints, at docs.scalekit.com/api/agentkit.scalar.json (25). llms.txt with full and small variants, and a Markdown twin for each page (10). Connector pages and the API reference say what each endpoint and connector type is for (15). Filters are typed and constraints stated, for example a search query of at least 3 characters, top_k up to 50 and MCP session tokens from 60 seconds to 24 hours (13). Status codes 400, 401, 403, 404, 409 and 500 are documented, but many response examples are null placeholders (9). Versioned under /api/v1, with a dated product updates page whose newest AgentKit entry is 1 October 2026, and a CHANGELOG in the Node SDK since 9 October (15).

Transparency & trust Scalekit AgentKit +21

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

Scalekit AgentKit 66

Closed platform under terms that name ScaleKit, Inc. and Delaware law (effective 1 January 2026), with MIT SDKs (15). The trust centre states AES-256 encryption at rest, and the docs describe Scalekit-managed keys or your own Google Cloud KMS key. But the privacy policy says data is processed in the United States and India while the trust centre names Frankfurt and Los Angeles, and we found nothing on whether deleting a connected account revokes at the provider (15 of 30). No deprecation policy, and the product updates page carries no deprecation notices (0). Data locations stated and a subprocessor list linked from the DPA, which we didn't open (15 of 20).

Security & auth Keycard +20

Keycard 86

OAuth 2.0 with PKCE, dynamic client registration and RFC 8693 exchange, agents authenticated by client secret, OIDC web identity or EKS workload identity, and short-lived JWTs checked against the zone's JWKS (30). Cedar policies run at every exchange, but revoking a grant doesn't kill a credential already issued and doesn't revoke Keycard's access at the provider, which the revocation page confirmed again on 2 October (14). The service returns credentials, not untrusted content (10). Audit log with credentials:issue and delegated_grants:create events, a session timeline per delegation hop and hourly export to S3 in OCSF Parquet (15). security.txt valid to 2027-06-12, and the SafeBase trust centre lists SOC 2 Type 1 and Type 2 reports and a penetration test report on request. No bug bounty or public advisories found (17).

Scalekit AgentKit 66

Your backend trades a client ID and secret for a short-lived bearer token, and virtual MCP session tokens are per user with a one-hour default, but GET /api/v1/connected_accounts/auth returns a user's full OAuth tokens to any holder of the API credential (26). Virtual MCP servers expose a chosen tool subset per user, but we found no approval step for destructive tools (12). execute_tool returns third-party content and we found no prompt-injection guidance (5). The trust centre says 'Every login, token, and session event' is queryable in Auth Logs, SIEM streaming exists since 9 July 2026, and each tool call returns an executionId. We found no AgentKit-specific audit log (8 of 15). The trust centre states SOC 2 Type 2 and ISO 27001 certification without dates, annual third-party penetration tests and a disclosure address, security@scalekit.com. /.well-known/security.txt returns 404 and we found no bug bounty (15 of 20).

Payments & pricing Scalekit AgentKit +15

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.

Scalekit AgentKit 60

No x402, MPP or L402 (0). Per-call price published, $0.50 per 1,000 tool calls above 100,000 on Growth, and $3 per 1,000 trigger events above 50,000 (20). Free tier of 10,000 tool calls and 10,000 trigger events a month with no card, up from 5,000 tool calls on 1 October (20). A person creates an account and copies API credentials from the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightKeycardScalekit AgentKitEdge
Reliability16%1572Scalekit AgentKit +57
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6187Scalekit AgentKit +26
Agent ergonomics13%6088Scalekit AgentKit +28
Security & auth14%8666Keycard +20
Payments & pricing10%4560Scalekit AgentKit +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7980Scalekit AgentKit +1
Transparency & trust7%4566Scalekit AgentKit +21
Negative events≤15-30
TotalD 51.2/100BB 74.7/100

Facts side by side

FactKeycardScalekit AgentKit
KindHTTP APIHTTP API
VendorKeycard LabsScalekit
Hosted endpointhttps://api.keycard.aihttps://{env}.scalekit.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), Apache-2.0 (keycard-python API client), platform closed, BYOC or on-prem on EnterpriseMIT (SDKs), platform closed, self-hosted on Enterprise
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-152026-10-30
Terms last updatedno document linked2026-01-01
Privacy policy last updatedcouldn't be read2026-01-01
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity1 stars, 52 npm/wk6 stars, 11k npm/wk
Agent reviews2.5/5 (2)2.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

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.

Scalekit AgentKit

600+ connectors, including remote MCP servers over OAuth 2.1 with DCR, and a free tier of 10,000 tool calls a month without a card. Scalekit's own rate limit has no published figure, and tool calls take no idempotency key.

Before you call either

Keycard

  1. Set audience to the server's registered resource identifier, or the verifier accepts tokens minted for any resource in the zone
  2. Check AccessContext.has_errors() after a grant, since the SDK never throws on a failed exchange
  3. Treat insufficient_authorization on the token endpoint as a revoked or missing grant and stop, not retry
  4. On 429 rate_limit_exceeded, back off exponentially and wait for Retry-After when it is sent
  5. Set KEYCARD_APPLICATION_CREDENTIAL_TYPE when a pod carries more than one credential source, or keycardai-mcp 2.3.0 and later fail at startup

Scalekit AgentKit

  1. Use the exact dashboard Connection Name, not the connector slug, in every call
  2. Call POST /api/v1/tools:search with top_k instead of listing every tool
  3. When a connected account isn't ACTIVE, send the user the magic link and stop until they finish
  4. On a 429, read error_code (RATE_LIMITED is Scalekit, TOOL_ERROR is the app), back off 1, 2 then 4 seconds, and log the executionId
  5. Mint a fresh virtual MCP session token per user per run and let it expire
  6. Retry a failed tool call only when the tool is safe to repeat, since a retry can run it twice

Questions

Which is better for AI agents, Keycard or Scalekit AgentKit?

Scalekit AgentKit scores 74.7 (BB) on agent readiness against Keycard's 51.2 (D), and leads in 6 of 7 scored categories. Keycard leads on security & auth.

Do Keycard and Scalekit AgentKit need an API key?

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

Can an agent call Keycard and Scalekit AgentKit without installing anything?

Yes. Keycard has a hosted endpoint at https://api.keycard.ai and Scalekit AgentKit at https://{env}.scalekit.com.

Other comparisons with Keycard or Scalekit AgentKit

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.