{ "data": { "a": { "slug": "jumio", "name": "Jumio", "vendor": "Jumio Corporation", "vendorUrl": "https://www.jumio.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Jumio Corporation in Sunnyvale. It checks identity documents and selfies with liveness, screens against sanctions and PEP lists, and runs government database checks. Transactions are started and read through regional REST APIs with OAuth2.", "url": "https://www.anchorterminal.com/tools/jumio", "markdownUrl": "https://www.anchorterminal.com/tools/jumio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/jumio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/jumio.json", "repo": "https://github.com/Jumio/mobile-sdk-android", "license": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@jumio/websdk" }, { "registry": "npm", "name": "react-native-jumio-mobilesdk" } ], "auth": "oauth", "authNotes": "Sales approval. A Jumio account manager activates OAuth2 for the tenant and supplies the workflow keys. An admin then generates client ID and secret pairs in the Jumio Portal, each limited to initiating transactions, to retrieving and deleting them, or both, and each can be deactivated. The pair is sent as Basic credentials to the regional token URL with `grant_type=client_credentials`, and the bearer token lasts 60 minutes. Basic authentication on the REST APIs themselves is marked deprecated. Account creation also returns per-transaction tokens for uploads and the capture SDKs.", "pricing": "paid", "pricingNotes": "No public prices. www.jumio.com/pricing/ returns 404 and the site's Get Started button opens a sales enquiry form. No free tier, trial or self-serve signup was found. The mock service for synthetic test transactions needs a dedicated tenant that Jumio Support or the account manager sets up (checked 2026-10-08).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms-full.txt, the five OpenAPI files or the Jumio website (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 72, "npmWeekly": 2122, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://documentation.jumio.ai", "llmsTxt": "https://documentation.jumio.ai/llms.txt", "openapi": "https://documentation.jumio.ai/redocusaurus/account.yaml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "enterprise", "oauth", "openapi", "llms-txt", "callbacks", "sales-led", "status-page", "soc2", "iso27001", "java", "dotnet" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 55, "grade": "C", "agentReady": false, "rank": 521, "ranked": true, "rankOf": 722, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 60 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Five downloadable OpenAPI 3.0 files covering 25 operations, plus llms.txt and a 2.2 MB llms-full.txt of the docs in Markdown", "OAuth2 client credentials with 60-minute bearer tokens. Each client is limited to initiate, to retrieve and delete, or both, and can be deactivated", "Rate limits are published per tenant. Token requests 10 a second, new transactions 1 a second, retrievals 15 a second", "Statuspage at monitor.jumio.com by data centre, and an unauthenticated health endpoint per region that answers UP, DEGRADED or DOWN", "SOC 2, ISO 27001 and PCI DSS 4.0.1 listed on the Trust Centre, and a vulnerability disclosure programme at vdp.jumio.com" ], "weaknesses": [ "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager", "No service agreement or DPA is published. The public terms of use cover end users in the United States", "Four processing degradations and a 35-minute Singapore outage on the status page between 14 August and 2 October 2026", "No idempotency key. A repeated POST or PUT on accounts starts another transaction", "GET /api/v1/workflow-executions takes no paging or filter parameters, and the specs document only 401, 403 and 404 errors", "Retention periods and the sub-processor list are available on request only, and security.txt returns 404" ], "agentNotes": [ "Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55 } ], "editorialScores": { "ergonomics": 45, "maintenance": 75, "payments": 0, "reliability": 65, "schema": 73, "security": 63, "transparency": 41 }, "provenanceScore": 78 }, "connect": { "http": "curl --location 'https://auth.amer-1.jumio.ai/oauth2/token' \\\n -u CLIENT_ID:CLIENT_SECRET \\\n --header 'Accept: application/json' \\\n --data-urlencode 'grant_type=client_credentials'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/jumio" }, "area": "domain-data", "provenance": { "legalEntity": "Jumio Corporation", "domain": "jumio.com", "domainRegistered": "2004-03-30", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "statusPage": "https://monitor.jumio.com", "changelog": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Online Services Privacy Notice (last updated 4 August 2026) names Jumio Corporation, 100 Mathilda Place, Suite 100, Sunnyvale, CA 94086, with Jumio Software Development GmbH in Linz as EU representative.", "No terms field. Jumio publishes no service agreement or API terms for customers. www.jumio.com/terms-of-use/ (last updated 18 June 2026) is addressed to end users in the United States, so it isn't recorded as the governing document.", "The APIs answer on jumio.ai hosts (auth, account, api, retrieval, kyx and status under amer-1, emea-1 and apac-1), a second domain used throughout Jumio's own documentation at documentation.jumio.ai.", "www.jumio.com/.well-known/security.txt and /security.txt return 404. Reports go to the vulnerability disclosure programme at https://vdp.jumio.com, which pays nothing.", "The changelog linked is the Android SDK's. No changelog for the REST APIs was found.", "RDAP for jumio.com gives a registration date of 2004-03-30." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/jumio.json", "live": { "slug": "jumio", "vendorStatus": { "page": "https://monitor.jumio.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T20:22:37.990012468Z" }, "pages": [ { "url": "https://documentation.jumio.ai/docs/developer-resources/SDKs/mobile-sdk/mobile-sdk-android-master/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:19:56.339175642Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e0b13492ecb" }, { "url": "https://www.jumio.com/privacy-center/privacy-notices/online-services-notice/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:28:35.8188334Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "47ddc34e8761" } ], "updatedAt": "2026-10-08T20:22:37.990012468Z" } }, "answer": "Veriff scores 61.1 (C) on agent readiness against Jumio's 55 (C), and leads in 3 of 7 scored categories.", "b": { "slug": "veriff", "name": "Veriff", "vendor": "Veriff OÜ", "vendorUrl": "https://www.veriff.com", "kind": "http-api", "category": "identity-verification", "summary": "Identity verification service from Veriff in Tallinn. It checks an identity document and a selfie, with liveness, database checks and PEP and sanctions screening. Sessions are created and read through the Public API v1, with results sent by webhook.", "url": "https://www.anchorterminal.com/tools/veriff", "markdownUrl": "https://www.anchorterminal.com/tools/veriff.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/veriff.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/veriff.json", "repo": "https://github.com/Veriff/veriff-js-sdk", "license": "Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@veriff/incontext-sdk" }, { "registry": "npm", "name": "@veriff/js-sdk" }, { "registry": "npm", "name": "@veriff/react-native-sdk" } ], "auth": "api-key", "authNotes": "Self-serve. Signing up for a Self-Serve plan creates a Customer Portal account with a test integration, and Enterprise accounts start from a sales form. Each integration has an API key, sent as `X-AUTH-CLIENT`, and up to five shared secret keys used to compute an HMAC-SHA256 `X-HMAC-SIGNATURE` (over the body on POST and PATCH, over the session ID on GET and DELETE). POST /v1/sessions needs only the API key. Secrets are shown once and can be rotated or deleted by an admin. There are no scopes. A live integration unlocks once the account holder passes Veriff's own identity verification.", "pricing": "usage", "pricingNotes": "Self-Serve is priced per verification with a monthly minimum. Essential is $0.80 ($49 a month minimum), Plus $1.39 ($99) and Premium $1.89 ($209). PEP and sanctions screening adds $0.64, ongoing monitoring $0.09 and two-year retention $0.30. A 15-day trial covers up to 50 sessions with no card, after the account holder completes identity verification. Test integrations are free and unbilled. Enterprise, suggested for 5,000 or more verifications a month, is priced by sales (https://www.veriff.com/plans/self-serve, checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs index, the API guides or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 32, "npmWeekly": 109625, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://devdocs.veriff.com", "llmsTxt": "https://devdocs.veriff.com/llms.txt", "openapi": "https://devdocs.veriff.com/apidocs/v1sessions.md", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "hmac", "webhooks", "openapi", "llms-txt", "free-trial", "sandbox", "status-page", "bug-bounty", "soc2", "iso27001" ], "lastRelease": "2026-10-02", "graded": true, "anchor": { "graded": true, "score": 61.1, "grade": "C", "agentReady": false, "rank": 376, "ranked": true, "rankOf": 722, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 67 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public prices of $0.80, $1.39 and $1.89 a verification, with a 15-day trial of up to 50 sessions and no card", "llms.txt index and Markdown pages, each API endpoint with an OpenAPI 3.0.0 fragment, examples and error schemas", "Up to five shared secret keys per integration, shown once, with documented rotation and deletion", "Test integrations are created at signup, aren't billed, and let the developer force a decision", "ISO/IEC 27001:2022, SOC 2 Type II, Cyber Essentials and a bug bounty on Intigriti paying 50 to 6,000 euros" ], "weaknesses": [ "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture", "No idempotency key on POST /v1/sessions, and no Retry-After or backoff guidance for the documented 429", "Nine status-page incidents between 20 July and 7 October 2026, mostly delayed decisions in the US region", "No endpoint lists sessions and no pagination was found. Every read needs a stored session ID", "Session deletion by API is off by default and capped at 10 sessions in 24 hours", "No security.txt, and the sub-processor list sits on a help centre page that needs JavaScript" ], "agentNotes": [ "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 `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.1 } ], "editorialScores": { "ergonomics": 43, "maintenance": 74, "payments": 40, "reliability": 62, "schema": 82, "security": 63, "transparency": 48 }, "provenanceScore": 85 }, "connect": { "http": "curl -X POST \"https://\u003cBaseURL\u003e/v1/sessions\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-AUTH-CLIENT: API-KEY' \\\n -d '{\"verification\": {}}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/veriff" }, "area": "domain-data", "unitPrices": [ { "item": "Verification, Essential plan (automated decision)", "unit": "tx", "usd": 0.8, "note": "$49 a month minimum" }, { "item": "Verification, Plus plan", "unit": "tx", "usd": 1.39, "note": "$99 a month minimum" }, { "item": "Verification, Premium plan", "unit": "tx", "usd": 1.89, "note": "$209 a month minimum" }, { "item": "PEP and sanctions screening add-on, per verification", "unit": "tx", "usd": 0.64, "note": "charged on top of the monthly minimum" }, { "item": "Ongoing monitoring add-on, per verification", "unit": "tx", "usd": 0.09, "note": "charged on top of the monthly minimum" } ], "provenance": { "legalEntity": "Veriff OÜ", "domain": "veriff.com", "domainRegistered": "2006-04-12", "endpointOnVendorDomain": true, "terms": "https://www.veriff.com/terms-of-service", "privacy": "https://www.veriff.com/privacy-notice", "statusPage": "https://status.veriff.com", "changelog": "https://devdocs.veriff.com/docs/release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy notice (valid from 30 July 2020, last updated 16 April 2026) names Veriff OÜ and Veriff Brazil Ltda. and gives the Estonian Data Protection Inspectorate as lead supervisory authority.", "www.veriff.com/terms-of-service answers 200 with the title Terms of Service but no terms text in the HTML we fetched, so the terms themselves weren't read.", "www.veriff.com/.well-known/security.txt and /security.txt return 404. Reports go to a bug bounty programme on Intigriti (https://www.veriff.com/bug-bounty).", "The API base URL is per integration and shown in the Customer Portal. Code samples in the docs use https://stationapi.veriff.com.", "RDAP for veriff.com gives a registration date of 2006-04-12, which predates the company.", "The sub-processor list is linked from the privacy notice to help.veriff.com, which returned only a JavaScript shell to our fetch." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/veriff.json", "live": { "slug": "veriff", "vendorStatus": { "page": "https://status.veriff.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T20:22:56.656101906Z" }, "versions": [ { "registry": "github", "name": "Veriff/veriff-js-sdk", "version": "v2.0.0", "released": "2025-09-09", "seenAt": "2026-10-08T16:34:12.058479178Z" }, { "registry": "npm", "name": "@veriff/incontext-sdk", "version": "2.5.0", "seenAt": "2026-10-08T16:34:07.822049846Z" }, { "registry": "npm", "name": "@veriff/js-sdk", "version": "2.0.0", "seenAt": "2026-10-08T16:34:08.944903091Z" }, { "registry": "npm", "name": "@veriff/react-native-sdk", "version": "13.2.0", "seenAt": "2026-10-08T16:34:10.073325113Z" } ], "githubStars": 32, "npmWeekly": 109625, "securityTxt": { "url": "https://veriff.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:34.847122653Z" }, "pages": [ { "url": "https://devdocs.veriff.com/docs/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:01.404186048Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "26520a9df2cc" }, { "url": "https://www.veriff.com/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:31:21.093035848Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "024c0d3f9713" }, { "url": "https://www.veriff.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:31:23.123829782Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d9e650601ce7" } ], "updatedAt": "2026-10-08T20:22:56.656101906Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Jumio Corporation", "b": "Veriff OÜ", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED", "b": "Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk)", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-28", "b": "2026-10-02", "name": "Last release" }, { "a": "no document linked", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-08-04", "b": "2026-04-16", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "72 stars, 2.1k npm/wk", "b": "32 stars, 110k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Veriff scores 61.1 (C) on agent readiness against Jumio's 55 (C), and leads in 3 of 7 scored categories.", "question": "Which is better for AI agents, Jumio or Veriff?" }, { "answer": "Jumio uses an OAuth sign-in. Veriff needs an API key.", "question": "Do Jumio and Veriff need an API key?" }, { "answer": "No hosted endpoint is listed for Jumio. No hosted endpoint is listed for Veriff.", "question": "Can an agent call Jumio and Veriff without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "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.", "slug": "jumio", "watchFor": "No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager" }, { "aheadOn": [ "Schema \u0026 documentation, 82 against 73", "Payments \u0026 pricing, 40 against 0", "Transparency \u0026 trust, 67 against 60" ], "also": null, "goodFor": "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.", "slug": "veriff", "watchFor": "No server-side SDK and no MCP server. Official packages cover only browser and mobile capture" } ], "job": { "capability": "kyc.identity", "name": "Kyc identity" }, "others": [ { "json": "https://www.anchorterminal.com/compare/complycube-vs-jumio.json", "title": "ComplyCube vs Jumio", "url": "https://www.anchorterminal.com/compare/complycube-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-veriff.json", "title": "ComplyCube vs Veriff", "url": "https://www.anchorterminal.com/compare/complycube-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-jumio.json", "title": "Didit vs Jumio", "url": "https://www.anchorterminal.com/compare/didit-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-veriff.json", "title": "Didit vs Veriff", "url": "https://www.anchorterminal.com/compare/didit-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-middesk.json", "title": "Jumio vs Middesk", "url": "https://www.anchorterminal.com/compare/jumio-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-persona.json", "title": "Jumio vs Persona", "url": "https://www.anchorterminal.com/compare/jumio-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-sumsub.json", "title": "Jumio vs Sumsub", "url": "https://www.anchorterminal.com/compare/jumio-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/jumio-vs-trulioo.json", "title": "Jumio vs Trulioo", "url": "https://www.anchorterminal.com/compare/jumio-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-veriff.json", "title": "Middesk vs Veriff", "url": "https://www.anchorterminal.com/compare/middesk-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-veriff.json", "title": "Persona vs Veriff", "url": "https://www.anchorterminal.com/compare/persona-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/sumsub-vs-veriff.json", "title": "Sumsub vs Veriff", "url": "https://www.anchorterminal.com/compare/sumsub-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/trulioo-vs-veriff.json", "title": "Trulioo vs Veriff", "url": "https://www.anchorterminal.com/compare/trulioo-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.json", "title": "ComplyAdvantage vs Jumio", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.json", "title": "ComplyAdvantage vs Veriff", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-veriff" } ], "scores": [ { "by": 3, "edge": "jumio", "jumio": 65, "key": "reliability", "name": "Reliability", "veriff": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "veriff", "jumio": 73, "key": "schema", "name": "Schema \u0026 documentation", "veriff": 82, "weight": 13 }, { "by": 2, "edge": "jumio", "jumio": 45, "key": "ergonomics", "name": "Agent ergonomics", "veriff": 43, "weight": 13 }, { "by": 0, "edge": "", "jumio": 63, "key": "security", "name": "Security \u0026 auth", "veriff": 63, "weight": 14 }, { "by": 40, "edge": "veriff", "jumio": 0, "key": "payments", "name": "Payments \u0026 pricing", "veriff": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 1, "edge": "jumio", "jumio": 75, "key": "maintenance", "name": "Maintenance \u0026 community", "veriff": 74, "weight": 7 }, { "by": 7, "edge": "veriff", "jumio": 60, "key": "transparency", "name": "Transparency \u0026 trust", "veriff": 67, "weight": 7 } ], "summary": "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.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/jumio-vs-veriff", "json": "https://www.anchorterminal.com/compare/jumio-vs-veriff.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/jumio-vs-veriff.md", "slim": "https://www.anchorterminal.com/compare/jumio-vs-veriff.min.md" }, "markdown": "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.\n\n- 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\n- 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\n\n## Which one, for what\n\n### Jumio (C)\n\nGood 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.\n\nWatch for: No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager\n\n### Veriff (C)\n\nGood 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.\n\nAhead on:\n- Schema \u0026 documentation, 82 against 73\n- Payments \u0026 pricing, 40 against 0\n- Transparency \u0026 trust, 67 against 60\n\nWatch for: No server-side SDK and no MCP server. Official packages cover only browser and mobile capture\n\n\n## Score by category\n\n| Category | Weight | Jumio | Veriff | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 62 | Jumio +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 82 | Veriff +9 |\n| Agent ergonomics | 13% (16.2 this run) | 45 | 43 | Jumio +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 63 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 40 | Veriff +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 74 | Jumio +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 67 | Veriff +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55 · C** | **61.1 · C** | |\n\n## Facts side by side\n\n| Fact | Jumio | Veriff |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Jumio Corporation | Veriff OÜ |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| 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) |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-28 | 2026-10-02 |\n| Terms last updated | no document linked | couldn't be read |\n| Privacy policy last updated | 2026-08-04 | 2026-04-16 |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | | couldn't be read |\n| Terms restrict benchmarking | | couldn't be read |\n| Terms or service can change without notice | | couldn't be read |\n| Arbitration or class-action waiver | | couldn't be read |\n| Popularity | 72 stars, 2.1k npm/wk | 32 stars, 110k npm/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Jumio\n\n1. Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.\u003cregion\u003e.jumio.ai/oauth2/token with the client ID and secret as Basic credentials\n2. 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\n3. Send a User-Agent header on every call. The Account API marks it required\n4. Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists\n5. 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\n\n### Veriff\n\n1. 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\n2. 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\n3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004\n4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration\n5. Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal\n\n## Questions\n\n### Which is better for AI agents, Jumio or Veriff?\n\nVeriff scores 61.1 (C) on agent readiness against Jumio's 55 (C), and leads in 3 of 7 scored categories.\n\n### Do Jumio and Veriff need an API key?\n\nJumio uses an OAuth sign-in. Veriff needs an API key.\n\n### Can an agent call Jumio and Veriff without installing anything?\n\nNo hosted endpoint is listed for Jumio. No hosted endpoint is listed for Veriff.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"jumio\", \"b\": \"veriff\"}`. From a terminal: `anchor compare jumio veriff`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/jumio.json and https://www.anchorterminal.com/api/v1/tools/veriff.json\n\n## Other comparisons with Jumio or Veriff\n\n- [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md)\n- [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)\n- [Jumio vs Middesk](https://www.anchorterminal.com/compare/jumio-vs-middesk.md)\n- [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md)\n- [Jumio vs Sumsub](https://www.anchorterminal.com/compare/jumio-vs-sumsub.md)\n- [Jumio vs Trulioo](https://www.anchorterminal.com/compare/jumio-vs-trulioo.md)\n- [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md)\n- [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md)\n- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)\n- [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md)\n- [ComplyAdvantage vs Jumio](https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.md)\n- [ComplyAdvantage vs Veriff](https://www.anchorterminal.com/compare/complyadvantage-vs-veriff.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Jumio vs Veriff", "url": "" } ], "description": "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.", "facts": [ "Jumio C 55", "Veriff C 61.1", "scores" ], "h1": "Jumio vs Veriff", "image": "https://www.anchorterminal.com/assets/og/compare-jumio-vs-veriff.png", "path": "/compare/jumio-vs-veriff", "published": "2026-10-01", "section": "tools", "title": "Jumio vs Veriff for AI agents, C 55 vs C 61.1 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, "tokens": { "markdown": 2000, "slim": 630 }, "version": 1 }