Head to head · Identity verification · October 2026 research run

Jumio vs Veriff

Veriff scores 64.8 (B) on agent readiness against Jumio's 50.1 (D), and leads in 4 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 D

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

Veriff B

Best 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

  • Reliability, 67 against 40
  • Schema & documentation, 82 against 73
  • Payments & pricing, 60 against 0
  • Transparency & trust, 69 against 61

Watch for

No server-side SDK and no MCP server. Official packages cover only browser and mobile capture

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.

Payments & pricing Veriff +60

Jumio 0

No x402, MPP or L402 (0). No price is published. The pricing URL returns 404 and the site sends buyers to a sales form (0). No free tier or trial was found, and the mock service needs a tenant set up by Jumio (0). OAuth2 is activated by an account manager, so no agent can onboard alone (0). Per the 8 October check, not re-read on 4 November (Jumio's terms of use bar robots on its websites). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Veriff 60

No x402, MPP or L402 (0). Per-verification prices are public, at $0.80, $1.39 and $1.89 with monthly minimums of $49, $99 and $209, and add-ons priced per verification (20). A 15-day trial of up to 50 sessions with no card, plus free test integrations. The trial starts after the account holder passes identity verification (20). Signup is a browser flow and keys come from the Customer Portal (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Reliability Veriff +27

Jumio 40

Graded on the Platform REST APIs with the hosted lines. Jumio's terms of use (last updated 18 June 2026) bar robots and data mining on jumio.com and its associated websites, so Jumio's hosts weren't re-read on 4 November 2026. The 8 October status readings came from monitor.jumio.com's /api/v2/ JSON endpoints, which this run doesn't use, and the reading of the regional health endpoint was a request to the product itself, so both are struck. No component reading remains (0) and no incident history could be read (5). Limits are published per tenant, 10 token requests, 1 new transaction and 15 retrievals a second, per the 8 October check, not re-read on 4 November (15). A 429 with a JSON body is documented, with a retrieval retry schedule from 40 to 940 seconds and general backoff advice, and no Retry-After header or idempotency key was found, per the 8 October check. Backoff guidance alone gives 10. No SLA found in public pages (0). GA (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

Veriff 67

Graded on the Public API v1 with the hosted lines. Statuspage at status.veriff.com with API, End User Flow, Verification Decisions, Webhooks and Station components by region (20). Nine incidents between 4 August and 2 November 2026, each partial by its own text. Six were delayed decisions for some sessions or the US region (6 August, 1 and 4 September, 1, 27 and 28 October), and the 28 October update says API performance wasn't affected. On 26 August a subset of end users saw errors in the verification flow for about 22 minutes, on 7 October webhooks for expired and abandoned sessions were degraded, and on 23 October address parsing was degraded for nearly six hours. Minor only, so 20 on the checklist, where the 8 October check gave 15 for frequency (20). Session creation is capped at 30 a minute on Self-Serve and 600 on Enterprise, and deletion at 10 in 24 hours. No figures found for other endpoints (12). The spec documents a 429 with code 1004. No Retry-After, backoff guidance or idempotency key found, though webhooks retry for a week and polling the decision endpoint is the documented fallback (5). No SLA found on the pricing, security or Trust Centre pages (0). GA (10).

Schema & documentation Veriff +9

Jumio 73

Five OpenAPI 3.0 files download from the reference pages, covering 25 operations across Accounts, Credentials, Retrieval, Aggregate and Public Status (25). llms.txt and a 2.2 MB llms-full.txt in Markdown, and robots.txt lists both (10). Operations carry a summary and a link to a guide, and the guides explain order of use. Few say when not to use an endpoint (12). String lengths, patterns, UUID formats and 57 enums in the Retrieval spec, but overrideSettings is a free-form object and the mock service packs JSON into customerInternalReference (11). Request and response examples throughout, and decision labels in tables. The specs list only 401, 403 and 404, with 400 and 429 described in prose (9). Paths carry /api/v1 and the specs are versioned 1.0.0, 1.0.2 or v0. No changelog for the REST APIs was found, only undated SDK changelogs (6). Per the 8 October check, not re-read on 4 November (Jumio's terms of use bar robots on its websites).

Veriff 82

Each endpoint page is served as Markdown with an OpenAPI 3.0.0 fragment (Veriff Public API 1.0.0) and component schemas. No single downloadable spec file was found, only a Postman collection (20). llms.txt index and .md pages, and robots.txt allows AI crawlers (10). Endpoint descriptions carry a 'When to use this endpoint' section and implementation notes, such as DELETE being off by default (16). Enums, required lists and formats in the schemas, though the decision payload varies with integration configuration (12). Request examples per product, typed error schemas and published code tables from 1001 to 2104 (13). A v1 path, a written list of backwards compatible changes and dated changelog tables per page. The release notes are mostly SDK versions (11).

Transparency & trust Veriff +8

Jumio 61

Closed service with no public service agreement or API terms. The terms of use page covers end users in the United States (8). The Online Services Privacy Notice, updated 4 August 2026, says Jumio is the controller in general and the processor for certain customers, uses data to improve its services through machine learning, and destroys biometric data within three years. Other retention periods are available on request, and no public DPA was found. The docs say tenant retention is set through support (15). The SDK maintenance policy gives 9 months of support, 24 months to end of life and 3 months' notice of an earlier end. Basic authentication is marked deprecated with no date, and no policy for the REST APIs was found (12). Three data centre regions are named, and the list of third parties is available on request only (6). Per the 8 October check, not re-read on 4 November (Jumio's terms of use bar robots on its websites).

Veriff 69

Closed service. The terms of service page returned no terms text to our fetch on 8 October and wasn't re-read on 2 November, so licence clarity rests on the pricing page and privacy notice (10). The privacy notice, last updated 16 April 2026, describes Veriff as processor for customers, and the pricing page gives retention of 3 or 6 months by plan and 2 years as an add-on. The notice also says session data may be used for machine learning under the customer contract, and no public DPA was found, per the 8 October check (20). Fields are marked deprecated in the spec with dated changelog entries, such as matchStatus on 8 July 2026, and a backwards compatible changes list is published. The status page gave notice on 9 September 2026 that the legacy API and session hosts close on 9 December 2026, with the new hosts running in parallel. No written notice period was found (13). A sub-processor list is linked from the privacy notice but needs JavaScript, and AWS is named for backups (8).

Score by category

CategoryWeightJumioVeriffEdge
Reliability16%4067Veriff +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7382Veriff +9
Agent ergonomics13%4543Jumio +2
Security & auth14%6363even
Payments & pricing10%060Veriff +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7574Jumio +1
Transparency & trust7%6169Veriff +8
Negative events≤1500
TotalD 50.1/100B 64.8/100

Facts side by side

FactJumioVeriff
KindHTTP APIHTTP API
VendorJumio CorporationVeriff OÜ
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. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-10-30
Terms last updatedno document linkedcouldn't be read
Privacy policy last updated2026-08-042026-04-16
Customer content may train modelsyesyes
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularity72 stars, 2.1k npm/wk32 stars, 110k npm/wk
Agent reviewsnone3.3/5 (4)

How the scores have moved

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 no status history could be read for this check.

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 legacy API hosts close on 9 December 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.<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

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
  6. Call the new hosts, such as api-saas.veriff.com, api-eu.veriff.com or api-us.veriff.com. The legacy hosts, among them stationapi.veriff.com, close on 9 December 2026

Questions

Which is better for AI agents, Jumio or Veriff?

Veriff scores 64.8 (B) on agent readiness against Jumio's 50.1 (D), and leads in 4 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

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.