Head to head · Kyc identity · October 2026 research run
Jumio vs Veriff
Veriff scores 61.1 (C) on agent readiness against Jumio's 55 (C), and leads in 3 of 7 scored categories. Both do kyc identity.
Which one, for what
Jumio C
Good 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
Veriff C
Good for A team that needs document and selfie verification with public per-verification prices and a trial, and that can run a webhook receiver and HMAC signing.
Ahead on
- Schema & documentation, 82 against 73
- Payments & pricing, 40 against 0
- Transparency & trust, 67 against 60
Watch for
No server-side SDK and no MCP server. Official packages cover only browser and mobile capture
Score by category
| Category | Weight this run | Jumio | Veriff | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 62 | Jumio +3 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 73 | 82 | Veriff +9 |
| Agent ergonomics | 13%16.2 | 45 | 43 | Jumio +2 |
| Security & auth | 14%17.5 | 63 | 63 | even |
| Payments & pricing | 10%12.5 | 0 | 40 | Veriff +40 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 75 | 74 | Jumio +1 |
| Transparency & trust | 7%8.8 | 60 | 67 | Veriff +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 55 · C | 61.1 · C |
Facts side by side
| Fact | Jumio | Veriff |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jumio Corporation | Veriff OÜ |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED | Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-28 | 2026-10-02 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | 2026-08-04 | 2026-04-16 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | couldn't be read | |
| Terms restrict benchmarking | couldn't be read | |
| Terms or service can change without notice | couldn't be read | |
| Arbitration or class-action waiver | couldn't be read | |
| Popularity | 72 stars, 2.1k npm/wk | 32 stars, 110k npm/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.
Veriff
Per-verification prices are public from $0.80, with a 15-day trial of 50 sessions and no card. Each endpoint page is Markdown with an OpenAPI 3.0 fragment. There is no server SDK, MCP server or idempotency key, most calls need an HMAC signature, and the status page shows nine incidents between 20 July and 7 October 2026.
Before you call either
Jumio
- 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
- 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
- Send a User-Agent header on every call. The Account API marks it required
- Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists
- 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
Veriff
- Take the base URL from the integration's API keys page. Send X-AUTH-CLIENT on every call and store verification.id from POST /v1/sessions
- Sign POST and PATCH bodies, and the session ID on GET and DELETE, with HMAC-SHA256 in X-HMAC-SIGNATURE. POST /v1/sessions needs no signature
- Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
- Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
- Poll GET /v1/sessions/{id}/decision until
verificationis not null, or accept webhooks within 5 seconds and treat duplicates as normal
Questions
Which is better for AI agents, Jumio or Veriff?
Veriff scores 61.1 (C) on agent readiness against Jumio's 55 (C), and leads in 3 of 7 scored categories.
Do Jumio and Veriff need an API key?
Jumio uses an OAuth sign-in. Veriff needs an API key.
Can an agent call Jumio and Veriff without installing anything?
No hosted endpoint is listed for Jumio. No hosted endpoint is listed for Veriff.
Other comparisons with Jumio or Veriff
Machine-readable
- This page as Markdown
/compare/jumio-vs-veriff.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jumio.json·/api/v1/tools/veriff.json - From a terminal
anchor compare jumio veriff(the CLI) - Over MCP
compare_tools {"a": "jumio", "b": "veriff"}at/mcp, no key