{ "data": { "a": { "slug": "complycube", "name": "ComplyCube", "vendor": "ComplyCube (Teemo Technology Ltd)", "vendorUrl": "https://www.complycube.com", "kind": "http-api", "category": "identity-verification", "summary": "ComplyCube verifies people from identity documents and a liveness check, screens people and companies against sanctions, PEP and adverse media lists, and runs address and bureau checks. Agents reach it through a REST API with separate test and live keys.", "url": "https://www.anchorterminal.com/tools/complycube", "markdownUrl": "https://www.anchorterminal.com/tools/complycube.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/complycube.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/complycube.json", "repo": "https://github.com/complycube/complycube-php", "license": "Proprietary service under ComplyCube's terms of service. The PHP library and the web, iOS and Android SDK repositories are MIT, and `@complycube/api` on npm is MIT", "transports": [ "http" ], "remoteUrl": "https://api.complycube.com", "packages": [ { "registry": "npm", "name": "@complycube/api" }, { "registry": "pypi", "name": "complycube" } ], "auth": "api-key", "authNotes": "Every request carries an API key in the `Authorization` header, with no Bearer prefix. Each account has a test key (prefix `test_`) and a live key (prefix `live_`), created and rotated on the API keys page of the Web Portal by a signed-in Owner, Administrator or Developer. Keys have no scopes, and the docs say they carry many privileges. The live key opens when the account is activated from Test to Live in the portal. Client-side SDKs use short-lived tokens from `POST /v1/tokens` (https://docs.complycube.com/documentation/api-reference/authentication).", "pricing": "usage", "pricingNotes": "Starter is $99 a month and Core $299, each converted to credits spent per check, with further checks billed at plan rates. On Starter a document check is $1.05, standard AML screening $0.50 and a photo liveness check $0.35. Growth and Enterprise are quoted by sales. Only completed verifications are charged. The sandbox is free with a test key, and a 14-day trial of 50 checks starts on activation to Live (https://www.complycube.com/en/pricing/, checked 2026-10-08).", "priceSummary": "$99 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI spec or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 6182, "pypiWeekly": 292, "asOf": "2026-10-08" }, "docsUrl": "https://docs.complycube.com/documentation", "llmsTxt": "https://docs.complycube.com/documentation/llms.txt", "openapi": "https://2245032618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkAhgmUKSf8CFUFVL3GEe%2Fuploads%2FcpxxltxmYAxOotxgEkmP%2Fcomplycube-openapi.yaml?alt=media\u0026token=aa988fe0-8ce8-431c-a69a-6657f5eacf28", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business" ], "tags": [ "hosted", "usage-based", "sandbox", "api-key", "openapi", "llms-txt", "webhooks", "status-page", "python", "typescript", "php", "dotnet", "iso27001", "soc2" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 63.7, "grade": "B", "agentReady": false, "rank": 403, "ranked": true, "rankOf": 1076, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 74, "payments": 27, "reliability": 84, "schema": 78, "security": 52, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A sandbox with its own key and scripted outcomes, a public OpenAPI spec, Markdown docs and an audit log API suit an agent running verification checks. Each environment has one unscoped key, no idempotency keys were found, and the only published terms are undated and read as website terms.", "bestFor": "An agent that creates clients, uploads documents, starts document, identity and AML screening checks and reads results for a regulated business, with low entry cost ($99 a month) and a scripted sandbox.", "strengths": [ "Test and live environments have separate keys, and sandbox outcomes are set by test data such as a client last name of attention or failed", "Public OpenAPI 3.0.0 spec (version 1.7.3, 52 operations), `llms.txt`, and every docs page served as Markdown", "Audit log API records the team member, trigger, action and a field-level diff of old and new values", "Per-check prices are public for the Starter and Core plans, and failed or incomplete verifications are not charged", "Statuspage lists API, Web Portal and each check type for four regions, with no incident recorded since August 2022" ], "weaknesses": [ "One API key per environment with no scopes. The docs say keys carry many privileges", "No idempotency keys, and no Retry-After header documented for 429 responses", "The only published terms are undated, read as website terms and cite the Data Protection Act 1998. No service agreement or DPA was found on a public page", "No `security.txt`, disclosure policy or bug bounty found, and the trust centre is drawn by script", "Company search, address search and redaction endpoints are in the API reference but not in the OpenAPI spec", "The ComplyCube MCP server serves documentation only and cannot reach account data" ], "agentNotes": [ "Send the key bare in the `Authorization` header, with no Bearer prefix. Keys start `test_` or `live_`", "Create a client first, then documents or live photos for it, then `POST /v1/checks` with the client and upload IDs", "Stay under 10 requests a second live and 5 in the sandbox. On 429, back off exponentially with jitter, starting at 30 seconds", "A badly formed filter returns 200 with no results, so check filter names before trusting an empty list", "Checks are asynchronous. Subscribe to webhooks, verify the `ComplyCube-Signature` HMAC-SHA256 header, and expect duplicate and out-of-order events" ], "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.7 } ], "editorialScores": { "ergonomics": 60, "maintenance": 74, "payments": 27, "reliability": 84, "schema": 78, "security": 52, "transparency": 43 }, "provenanceScore": 82 }, "connect": { "install": "npm install --save @complycube/api", "http": "curl -X GET https://api.complycube.com/v1/clients \\\n -H 'Authorization: \u003cYOUR_API_KEY\u003e'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/complycube" }, "area": "domain-data", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 99, "note": "converted to usage credits; 1,000 checks a month quota" }, { "item": "Core plan", "unit": "month", "usd": 299, "note": "converted to usage credits; 8,000 checks a month quota" }, { "item": "Document verification check, Starter", "unit": "tx", "usd": 1.05, "note": "per completed check; $0.75 on Core" }, { "item": "Standard AML screening, Starter", "unit": "tx", "usd": 0.5, "note": "per completed check; $0.35 on Core" }, { "item": "Extensive AML screening, Starter", "unit": "tx", "usd": 1.05, "note": "per completed check; $0.85 on Core" }, { "item": "Liveness and facial similarity check (photo), Starter", "unit": "tx", "usd": 0.35, "note": "per completed check; $0.20 on Core" } ], "provenance": { "legalEntity": "Teemo Technology Ltd", "domain": "complycube.com", "domainRegistered": "2018-05-24", "endpointOnVendorDomain": true, "terms": "https://www.complycube.com/en/terms-of-service/", "privacy": "https://www.complycube.com/en/privacy-policy/", "statusPage": "https://status.complycube.com", "changelog": "https://docs.complycube.com/documentation/changelog", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The privacy policy gives ComplyCube as the trading name of TEEMO TECHNOLOGY LTD, company number 12392069, Crown House, 27 Old Gloucester Street, London WC1N 3AX. The terms of service name only ComplyCube, registered in England and Wales, at that address.", "The terms of service are the only terms published. They define the Services to include ComplyCube's data and software services, but are written around website use, carry no date and cite the Data Protection Act 1998. No separate service agreement or DPA was found on a public page.", "The privacy policy covers the website and the Service and carries no date.", "The API answers at api.complycube.com, the Web Portal at portal.complycube.com and the docs at docs.complycube.com.", "www.complycube.com/.well-known/security.txt redirects to a 404 page, and api.complycube.com returns 403 for the same path.", "RDAP for complycube.com gives a registration date of 2018-05-24." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/complycube.json", "live": { "slug": "complycube", "probe": { "target": "https://api.complycube.com", "method": "get", "lastAt": "2026-10-14T09:41:47.00857857Z", "lastOk": true, "lastStatus": 403, "lastMs": 23, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 31, "p95ms24h": 61, "samples24h": 248, "samples30d": 1389, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 100, "ok": 100 } ] }, "vendorStatus": { "page": "https://status.complycube.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:03.573157507Z" }, "versions": [ { "registry": "github", "name": "complycube/complycube-php", "version": "v1.1.7", "released": "2026-06-12", "seenAt": "2026-10-13T22:50:34.951018678Z" }, { "registry": "npm", "name": "@complycube/api", "version": "1.1.14", "seenAt": "2026-10-13T22:50:33.853096293Z" }, { "registry": "pypi", "name": "complycube", "version": "1.1.8", "released": "2025-12-08", "seenAt": "2026-10-13T22:50:34.764450201Z" } ], "githubStars": 8, "npmWeekly": 3903, "pypiWeekly": 226, "securityTxt": { "url": "https://complycube.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-13T15:45:37.986718457Z" }, "llmsTxt": { "url": "https://docs.complycube.com/documentation/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-13T14:11:18.521517961Z" }, "domain": { "domain": "complycube.com", "registered": "2018-05-24", "source": "https://rdap.verisign.com/com/v1/domain/complycube.com", "checkedAt": "2026-10-11T13:22:08.453398589Z" }, "pages": [ { "url": "https://docs.complycube.com/documentation/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-13T20:14:29.245781819Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "a0f1e75d7152" }, { "url": "https://www.complycube.com/en/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-13T20:27:00.290699453Z", "changedAt": "2026-10-13T20:27:00.290699453Z", "fingerprint": "929dd6bebaf1" }, { "url": "https://www.complycube.com/en/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-13T20:27:02.379636504Z", "changedAt": "2026-10-13T20:27:02.379636504Z", "fingerprint": "6e85f6c17ce3" }, { "url": "https://www.complycube.com/en/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-13T20:27:04.438246898Z", "changedAt": "2026-10-13T20:27:04.438246898Z", "fingerprint": "3f61d0059f99" } ], "updatedAt": "2026-10-14T09:41:47.00857857Z" } }, "answer": "ComplyCube scores 63.7 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 3 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.", "b": { "slug": "entrust-identity-verification", "name": "Entrust Identity Verification (formerly Onfido)", "vendor": "Onfido Ltd (Entrust)", "vendorUrl": "https://www.entrust.com/products/identity-verification", "kind": "http-api", "category": "identity-verification", "summary": "Entrust Identity Verification, formerly Onfido, checks identity documents, selfies and liveness, runs watchlist and database checks and orchestrates them in Workflow Studio. Agents use the Onfido Public API v3.6 in EU, US and CA regions.", "url": "https://www.anchorterminal.com/tools/entrust-identity-verification", "markdownUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json", "repo": "https://github.com/onfido/onfido-openapi-spec", "license": "Proprietary service under Entrust's terms. The OpenAPI spec and the server libraries (onfido-java, onfido-node, onfido-php, onfido-python, onfido-ruby) are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "@onfido/api" }, { "registry": "pypi", "name": "onfido-python" } ], "auth": "mixed", "authNotes": "API tokens per region and environment (`api_live.`, `api_sandbox.`, with `_us` and `_ca` variants) sent as `Authorization: Token token=\u003ctoken\u003e`, generated in the Dashboard under Developers, API authentication. From v3.6, OAuth client credentials issue 60-minute access tokens, with scopes and a per-application IP allowlist set in the Dashboard. Tokens remain valid until revoked. SDK tokens are separate and scoped to one workflow run. Live checks need billing details on the account (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No price list was readable. Entrust's pricing page answered 403. The UK G-Cloud 14 listing by Onfido Ltd gives £0.43 to £2.12 a transaction and says a free trial with sandbox access is available. Sandbox requests aren't charged (checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs index, the API v3.6 reference or the OpenAPI spec (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 59334, "pypiWeekly": 26714, "asOf": "2026-10-14" }, "docsUrl": "https://documentation.identity.entrust.com/", "llmsTxt": "https://documentation.identity.entrust.com/llms.txt", "openapi": "https://github.com/onfido/onfido-openapi-spec/blob/master/openapi.yaml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "oauth", "openapi", "llms-txt", "webhooks", "sandbox", "status-page", "python", "typescript", "java", "ruby", "php", "soc2", "iso27001" ], "lastRelease": "2026-08-31", "graded": true, "anchor": { "graded": true, "score": 62.1, "grade": "B", "agentReady": false, "rank": 472, "ranked": true, "rankOf": 1076, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 58, "payments": 20, "reliability": 70, "schema": 84, "security": 58, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "The v3.6 API has a public MIT OpenAPI file, server libraries in five languages, OAuth client credentials with scopes and an 18-month deprecation notice. Entrust's own site answered 403, so terms, privacy notice, pricing and security.txt weren't read. There is no idempotency key, and live tokens need a Dashboard account with billing details.", "bestFor": "A company already contracted with Entrust that wants an agent to create applicants, start workflow runs and read reports through typed libraries and a public spec.", "strengths": [ "Public OpenAPI 3.0 file for v3.6 (85 operations, MIT) with official libraries in Java, Node.js, PHP, Python and Ruby", "OAuth client credentials with scopes and a per-application IP allowlist, alongside region-specific API tokens", "Rate limits stated, 400 requests a minute live and 120 in sandbox, with a free sandbox that returns predetermined results", "Written versioning policy with at least 18 months' notice before a version is deprecated", "Webhooks signed with HMAC-SHA256, retried five times over 10 hours and resendable for 30 days" ], "weaknesses": [ "entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read", "No idempotency key on POST and no Retry-After header on 429", "The API release notes page has no entry after 27 February 2023", "A faulty deployment rejected valid tokens on the CA Public API for an hour on 7 September 2026", "Pricing is known only as a range of £0.43 to £2.12 a transaction from a 2024 UK G-Cloud listing" ], "agentNotes": [ "Use the regional host for the account (api.eu, api.us or api.ca.onfido.com/v3.6). v3.6 has no default region", "Prefer an OAuth client with only the scopes the task needs over a live API token, and refresh the 60-minute access token", "Stay under 400 requests a minute live and 120 in sandbox, and back off on a 429 `rate_limit` error", "Check before retrying a POST. There is no idempotency key, so a retry can create a second applicant or check", "Treat webhook events as duplicates or out of order, and verify `X-SHA2-Signature` over the raw body" ], "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": 62.1 } ], "editorialScores": { "ergonomics": 65, "maintenance": 58, "payments": 20, "reliability": 70, "schema": 84, "security": 58, "transparency": 52 }, "provenanceScore": 87 }, "connect": { "install": "pip install onfido-python" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/entrust-identity-verification" }, "area": "domain-data", "provenance": { "legalEntity": "Onfido Ltd", "domain": "onfido.com", "domainRegistered": "2013-02-22", "endpointOnVendorDomain": true, "terms": "https://www.entrust.com/terms-and-conditions", "privacy": "https://www.entrust.com/sites/default/files/documentation/licensingandagreements/product-privacy-notice-identity-verification-services.pdf", "statusPage": "https://status.onfido.com", "changelog": "https://documentation.identity.entrust.com/api/release-notes", "securityTxt": "unknown", "checked": "2026-10-14", "notes": [ "The UK G-Cloud 14 listing names ONFIDO LTD as supplier. The docs say Onfido is now part of Entrust.", "onfido.com/terms-and-conditions and onfido.com/privacy redirect to the entrust.com URLs above, which answered 403, so neither was read.", "onfido.com/.well-known/security.txt redirects to entrust.com, which answered 403.", "The API answers on api.{eu,us,ca}.onfido.com, an onfido.com subdomain. The docs moved to documentation.identity.entrust.com.", "RDAP for onfido.com gives a registration date of 2013-02-22." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/entrust-identity-verification.json", "live": { "slug": "entrust-identity-verification", "vendorStatus": { "page": "https://status.onfido.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:10.845654397Z" }, "updatedAt": "2026-10-14T09:39:10.845654397Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "ComplyCube (Teemo Technology Ltd)", "b": "Onfido Ltd (Entrust)", "name": "Vendor" }, { "a": "https://api.complycube.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under ComplyCube's terms of service. The PHP library and the web, iOS and Android SDK repositories are MIT, and `@complycube/api` on npm is MIT", "b": "Proprietary service under Entrust's terms. The OpenAPI spec and the server libraries (onfido-java, onfido-node, onfido-php, onfido-python, onfido-ruby) are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-06", "b": "2026-08-31", "name": "Last release" }, { "a": "no date given", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no date given", "b": "", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Arbitration or class-action waiver" }, { "a": "6.2k npm/wk, 292 PyPI/wk", "b": "59k npm/wk, 27k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "ComplyCube scores 63.7 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 3 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, ComplyCube or Entrust Identity Verification (formerly Onfido)?" }, { "answer": "ComplyCube needs an API key. Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in.", "question": "Do ComplyCube and Entrust Identity Verification (formerly Onfido) need an API key?" }, { "answer": "ComplyCube has a hosted endpoint at https://api.complycube.com. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).", "question": "Can an agent call ComplyCube and Entrust Identity Verification (formerly Onfido) without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 84 against 70", "Payments \u0026 pricing, 27 against 20", "Maintenance \u0026 community, 74 against 58" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "An agent that creates clients, uploads documents, starts document, identity and AML screening checks and reads results for a regulated business, with low entry cost ($99 a month) and a scripted sandbox.", "slug": "complycube", "watchFor": "One API key per environment with no scopes. The docs say keys carry many privileges" }, { "aheadOn": [ "Schema \u0026 documentation, 84 against 78", "Agent ergonomics, 65 against 60", "Security \u0026 auth, 58 against 52", "Transparency \u0026 trust, 70 against 63" ], "also": null, "goodFor": "A company already contracted with Entrust that wants an agent to create applicants, start workflow runs and read reports through typed libraries and a public spec.", "slug": "entrust-identity-verification", "watchFor": "entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read" } ], "job": { "capability": "kyc.identity", "name": "Identity verification" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alloy-vs-complycube.json", "title": "Alloy vs ComplyCube", "url": "https://www.anchorterminal.com/compare/alloy-vs-complycube" }, { "json": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.json", "title": "Alloy vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-didit.json", "title": "ComplyCube vs Didit", "url": "https://www.anchorterminal.com/compare/complycube-vs-didit" }, { "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-middesk.json", "title": "ComplyCube vs Middesk", "url": "https://www.anchorterminal.com/compare/complycube-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-persona.json", "title": "ComplyCube vs Persona", "url": "https://www.anchorterminal.com/compare/complycube-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.json", "title": "ComplyCube vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-shufti.json", "title": "ComplyCube vs Shufti", "url": "https://www.anchorterminal.com/compare/complycube-vs-shufti" }, { "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/complycube-vs-stripe-identity.json", "title": "ComplyCube vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/complycube-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-sumsub.json", "title": "ComplyCube vs Sumsub", "url": "https://www.anchorterminal.com/compare/complycube-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/complycube-vs-trulioo.json", "title": "ComplyCube vs Trulioo", "url": "https://www.anchorterminal.com/compare/complycube-vs-trulioo" }, { "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/complycube-vs-vouched.json", "title": "ComplyCube vs Vouched", "url": "https://www.anchorterminal.com/compare/complycube-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.json", "title": "Didit vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.json", "title": "Entrust Identity Verification (formerly Onfido) vs Jumio", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk.json", "title": "Entrust Identity Verification (formerly Onfido) vs Middesk", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona.json", "title": "Entrust Identity Verification (formerly Onfido) vs Persona", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.json", "title": "Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti.json", "title": "Entrust Identity Verification (formerly Onfido) vs Shufti", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.json", "title": "Entrust Identity Verification (formerly Onfido) vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity.json", "title": "Entrust Identity Verification (formerly Onfido) vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub.json", "title": "Entrust Identity Verification (formerly Onfido) vs Sumsub", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo.json", "title": "Entrust Identity Verification (formerly Onfido) vs Trulioo", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.json", "title": "Entrust Identity Verification (formerly Onfido) vs Veriff", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched.json", "title": "Entrust Identity Verification (formerly Onfido) vs Vouched", "url": "https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-complycube.json", "title": "ComplyAdvantage vs ComplyCube", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-complycube" }, { "json": "https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification.json", "title": "ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification" } ], "scores": [ { "by": 14, "complycube": 84, "edge": "complycube", "entrust-identity-verification": 70, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 6, "complycube": 78, "edge": "entrust-identity-verification", "entrust-identity-verification": 84, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 5, "complycube": 60, "edge": "entrust-identity-verification", "entrust-identity-verification": 65, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 6, "complycube": 52, "edge": "entrust-identity-verification", "entrust-identity-verification": 58, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 7, "complycube": 27, "edge": "complycube", "entrust-identity-verification": 20, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "complycube": 74, "edge": "complycube", "entrust-identity-verification": 58, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 7, "complycube": 63, "edge": "entrust-identity-verification", "entrust-identity-verification": 70, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "ComplyCube scores 63.7 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 3 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do identity verification.", "verdicts": { "complycube": "A sandbox with its own key and scripted outcomes, a public OpenAPI spec, Markdown docs and an audit log API suit an agent running verification checks. Each environment has one unscoped key, no idempotency keys were found, and the only published terms are undated and read as website terms.", "entrust-identity-verification": "The v3.6 API has a public MIT OpenAPI file, server libraries in five languages, OAuth client credentials with scopes and an 18-month deprecation notice. Entrust's own site answered 403, so terms, privacy notice, pricing and security.txt weren't read. There is no idempotency key, and live tokens need a Dashboard account with billing details." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification", "json": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.md", "slim": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.min.md" }, "markdown": "ComplyCube scores 63.7 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 3 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust. Both do identity verification.\n\n- ComplyCube: grade B, 63.7/100, rank #403 of 1076. Markdown https://www.anchorterminal.com/tools/complycube.md · JSON https://www.anchorterminal.com/api/v1/tools/complycube.json\n- Entrust Identity Verification (formerly Onfido): grade B, 62.1/100, rank #472 of 1076. Markdown https://www.anchorterminal.com/tools/entrust-identity-verification.md · JSON https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json\n- Best identity and business verification APIs for AI agents: https://www.anchorterminal.com/best/identity-verification/index.md\n- All 119 verification comparisons: https://www.anchorterminal.com/compare/identity-verification/index.md\n\n## Which one, for what\n\n### ComplyCube (B)\n\nGood for: An agent that creates clients, uploads documents, starts document, identity and AML screening checks and reads results for a regulated business, with low entry cost ($99 a month) and a scripted sandbox.\n\nAhead on:\n- Reliability, 84 against 70\n- Payments \u0026 pricing, 27 against 20\n- Maintenance \u0026 community, 74 against 58\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: One API key per environment with no scopes. The docs say keys carry many privileges\n\n### Entrust Identity Verification (formerly Onfido) (B)\n\nGood for: A company already contracted with Entrust that wants an agent to create applicants, start workflow runs and read reports through typed libraries and a public spec.\n\nAhead on:\n- Schema \u0026 documentation, 84 against 78\n- Agent ergonomics, 65 against 60\n- Security \u0026 auth, 58 against 52\n- Transparency \u0026 trust, 70 against 63\n\nWatch for: entrust.com answered 403 to every request, so the terms, privacy notice, pricing page and security.txt weren't read\n\n\n## Score by category\n\n| Category | Weight | ComplyCube | Entrust Identity Verification (formerly Onfido) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 70 | ComplyCube +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 84 | Entrust Identity Verification (formerly Onfido) +6 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 65 | Entrust Identity Verification (formerly Onfido) +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 58 | Entrust Identity Verification (formerly Onfido) +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 27 | 20 | ComplyCube +7 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 58 | ComplyCube +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 70 | Entrust Identity Verification (formerly Onfido) +7 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **62.1 · B** | |\n\n## Facts side by side\n\n| Fact | ComplyCube | Entrust Identity Verification (formerly Onfido) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | ComplyCube (Teemo Technology Ltd) | Onfido Ltd (Entrust) |\n| Hosted endpoint | `https://api.complycube.com` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under ComplyCube's terms of service. The PHP library and the web, iOS and Android SDK repositories are MIT, and `@complycube/api` on npm is MIT | Proprietary service under Entrust's terms. The OpenAPI spec and the server libraries (onfido-java, onfido-node, onfido-php, onfido-python, onfido-ruby) are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-08-31 |\n| Terms last updated | no date given | couldn't be read |\n| Privacy policy last updated | no date given | |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | not found in the text | couldn't be read |\n| Popularity | 6.2k npm/wk, 292 PyPI/wk | 59k npm/wk, 27k PyPI/wk |\n\n## Verdicts\n\n**ComplyCube.** A sandbox with its own key and scripted outcomes, a public OpenAPI spec, Markdown docs and an audit log API suit an agent running verification checks. Each environment has one unscoped key, no idempotency keys were found, and the only published terms are undated and read as website terms.\n\n**Entrust Identity Verification (formerly Onfido).** The v3.6 API has a public MIT OpenAPI file, server libraries in five languages, OAuth client credentials with scopes and an 18-month deprecation notice. Entrust's own site answered 403, so terms, privacy notice, pricing and security.txt weren't read. There is no idempotency key, and live tokens need a Dashboard account with billing details.\n\n## Before you call either\n\n### ComplyCube\n\n1. Send the key bare in the `Authorization` header, with no Bearer prefix. Keys start `test_` or `live_`\n2. Create a client first, then documents or live photos for it, then `POST /v1/checks` with the client and upload IDs\n3. Stay under 10 requests a second live and 5 in the sandbox. On 429, back off exponentially with jitter, starting at 30 seconds\n4. A badly formed filter returns 200 with no results, so check filter names before trusting an empty list\n5. Checks are asynchronous. Subscribe to webhooks, verify the `ComplyCube-Signature` HMAC-SHA256 header, and expect duplicate and out-of-order events\n\n### Entrust Identity Verification (formerly Onfido)\n\n1. Use the regional host for the account (api.eu, api.us or api.ca.onfido.com/v3.6). v3.6 has no default region\n2. Prefer an OAuth client with only the scopes the task needs over a live API token, and refresh the 60-minute access token\n3. Stay under 400 requests a minute live and 120 in sandbox, and back off on a 429 `rate_limit` error\n4. Check before retrying a POST. There is no idempotency key, so a retry can create a second applicant or check\n5. Treat webhook events as duplicates or out of order, and verify `X-SHA2-Signature` over the raw body\n\n## Questions\n\n### Which is better for AI agents, ComplyCube or Entrust Identity Verification (formerly Onfido)?\n\nComplyCube scores 63.7 (B) on agent readiness against Entrust Identity Verification (formerly Onfido)'s 62.1 (B), and leads in 3 of 7 scored categories. Entrust Identity Verification (formerly Onfido) leads on schema \u0026 documentation, agent ergonomics, security \u0026 auth and transparency \u0026 trust.\n\n### Do ComplyCube and Entrust Identity Verification (formerly Onfido) need an API key?\n\nComplyCube needs an API key. Entrust Identity Verification (formerly Onfido) takes an API key or an OAuth sign-in.\n\n### Can an agent call ComplyCube and Entrust Identity Verification (formerly Onfido) without installing anything?\n\nComplyCube has a hosted endpoint at https://api.complycube.com. No hosted endpoint is listed for Entrust Identity Verification (formerly Onfido).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.json, and with the fewest tokens: https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"complycube\", \"b\": \"entrust-identity-verification\"}`. From a terminal: `anchor compare complycube entrust-identity-verification`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/complycube.json and https://www.anchorterminal.com/api/v1/tools/entrust-identity-verification.json\n\n## Other comparisons with ComplyCube or Entrust Identity Verification (formerly Onfido)\n\n- [Alloy vs ComplyCube](https://www.anchorterminal.com/compare/alloy-vs-complycube.md)\n- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)\n- [ComplyCube vs Didit](https://www.anchorterminal.com/compare/complycube-vs-didit.md)\n- [ComplyCube vs Jumio](https://www.anchorterminal.com/compare/complycube-vs-jumio.md)\n- [ComplyCube vs Middesk](https://www.anchorterminal.com/compare/complycube-vs-middesk.md)\n- [ComplyCube vs Persona](https://www.anchorterminal.com/compare/complycube-vs-persona.md)\n- [ComplyCube vs Plaid Identity Verification](https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.md)\n- [ComplyCube vs Shufti](https://www.anchorterminal.com/compare/complycube-vs-shufti.md)\n- [ComplyCube vs Socure RiskOS](https://www.anchorterminal.com/compare/complycube-vs-socure-riskos.md)\n- [ComplyCube vs Stripe Identity](https://www.anchorterminal.com/compare/complycube-vs-stripe-identity.md)\n- [ComplyCube vs Sumsub](https://www.anchorterminal.com/compare/complycube-vs-sumsub.md)\n- [ComplyCube vs Trulioo](https://www.anchorterminal.com/compare/complycube-vs-trulioo.md)\n- [ComplyCube vs Veriff](https://www.anchorterminal.com/compare/complycube-vs-veriff.md)\n- [ComplyCube vs Vouched](https://www.anchorterminal.com/compare/complycube-vs-vouched.md)\n- [Didit vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md)\n- [Entrust Identity Verification (formerly Onfido) vs Jumio](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-jumio.md)\n- [Entrust Identity Verification (formerly Onfido) vs Middesk](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-middesk.md)\n- [Entrust Identity Verification (formerly Onfido) vs Persona](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-persona.md)\n- [Entrust Identity Verification (formerly Onfido) vs Plaid Identity Verification](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-plaid-identity-verification.md)\n- [Entrust Identity Verification (formerly Onfido) vs Shufti](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-shufti.md)\n- [Entrust Identity Verification (formerly Onfido) vs Socure RiskOS](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-socure-riskos.md)\n- [Entrust Identity Verification (formerly Onfido) vs Stripe Identity](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-stripe-identity.md)\n- [Entrust Identity Verification (formerly Onfido) vs Sumsub](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-sumsub.md)\n- [Entrust Identity Verification (formerly Onfido) vs Trulioo](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-trulioo.md)\n- [Entrust Identity Verification (formerly Onfido) vs Veriff](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-veriff.md)\n- [Entrust Identity Verification (formerly Onfido) vs Vouched](https://www.anchorterminal.com/compare/entrust-identity-verification-vs-vouched.md)\n- [ComplyAdvantage vs ComplyCube](https://www.anchorterminal.com/compare/complyadvantage-vs-complycube.md)\n- [ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complyadvantage-vs-entrust-identity-verification.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-14", "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": "ComplyCube vs Entrust Identity Verification (formerly Onfido)", "url": "" } ], "description": "ComplyCube scores 63.7 (B) to Entrust Identity Verification's 62.1 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ComplyCube B 63.7", "Entrust Identity Verification (formerly Onfido) B 62.1", "scores" ], "h1": "ComplyCube vs Entrust Identity Verification (formerly Onfido)", "image": "https://www.anchorterminal.com/assets/og/compare-complycube-vs-entrust-identity-verification.png", "path": "/compare/complycube-vs-entrust-identity-verification", "published": "2026-10-01", "section": "tools", "title": "ComplyCube vs Entrust Identity Verification for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification" }, "tokens": { "markdown": 3050, "slim": 880 }, "version": 1 }