# 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. Category scores, facts, verdicts and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/jumio-vs-veriff - Markdown: https://www.anchorterminal.com/compare/jumio-vs-veriff.md (~2,000 tokens) - Slim: https://www.anchorterminal.com/compare/jumio-vs-veriff.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/jumio-vs-veriff.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 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. - Jumio: grade C, 55/100, rank #521 of 722. Markdown https://www.anchorterminal.com/tools/jumio.md · JSON https://www.anchorterminal.com/api/v1/tools/jumio.json - Veriff: grade C, 61.1/100, rank #376 of 722. Markdown https://www.anchorterminal.com/tools/veriff.md · JSON https://www.anchorterminal.com/api/v1/tools/veriff.json ## 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. 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 | Jumio | Veriff | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 65 | 62 | Jumio +3 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 73 | 82 | Veriff +9 | | Agent ergonomics | 13% (16.2 this run) | 45 | 43 | Jumio +2 | | Security & auth | 14% (17.5 this run) | 63 | 63 | even | | Payments & pricing | 10% (12.5 this run) | 0 | 40 | Veriff +40 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 75 | 74 | Jumio +1 | | Transparency & trust | 7% (8.8 this run) | 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 1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth..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 ### Veriff 1. 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 2. 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 3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004 4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration 5. Poll GET /v1/sessions/{id}/decision until `verification` is 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. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/jumio-vs-veriff.json, and with the fewest tokens: https://www.anchorterminal.com/compare/jumio-vs-veriff.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "jumio", "b": "veriff"}`. From a terminal: `anchor compare jumio veriff` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/jumio.json and https://www.anchorterminal.com/api/v1/tools/veriff.json ## Other comparisons with Jumio or Veriff - [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md) - [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md) - [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md) - [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md) - [Jumio vs Middesk](https://www.anchorterminal.com/compare/jumio-vs-middesk.md) - [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md) - [Jumio vs Sumsub](https://www.anchorterminal.com/compare/jumio-vs-sumsub.md) - [Jumio vs Trulioo](https://www.anchorterminal.com/compare/jumio-vs-trulioo.md) - [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md) - [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md) - [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md) - [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md) - [ComplyAdvantage vs Jumio](https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.md) - [ComplyAdvantage vs Veriff](https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.md)