{ "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": 299, "ranked": true, "rankOf": 722, "categoryRank": 4, "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-08T21:12:08.016023639Z", "lastOk": true, "lastStatus": 403, "lastMs": 28, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 32, "p95ms24h": 67, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.complycube.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:57.230738482Z" }, "updatedAt": "2026-10-08T21:12:08.016023639Z" } }, "answer": "Didit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories.", "b": { "slug": "didit", "name": "Didit", "vendor": "Didit Identity Spain, S.L.", "vendorUrl": "https://didit.me", "kind": "http-api", "category": "identity-verification", "summary": "Didit is a hosted identity verification service for document, liveness, face match, sanctions screening and business registry checks. Developers reach it through a REST API with an OpenAPI spec, a hosted MCP server and client SDKs.", "url": "https://www.anchorterminal.com/tools/didit", "markdownUrl": "https://www.anchorterminal.com/tools/didit.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/didit.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/didit.json", "repo": "https://github.com/didit-protocol/mcp", "license": "Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://verification.didit.me", "packages": [ { "registry": "npm", "name": "@didit-protocol/mcp-server" }, { "registry": "npm", "name": "@didit-protocol/sdk-web" }, { "registry": "npm", "name": "@didit-protocol/sdk-react-native" } ], "auth": "mixed", "authNotes": "Self-serve. The REST API takes an application API key in the `x-api-key` header. A key comes from the Business Console or from the registration API on `apx.didit.me`, which emails a 6-character code and returns the key with no browser step. Each application has a primary key with full access and any number of named keys with read or write access per resource, workflow and status limits, an IP allowlist and an expiry date. Named keys are created, rotated and revoked only in the console. The hosted MCP server uses OAuth 2.1 with PKCE and dynamic client registration, with the scopes `didit:management` and `didit:verification`, and accepts no API key.", "pricing": "usage", "pricingNotes": "Pay per completed check from prepaid USD credits, with no contract or minimum and no card needed to sign up. In a workflow, ID verification is $0.15, passive liveness $0.10, face match $0.05, device and IP analysis $0.03 and AML screening $0.20. Until 1 November 2026 each organisation gets 500 free checks a month for each of the first four. From 1 November that becomes $10 of credit a month, with optional Growth ($99 a month) and Scale ($299 a month) plans. Sandbox applications are not billed (https://docs.didit.me/getting-started/pricing, checked 2026-10-08).", "priceSummary": "$0.15 / tx", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI spec, the docs index or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": 156, "popularity": { "githubStars": 0, "npmWeekly": 27338, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://docs.didit.me", "llmsTxt": "https://docs.didit.me/llms.txt", "openapi": "https://docs.didit.me/openapi-25.json", "registryName": "me.didit/mcp", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening", "kyc.business", "kyc.cases" ], "tags": [ "hosted", "api-key", "oauth", "mcp", "webhooks", "openapi", "llms-txt", "free-tier", "no-card", "sandbox", "status-page", "sla", "soc2", "iso27001" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 75, "grade": "BB", "agentReady": true, "rank": 54, "ranked": true, "rankOf": 722, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.", "bestFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "strengths": [ "An account and API key can be created by API at `apx.didit.me/auth/v2/programmatic/register/`, with an emailed code and no browser step", "Public OpenAPI 3.0.0 spec with 256 operations, plus llms.txt and a Markdown copy of every docs page", "Named API keys take read or write access per resource, workflow limits, an IP allowlist and an expiry date, and rotation keeps the old secret for 24 hours", "429 responses carry `Retry-After`, limits are published per scope, and 31 operations document an `Idempotency-Key` header or a reuse rule", "Per-check prices are public, charged only when a check finishes, with 500 free checks a month per core feature until 1 November 2026" ], "weaknesses": [ "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database", "No server-side SDK in any language. The published SDKs are capture clients for web, iOS, Android, React Native and Flutter", "The data processing addendum says the sub-processor list is published at `/terms/sub-processors`, but that address shows the legal index, which says the list is sent after a signed NDA", "Verification data is used for model training by default until an organisation owner turns it off in the console", "The hosted MCP server lists 156 tools to a signed-in user, 23 of them destructive, and role checks run in a mode that logs without hiding tools by default" ], "agentNotes": [ "Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.", "Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.", "Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.", "Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.", "The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75 } ], "editorialScores": { "ergonomics": 69, "maintenance": 82, "payments": 60, "reliability": 80, "schema": 88, "security": 76, "transparency": 53 }, "provenanceScore": 73 }, "connect": { "http": "curl -X POST https://verification.didit.me/v3/session/ \\\n -H \"x-api-key: $DIDIT_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"workflow_id\":\"\u003cWORKFLOW_ID\u003e\",\"vendor_data\":\"user-42\",\"callback\":\"https://myapp.com/return\"}'", "claudeCode": "claude mcp add --transport http didit https://mcp.didit.me/mcp", "config": { "mcpServers": { "didit": { "url": "https://mcp.didit.me/mcp" } } } }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/didit" }, "area": "domain-data", "unitPrices": [ { "item": "ID verification in a workflow (document capture)", "unit": "tx", "usd": 0.15, "note": "500 free a month until 1 November 2026" }, { "item": "Passive liveness in a workflow", "unit": "tx", "usd": 0.1, "note": "500 free a month until 1 November 2026" }, { "item": "Face match 1:1 in a workflow", "unit": "tx", "usd": 0.05, "note": "500 free a month until 1 November 2026" }, { "item": "Device and IP analysis in a workflow", "unit": "tx", "usd": 0.03, "note": "500 free a month until 1 November 2026" }, { "item": "AML screening", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "Proof of address", "unit": "tx", "usd": 0.2, "note": "no free allowance" }, { "item": "KYB registry, per selected company (Lite profile)", "unit": "tx", "usd": 2, "note": "search is charged separately at up to $0.50" } ], "provenance": { "legalEntity": "Didit Identity Spain, S.L.", "domain": "didit.me", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://didit.me/terms/business/", "privacy": "https://didit.me/terms/privacy-policy/", "statusPage": "https://status.didit.me", "changelog": "https://docs.didit.me/changelog/september-2026", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Business Terms and Conditions (updated 23 September 2026) name two contracting entities. Didit Identity Spain, S.L., CIF B22929327, Barcelona, contracts with clients in the EU, EEA, UK and Switzerland, and Didit Identity, Inc., Dover, Delaware, with clients elsewhere.", "The Business Terms are the self-serve contract and include the SLA as Annex 1 and the Data Processing Addendum as Annex 2. A separate Master Services Agreement covers enterprise order forms.", "The Privacy Policy was updated on 7 October 2026 and names the Spanish Data Protection Agency as lead supervisory authority. A Verification Privacy Notice supplements it for end users.", "didit.me/.well-known/security.txt and docs.didit.me/.well-known/security.txt return 404. The Information Security Policy sends reports to security@didit.me.", "The API answers at verification.didit.me, account routes at apx.didit.me and the MCP server at mcp.didit.me, all on the vendor's domain.", "The registration date of didit.me wasn't established. whois returned nothing and rdap.org has no RDAP service for .me." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/didit.json", "live": { "slug": "didit", "probe": { "target": "https://verification.didit.me", "method": "get", "lastAt": "2026-10-08T21:12:08.968530696Z", "lastOk": true, "lastStatus": 404, "lastMs": 54, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 61, "p95ms24h": 88, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.didit.me", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T21:05:59.379981915Z" }, "updatedAt": "2026-10-08T21:12:08.968530696Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "ComplyCube (Teemo Technology Ltd)", "b": "Didit Identity Spain, S.L.", "name": "Vendor" }, { "a": "https://api.complycube.com", "b": "https://verification.didit.me", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, stdio", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "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 Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT", "name": "Licence" }, { "a": "none", "b": "156", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "me.didit/mcp", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-10-08", "name": "Last release" }, { "a": "no date given", "b": "2026-09-23", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-10-07", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "yes, with an opt-out", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "6.2k npm/wk, 292 PyPI/wk", "b": "0 stars, 27k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Didit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, ComplyCube or Didit?" }, { "answer": "ComplyCube needs an API key. Didit takes an API key or an OAuth sign-in.", "question": "Do ComplyCube and Didit need an API key?" }, { "answer": "Yes. ComplyCube has a hosted endpoint at https://api.complycube.com and Didit at https://verification.didit.me.", "question": "Can an agent call ComplyCube and Didit without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "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, 88 against 78", "Agent ergonomics, 69 against 60", "Security \u0026 auth, 76 against 52", "Payments \u0026 pricing, 60 against 27", "Maintenance \u0026 community, 82 against 74" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine", "Free to start without a card" ], "goodFor": "A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.", "slug": "didit", "watchFor": "Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database" } ], "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-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-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/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-middesk.json", "title": "Didit vs Middesk", "url": "https://www.anchorterminal.com/compare/didit-vs-middesk" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-persona.json", "title": "Didit vs Persona", "url": "https://www.anchorterminal.com/compare/didit-vs-persona" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-sumsub.json", "title": "Didit vs Sumsub", "url": "https://www.anchorterminal.com/compare/didit-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/didit-vs-trulioo.json", "title": "Didit vs Trulioo", "url": "https://www.anchorterminal.com/compare/didit-vs-trulioo" }, { "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/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-didit.json", "title": "ComplyAdvantage vs Didit", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-didit" } ], "scores": [ { "by": 4, "complycube": 84, "didit": 80, "edge": "complycube", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 10, "complycube": 78, "didit": 88, "edge": "didit", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 9, "complycube": 60, "didit": 69, "edge": "didit", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 24, "complycube": 52, "didit": 76, "edge": "didit", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 33, "complycube": 27, "didit": 60, "edge": "didit", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 8, "complycube": 74, "didit": 82, "edge": "didit", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 0, "complycube": 63, "didit": 63, "edge": "", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Didit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. Both do kyc identity.", "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.", "didit": "A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/complycube-vs-didit", "json": "https://www.anchorterminal.com/compare/complycube-vs-didit.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/complycube-vs-didit.md", "slim": "https://www.anchorterminal.com/compare/complycube-vs-didit.min.md" }, "markdown": "Didit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. Both do kyc identity.\n\n- ComplyCube: grade B, 63.7/100, rank #299 of 722. Markdown https://www.anchorterminal.com/tools/complycube.md · JSON https://www.anchorterminal.com/api/v1/tools/complycube.json\n- Didit: grade BB, 75/100, rank #54 of 722. Markdown https://www.anchorterminal.com/tools/didit.md · JSON https://www.anchorterminal.com/api/v1/tools/didit.json\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\nWatch for: One API key per environment with no scopes. The docs say keys carry many privileges\n\n### Didit (BB)\n\nGood for: A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.\n\nAhead on:\n- Schema \u0026 documentation, 88 against 78\n- Agent ergonomics, 69 against 60\n- Security \u0026 auth, 76 against 52\n- Payments \u0026 pricing, 60 against 27\n- Maintenance \u0026 community, 82 against 74\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n- Free to start without a card\n\nWatch for: Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database\n\n\n## Score by category\n\n| Category | Weight | ComplyCube | Didit | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 80 | ComplyCube +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 88 | Didit +10 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 69 | Didit +9 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 76 | Didit +24 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 27 | 60 | Didit +33 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 82 | Didit +8 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 63 | even |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **75 · BB** | |\n\n## Facts side by side\n\n| Fact | ComplyCube | Didit |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | ComplyCube (Teemo Technology Ltd) | Didit Identity Spain, S.L. |\n| Hosted endpoint | `https://api.complycube.com` | `https://verification.didit.me` |\n| Transports | HTTP | HTTP, Streamable HTTP, stdio |\n| Auth | API key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\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 Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT |\n| Tools exposed | none | 156 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `me.didit/mcp` |\n| Last release | 2026-10-06 | 2026-10-08 |\n| Terms last updated | no date given | 2026-09-23 |\n| Privacy policy last updated | no date given | 2026-10-07 |\n| Customer content may train models | not found in the text | yes, with an opt-out |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 6.2k npm/wk, 292 PyPI/wk | 0 stars, 27k npm/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**Didit.** A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.\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### Didit\n\n1. Register with `POST https://apx.didit.me/auth/v2/programmatic/register/`, then `verify-email` with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.\n2. Send the key as `x-api-key` to `https://verification.didit.me/v3/`. The JWT from registration works only on `apx.didit.me`.\n3. Create a workflow before `POST /v3/session/`. `workflow_id` is the only required field, and an unfinished session with the same `vendor_data` is returned again.\n4. Read results from webhooks and use `GET /v3/session/{sessionId}/decision/` for back-fill. Every per-feature result is a plural array.\n5. The MCP server at `https://mcp.didit.me/mcp` takes OAuth sign-in only, never an API key. Approve `didit:verification` alone when the task doesn't change workflows or keys.\n\n## Questions\n\n### Which is better for AI agents, ComplyCube or Didit?\n\nDidit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories.\n\n### Do ComplyCube and Didit need an API key?\n\nComplyCube needs an API key. Didit takes an API key or an OAuth sign-in.\n\n### Can an agent call ComplyCube and Didit without installing anything?\n\nYes. ComplyCube has a hosted endpoint at https://api.complycube.com and Didit at https://verification.didit.me.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/complycube-vs-didit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/complycube-vs-didit.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"complycube\", \"b\": \"didit\"}`. From a terminal: `anchor compare complycube didit`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/complycube.json and https://www.anchorterminal.com/api/v1/tools/didit.json\n\n## Other comparisons with ComplyCube or Didit\n\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 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- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)\n- [Didit vs Middesk](https://www.anchorterminal.com/compare/didit-vs-middesk.md)\n- [Didit vs Persona](https://www.anchorterminal.com/compare/didit-vs-persona.md)\n- [Didit vs Sumsub](https://www.anchorterminal.com/compare/didit-vs-sumsub.md)\n- [Didit vs Trulioo](https://www.anchorterminal.com/compare/didit-vs-trulioo.md)\n- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)\n- [ComplyAdvantage vs ComplyCube](https://www.anchorterminal.com/compare/complyadvantage-vs-complycube.md)\n- [ComplyAdvantage vs Didit](https://www.anchorterminal.com/compare/complyadvantage-vs-didit.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": "ComplyCube vs Didit", "url": "" } ], "description": "Didit scores 75 (BB) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "ComplyCube B 63.7", "Didit BB 75", "scores" ], "h1": "ComplyCube vs Didit", "image": "https://www.anchorterminal.com/assets/og/compare-complycube-vs-didit.png", "path": "/compare/complycube-vs-didit", "published": "2026-10-01", "section": "tools", "title": "ComplyCube vs Didit for AI agents, B 63.7 vs BB 75 | Anchor Terminal", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/complycube-vs-didit" }, "tokens": { "markdown": 2200, "slim": 730 }, "version": 1 }