{ "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": 603, "ranked": true, "rankOf": 842, "categoryRank": 10, "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-09T10:41:46.211525155Z" }, "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-09T10:41:46.211525155Z" } }, "answer": "Socure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories.", "b": { "slug": "socure-riskos", "name": "Socure RiskOS", "vendor": "Socure Inc.", "vendorUrl": "https://www.socure.com", "kind": "http-api", "category": "identity-verification", "summary": "Socure RiskOS is an identity verification and risk decisioning platform from Socure Inc. Its Evaluation API runs configured workflows for KYC, document and selfie checks, fraud scoring and watchlist screening, and returns a decision with reason codes.", "url": "https://www.anchorterminal.com/tools/socure-riskos", "markdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/socure-riskos.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/socure-riskos.json", "repo": "https://github.com/socure-inc/.github", "license": "Proprietary service. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "transports": [ "http" ], "remoteUrl": "https://mcp.riskos.socure.com/sandbox", "packages": [ { "registry": "npm", "name": "@socure-inc/device-risk-sdk" } ], "auth": "api-key", "authNotes": "Self-serve API key for the sandbox, sent as `Authorization: Bearer \u003ckey\u003e`. A person signs up in a browser for a Socure Launch sandbox account and copies the key from the Developer Workbench. Sandbox and production use separate keys and hosts. Production starts at 0 requests a second and needs Socure Support to activate it, and Enterprise accounts go through sandbox certification with Socure staff. Each key reaches every workflow, with no scopes. Regenerating a key keeps the old one working until it is deleted, and an additional key is requested from Support. The MCP server takes its own MCP Server Key. IP allowlisting, mutual TLS and payload encryption are optional (checked 2026-10-08).", "pricing": "usage", "pricingNotes": "Socure Launch charges per evaluation started in production, at $0.80 for document verification, $0.90 with watchlist screening, $1.00 for KYC, fraud and watchlist with a document step-up, and $1.30 with prefill. Launch accounts receive $1,000 in production credits each month. The sandbox is free, so an agent can build and test without a contract, but it returns predefined results. Evaluations an end user abandons are still charged. Socure Enterprise is priced through sales. Whether sign-up or the move to production asks for a card was not established (checked 2026-10-08).", "priceSummary": "$0.80 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI file, the MCP server page or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": 35395, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://help.socure.com/riskos/docs", "llmsTxt": "https://help.socure.com/riskos/llms.txt", "openapi": "https://raw.githubusercontent.com/socure-inc/.github/main/openapi-spec/riskos-api-spec.json", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "usage", "sandbox", "api-key", "mcp", "openapi", "llms-txt", "webhooks", "status-page", "soc2", "iso27001", "fedramp" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 63.5, "grade": "B", "agentReady": false, "rank": 357, "ranked": true, "rankOf": 842, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 84, "security": 60, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.", "bestFor": "A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.", "strengths": [ "OpenAPI 3.0.3 file for ten operations and a 3.1 webhook file in a public GitHub repository, last synced 5 October 2026", "llms.txt indexes for every docs section and a Markdown copy of each page, with a robots.txt signal that allows AI input", "Socure Launch publishes four solutions at $0.80 to $1.30 per evaluation, with a free sandbox and $1,000 of monthly production credits", "Errors return one of 15 machine-readable codes with field-level `invalid_args`, and 429 responses carry `X-Retry-After`", "Release notes show entries on 5 and 6 October 2026 and more than 20 dated entries since 10 July" ], "weaknesses": [ "No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture", "Each API key reaches every workflow, with no scopes or read-only keys, and an additional key has to be requested from Support", "The rate limit page advises idempotency keys, but neither the docs nor the OpenAPI file define an idempotency header", "No endpoint lists or searches evaluations. A caller needs the `eval_id` from the original response or a webhook", "Enrichment request and response schemas, reason codes and signal definitions sit in the dashboard, not in the public docs", "Production starts at 0 requests a second until Socure approves it, and Launch accounts are capped at 1 evaluation a second and 500 a day" ], "agentNotes": [ "Send `Authorization: Bearer \u003ckey\u003e` to `https://riskos.sandbox.socure.com/api/evaluation` for tests and `https://riskos.socure.com/api/evaluation` for live checks. The two environments use separate keys.", "Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.", "Store the `eval_id` from every `POST /api/evaluation` response. No list or search endpoint exists to find it later.", "On 429 wait the seconds given in `X-Retry-After`. Do not blindly resend a failed `POST /api/evaluation`, because no idempotency header is documented and Launch bills each initiated evaluation.", "The MCP server at `https://mcp.riskos.socure.com/sandbox` reads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 63.5 } ], "editorialScores": { "ergonomics": 46, "maintenance": 75, "payments": 35, "reliability": 75, "schema": 84, "security": 60, "transparency": 53 }, "provenanceScore": 82 }, "connect": { "http": "curl --request POST \\\n --url \"https://riskos.sandbox.socure.com/api/evaluation\" \\\n --header \"Authorization: Bearer YOUR_API_KEY\" \\\n --header \"Content-Type: application/json\" \\\n --header \"Accept: application/json\" \\\n --data '{\"id\":\"customer-onb-12345\",\"timestamp\":\"2024-12-01T08:15:30.456Z\",\"workflow\":\"consumer_onboarding\",\"data\":{\"individual\":{\"given_name\":\"Jane\",\"family_name\":\"Doe\",\"email\":\"jane.doe@example.com\",\"phone_number\":\"+1-555-123-4567\",\"address\":{\"line_1\":\"123 Main St\",\"locality\":\"San Francisco\",\"major_admin_division\":\"CA\",\"postal_code\":\"94105\",\"country\":\"US\"}}}}'", "claudeCode": "claude mcp add --transport http socure-dev-assist https://mcp.riskos.socure.com/sandbox --header \"Authorization: Bearer $RISKOS_MCP_KEY\"", "config": { "mcpServers": { "socure-dev-assist": { "args": [ "-y", "mcp-remote", "https://mcp.riskos.socure.com/sandbox", "--header", "Authorization: Bearer YOUR_MCP_SERVER_KEY" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/socure-riskos" }, "area": "domain-data", "unitPrices": [ { "item": "Socure Launch, Document Verification (DocV)", "unit": "tx", "usd": 0.8, "note": "Per evaluation started in production, after $1,000 of monthly credits" }, { "item": "Socure Launch, DocV + Watchlist", "unit": "tx", "usd": 0.9, "note": "Per evaluation started in production" }, { "item": "Socure Launch, KYC + Fraud + Watchlist with DocV step-up", "unit": "tx", "usd": 1, "note": "Per evaluation started in production" }, { "item": "Socure Launch, Prefill, KYC + Fraud + Watchlist with DocV step-up", "unit": "tx", "usd": 1.3, "note": "Per evaluation started in production" } ], "provenance": { "legalEntity": "Socure Inc.", "domain": "socure.com", "domainRegistered": "2003-06-20", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.socure.com/privacy-en", "statusPage": "https://status.socure.com", "changelog": "https://help.socure.com/riskos/page/release-notes", "securityTxt": "expired", "checked": "2026-10-08", "notes": [ "The Global Services Privacy Notice (effective 1 October 2026) names Socure Inc. and covers the verification services. A separate Website Privacy Notice covers the marketing site.", "No service agreement or API terms are published. www.socure.com/terms-of-service is the Website Terms of Use, and the policies page lists only privacy notices, the DocV Terms of Use for end users and a text messaging notice, so the terms field is left out.", "The API answers at riskos.socure.com and riskos.sandbox.socure.com, and the MCP server at mcp.riskos.socure.com, all socure.com subdomains.", "www.socure.com/.well-known/security.txt gives security@socure.com and an `Expires` value of 15 July 2026, which has passed.", "RDAP for socure.com gives a registration date of 2003-06-20." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/socure-riskos.json", "live": { "slug": "socure-riskos", "probe": { "target": "https://mcp.riskos.socure.com/sandbox", "method": "get", "lastAt": "2026-10-09T10:42:57.226946622Z", "lastOk": true, "lastStatus": 403, "lastMs": 344, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 334, "p95ms24h": 397, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-09", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://status.socure.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:42:04.23425622Z" }, "updatedAt": "2026-10-09T10:42:57.226946622Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Jumio Corporation", "b": "Socure Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://mcp.riskos.socure.com/sandbox", "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. No service agreement is published, and the OpenAPI file states its licence as Proprietary", "name": "Licence" }, { "a": "none", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-28", "b": "2026-10-06", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-08-04", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "yes", "b": "yes", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "72 stars, 2.1k npm/wk", "b": "35k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Socure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Jumio or Socure RiskOS?" }, { "answer": "Jumio uses an OAuth sign-in. Socure RiskOS needs an API key.", "question": "Do Jumio and Socure RiskOS need an API key?" }, { "answer": "No hosted endpoint is listed for Jumio. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox.", "question": "Can an agent call Jumio and Socure RiskOS 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": [ "Reliability, 75 against 65", "Schema \u0026 documentation, 84 against 73", "Payments \u0026 pricing, 35 against 0", "Transparency \u0026 trust, 68 against 60" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.", "slug": "socure-riskos", "watchFor": "No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document 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-socure-riskos.json", "title": "ComplyCube vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/complycube-vs-socure-riskos" }, { "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-socure-riskos.json", "title": "Didit vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/didit-vs-socure-riskos" }, { "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-shufti.json", "title": "Jumio vs Shufti", "url": "https://www.anchorterminal.com/compare/jumio-vs-shufti" }, { "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/jumio-vs-veriff.json", "title": "Jumio vs Veriff", "url": "https://www.anchorterminal.com/compare/jumio-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos.json", "title": "Persona vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/persona-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.json", "title": "Shufti vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/shufti-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.json", "title": "Socure RiskOS vs Sumsub", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo.json", "title": "Socure RiskOS vs Trulioo", "url": "https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.json", "title": "Socure RiskOS vs Veriff", "url": "https://www.anchorterminal.com/compare/socure-riskos-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-socure-riskos.json", "title": "ComplyAdvantage vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-socure-riskos.json", "title": "Middesk vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/middesk-vs-socure-riskos" } ], "scores": [ { "by": 10, "edge": "socure-riskos", "jumio": 65, "key": "reliability", "name": "Reliability", "socure-riskos": 75, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 11, "edge": "socure-riskos", "jumio": 73, "key": "schema", "name": "Schema \u0026 documentation", "socure-riskos": 84, "weight": 13 }, { "by": 1, "edge": "socure-riskos", "jumio": 45, "key": "ergonomics", "name": "Agent ergonomics", "socure-riskos": 46, "weight": 13 }, { "by": 3, "edge": "jumio", "jumio": 63, "key": "security", "name": "Security \u0026 auth", "socure-riskos": 60, "weight": 14 }, { "by": 35, "edge": "socure-riskos", "jumio": 0, "key": "payments", "name": "Payments \u0026 pricing", "socure-riskos": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 0, "edge": "", "jumio": 75, "key": "maintenance", "name": "Maintenance \u0026 community", "socure-riskos": 75, "weight": 7 }, { "by": 8, "edge": "socure-riskos", "jumio": 60, "key": "transparency", "name": "Transparency \u0026 trust", "socure-riskos": 68, "weight": 7 } ], "summary": "Socure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 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.", "socure-riskos": "A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos", "json": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.md", "slim": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.min.md" }, "markdown": "Socure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories. Both do kyc identity.\n\n- Jumio: grade C, 55/100, rank #603 of 842. Markdown https://www.anchorterminal.com/tools/jumio.md · JSON https://www.anchorterminal.com/api/v1/tools/jumio.json\n- Socure RiskOS: grade B, 63.5/100, rank #357 of 842. Markdown https://www.anchorterminal.com/tools/socure-riskos.md · JSON https://www.anchorterminal.com/api/v1/tools/socure-riskos.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### Socure RiskOS (B)\n\nGood for: A company in the United States that wants one decision from combined KYC, document, fraud and watchlist checks through a single evaluation call.\n\nAhead on:\n- Reliability, 75 against 65\n- Schema \u0026 documentation, 84 against 73\n- Payments \u0026 pricing, 35 against 0\n- Transparency \u0026 trust, 68 against 60\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No service agreement or API terms are published. The only terms pages are website terms of use and end-user terms for document capture\n\n\n## Score by category\n\n| Category | Weight | Jumio | Socure RiskOS | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 65 | 75 | Socure RiskOS +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 73 | 84 | Socure RiskOS +11 |\n| Agent ergonomics | 13% (16.2 this run) | 45 | 46 | Socure RiskOS +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 63 | 60 | Jumio +3 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 35 | Socure RiskOS +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 75 | 75 | even |\n| Transparency \u0026 trust | 7% (8.8 this run) | 60 | 68 | Socure RiskOS +8 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **55 · C** | **63.5 · B** | |\n\n## Facts side by side\n\n| Fact | Jumio | Socure RiskOS |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Jumio Corporation | Socure Inc. |\n| Hosted endpoint | no (local only) | `https://mcp.riskos.socure.com/sandbox` |\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. No service agreement is published, and the OpenAPI file states its licence as Proprietary |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-09-28 | 2026-10-06 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | 2026-08-04 | no date given |\n| Customer content may train models | yes | yes |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | 72 stars, 2.1k npm/wk | 35k 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**Socure RiskOS.** A public OpenAPI file, llms.txt, 15 documented error codes and dated release notes cover a ten-operation REST API, and Socure Launch publishes prices from $0.80 an evaluation with a free sandbox. API keys carry no scopes, no idempotency header is defined, no service terms are published, and production stays at zero requests until Socure activates it.\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### Socure RiskOS\n\n1. Send `Authorization: Bearer \u003ckey\u003e` to `https://riskos.sandbox.socure.com/api/evaluation` for tests and `https://riskos.socure.com/api/evaluation` for live checks. The two environments use separate keys.\n2. Use dummy data only in the sandbox. It returns predefined results, connects to no live data source and expects the documented test values.\n3. Store the `eval_id` from every `POST /api/evaluation` response. No list or search endpoint exists to find it later.\n4. On 429 wait the seconds given in `X-Retry-After`. Do not blindly resend a failed `POST /api/evaluation`, because no idempotency header is documented and Launch bills each initiated evaluation.\n5. The MCP server at `https://mcp.riskos.socure.com/sandbox` reads docs, workflows and webhooks with its own MCP Server Key. It cannot run evaluations or read results.\n\n## Questions\n\n### Which is better for AI agents, Jumio or Socure RiskOS?\n\nSocure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories.\n\n### Do Jumio and Socure RiskOS need an API key?\n\nJumio uses an OAuth sign-in. Socure RiskOS needs an API key.\n\n### Can an agent call Jumio and Socure RiskOS without installing anything?\n\nNo hosted endpoint is listed for Jumio. Socure RiskOS has a hosted endpoint at https://mcp.riskos.socure.com/sandbox.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.json, and with the fewest tokens: https://www.anchorterminal.com/compare/jumio-vs-socure-riskos.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"jumio\", \"b\": \"socure-riskos\"}`. From a terminal: `anchor compare jumio socure-riskos`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/jumio.json and https://www.anchorterminal.com/api/v1/tools/socure-riskos.json\n\n## Other comparisons with Jumio or Socure RiskOS\n\n- [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.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 Shufti](https://www.anchorterminal.com/compare/jumio-vs-shufti.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- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)\n- [Persona vs Socure RiskOS](https://www.anchorterminal.com/compare/persona-vs-socure-riskos.md)\n- [Shufti vs Socure RiskOS](https://www.anchorterminal.com/compare/shufti-vs-socure-riskos.md)\n- [Socure RiskOS vs Sumsub](https://www.anchorterminal.com/compare/socure-riskos-vs-sumsub.md)\n- [Socure RiskOS vs Trulioo](https://www.anchorterminal.com/compare/socure-riskos-vs-trulioo.md)\n- [Socure RiskOS vs Veriff](https://www.anchorterminal.com/compare/socure-riskos-vs-veriff.md)\n- [ComplyAdvantage vs Jumio](https://www.anchorterminal.com/compare/complyadvantage-vs-jumio.md)\n- [ComplyAdvantage vs Socure RiskOS](https://www.anchorterminal.com/compare/complyadvantage-vs-socure-riskos.md)\n- [Middesk vs Socure RiskOS](https://www.anchorterminal.com/compare/middesk-vs-socure-riskos.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "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 Socure RiskOS", "url": "" } ], "description": "Socure RiskOS scores 63.5 (B) on agent readiness against Jumio's 55 (C), and leads in 5 of 7 scored categories. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Jumio C 55", "Socure RiskOS B 63.5", "scores" ], "h1": "Jumio vs Socure RiskOS", "image": "https://www.anchorterminal.com/assets/og/compare-jumio-vs-socure-riskos.png", "path": "/compare/jumio-vs-socure-riskos", "published": "2026-10-01", "section": "tools", "title": "Jumio vs Socure RiskOS for AI agents, C 55 vs B 63.5 | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/jumio-vs-socure-riskos" }, "tokens": { "markdown": 2250, "slim": 580 }, "version": 1 }