Head to head · Identity verification · October 2026 research run

Jumio vs Stripe Identity

Stripe Identity scores 77.7 (BB) on agent readiness against Jumio's 55 (C), and leads in 6 of 7 scored categories. Both do identity verification.

Best identity and business verification APIs for AI agents · All 119 verification comparisons

Which one, for what

Jumio C

Best for An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.

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

Watch for

No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager

Stripe Identity BB

Best for A business already on Stripe that needs document and selfie checks or US SSN validation with published prices.

Ahead on

  • Schema & documentation, 94 against 73
  • Agent ergonomics, 93 against 45
  • Security & auth, 86 against 63
  • Payments & pricing, 40 against 0
  • Maintenance & community, 85 against 75
  • Transparency & trust, 85 against 60

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Document, selfie and US SSN checks only. No sanctions or watchlist screening and no business verification

Score by category

CategoryWeight this runJumioStripe IdentityEdge
Reliability16%206562Jumio +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27394Stripe Identity +21
Agent ergonomics13%16.24593Stripe Identity +48
Security & auth14%17.56386Stripe Identity +23
Payments & pricing10%12.5040Stripe Identity +40
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87585Stripe Identity +10
Transparency & trust7%8.86085Stripe Identity +25
Negative events≤1500
TotalC 55/100BB 77.7/100

Facts side by side

FactJumioStripe Identity
KindHTTP APIHTTP API
VendorJumio CorporationStripe, LLC
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP
AuthOAuthAPI key
PricingPaidPay per use
x402nono
LicenceProprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSEDProprietary service under the Stripe Services Agreement and Stripe Identity Terms. The OpenAPI spec and official SDKs are MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-282026-10-01
Terms last updatedno document linked2026-09-28
Privacy policy last updated2026-08-042026-04-28
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the text
Terms restrict benchmarkingnot found in the text
Terms or service can change without noticenot found in the text
Arbitration or class-action waivernot found in the text
Popularity72 stars, 2.1k npm/wk24.2M npm/wk, 11.4M PyPI/wk

Verdicts

Jumio

Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 October 2026.

Stripe Identity

Stripe Identity runs on the Stripe API, with a public OpenAPI spec, idempotency keys, restricted keys for sensitive fields and a redact endpoint. The product page lists £1.25 per document and selfie check, and the first 50 are free. It has no watchlist or business screening, and outside GB, JP and the US it is in public beta.

Before you call either

Jumio

  1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.<region>.jumio.ai/oauth2/token with the client ID and secret as Basic credentials
  2. Reuse the bearer token for its 60 minutes. Token requests are limited to 10 a second and new transactions to 1 a second per tenant
  3. Send a User-Agent header on every call. The Account API marks it required
  4. Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists
  5. Wait for the callback or poll the status endpoint until PROCESSED before retrieving. Jumio's retry schedule starts at 40 seconds and stops after 940

Stripe Identity

  1. Send an Idempotency-Key based on your user reference when creating a VerificationSession, so a retry doesn't make a second session
  2. Send the end user the session URL or client secret. The person completes the check, the agent can't. Links expire after 48 hours
  3. Use a restricted key for verified_outputs.dob and id_number. Without an IP restriction it reads them only for 48 hours
  4. Wait for identity.verification_session.verified or requires_input webhooks instead of polling
  5. Treat redact as irreversible, and don't put personal data in metadata

Questions

Which is better for AI agents, Jumio or Stripe Identity?

Stripe Identity scores 77.7 (BB) on agent readiness against Jumio's 55 (C), and leads in 6 of 7 scored categories.

Do Jumio and Stripe Identity need an API key?

Jumio uses an OAuth sign-in. Stripe Identity needs an API key.

Can an agent call Jumio and Stripe Identity without installing anything?

No hosted endpoint is listed for Jumio. No hosted endpoint is listed for Stripe Identity.

Other comparisons with Jumio or Stripe Identity

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.