{ "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": "Plaid Identity Verification scores 67.1 (B) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. ComplyCube leads on reliability and payments \u0026 pricing.", "b": { "slug": "plaid-identity-verification", "name": "Plaid Identity Verification", "vendor": "Plaid Inc.", "vendorUrl": "https://plaid.com/products/identity-verification/", "kind": "http-api", "category": "identity-verification", "summary": "Plaid Identity Verification checks a person against data sources, identity documents, selfies with liveness and SMS, with risk scoring and optional Monitor watchlist screening. Sessions run in Plaid Link or through a backend-only API flow.", "url": "https://www.anchorterminal.com/tools/plaid-identity-verification", "markdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json", "repo": "https://github.com/plaid/plaid-openapi", "license": "Proprietary service under Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "plaid" }, { "registry": "pypi", "name": "plaid-python" } ], "auth": "api-key", "authNotes": "`client_id` and `secret` in the JSON body of each POST to https://sandbox.plaid.com or https://production.plaid.com, with a separate secret per environment. No scopes. Sandbox for Identity Verification is enabled self-serve from the Dashboard Products page (since 12 August 2026). Production needs a product access request, and the integrating company must be based in the US, Canada or the UK (checked 2026-10-14).", "pricing": "paid", "pricingNotes": "No public prices. Each session is billed an Anti-Fraud Engine fee plus fees for data source verification (by country), document checks and selfie checks, and retries are billed as new sessions. Exact rates appear after applying for Production. Sandbox is free (https://plaid.com/docs/account/billing/, checked 2026-10-14).", "priceSummary": "Paid", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Identity Verification docs, the API reference or the pricing page (checked 2026-10-14).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1238045, "pypiWeekly": 656200, "asOf": "2026-10-14" }, "docsUrl": "https://plaid.com/docs/identity-verification/", "llmsTxt": "https://plaid.com/llms.txt", "openapi": "https://raw.githubusercontent.com/plaid/plaid-openapi/master/2020-09-14.yml", "capabilities": [ "kyc.identity", "kyc.documents", "kyc.screening" ], "tags": [ "hosted", "api-key", "openapi", "llms-txt", "webhooks", "sandbox", "status-page", "python", "typescript", "go", "java", "ruby", "bug-bounty" ], "lastRelease": "2026-10-13", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 278, "ranked": true, "rankOf": 1076, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-14" }, "negative": 0, "verdict": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.", "bestFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "strengths": [ "Four typed endpoints in the public OpenAPI file, with llms.txt and Markdown docs", "Backend-only flow runs data source checks from user data with no Link session", "`is_idempotent` on create returns the existing session instead of making a second", "Six dated Identity Verification changelog entries between 9 July and 13 October 2026", "Self-serve Sandbox since 12 August 2026, with sample identities for test outcomes" ], "weaknesses": [ "No public prices. Rates appear only after a Production application", "One team secret reaches every Plaid product, with no scopes or read-only key", "Integrating companies must be based in the US, Canada or the UK", "Data stays only while the contract is active, and access to past sessions ends with it", "Rate-limit and error pages sit under a path robots.txt disallows, so we didn't read them" ], "agentNotes": [ "Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session", "Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link", "Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed", "Don't issue retries casually. Each retry is a new session billed again", "Enable Sandbox for Identity Verification on the Dashboard Products page before the first call" ], "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": 67.1 } ], "editorialScores": { "ergonomics": 75, "maintenance": 83, "payments": 15, "reliability": 68, "schema": 91, "security": 61, "transparency": 57 }, "provenanceScore": 97 }, "connect": { "http": "curl -X POST https://sandbox.plaid.com/identity_verification/create \\\n-H 'Content-Type: application/json' \\\n-d '{\n \"client_user_id\": \"user-sandbox-b0e2c4ee-a763-4df5-bfe9-46a46bce993d\",\n \"client_id\": \"${PLAID_CLIENT_ID}\",\n \"secret\": \"${PLAID_SECRET}\",\n \"is_shareable\": true,\n \"template_id\": \"idvtmp_52xR9LKo77r1Np\",\n \"gave_consent\": true\n}'" }, "letme": { "capability": "https://letme.dev/kyc.identity", "tool": "https://letme.dev/plaid-identity-verification" }, "sameCompany": [ "plaid" ], "area": "domain-data", "provenance": { "legalEntity": "Plaid Inc.", "domain": "plaid.com", "domainRegistered": "1995-08-16", "endpointOnVendorDomain": true, "terms": "https://plaid.com/legal/#developer-policy", "privacy": "https://plaid.com/legal/#privacy-statement", "statusPage": "https://status.plaid.com", "changelog": "https://plaid.com/docs/changelog/", "securityTxt": "valid", "checked": "2026-10-14", "notes": [ "Same entity, legal pages and status page as the plaid listing. Plaid Financial Ltd and Plaid, B.V. cover the UK and the EEA.", "plaid.com/.well-known/security.txt lists HackerOne and security@plaid.com and expires 2026-12-31.", "plaid.com was registered in 1995, before Plaid was founded." ], "score": 97 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/plaid-identity-verification.json", "live": { "slug": "plaid-identity-verification", "vendorStatus": { "page": "https://status.plaid.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-14T09:39:36.297248466Z" }, "updatedAt": "2026-10-14T09:39:36.297248466Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "ComplyCube (Teemo Technology Ltd)", "b": "Plaid Inc.", "name": "Vendor" }, { "a": "https://api.complycube.com", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API 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 Plaid's developer policy and end-user terms. The OpenAPI file and client libraries 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-10-13", "name": "Last release" }, { "a": "no date given", "b": "2025-12-01", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-12-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "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": "1.2M npm/wk, 656k PyPI/wk", "name": "Popularity" } ], "faq": [ { "answer": "Plaid Identity Verification scores 67.1 (B) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. ComplyCube leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, ComplyCube or Plaid Identity Verification?" }, { "answer": "Both need an API key.", "question": "Do ComplyCube and Plaid Identity Verification need an API key?" }, { "answer": "ComplyCube has a hosted endpoint at https://api.complycube.com. No hosted endpoint is listed for Plaid Identity Verification.", "question": "Can an agent call ComplyCube and Plaid Identity Verification without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 84 against 68", "Payments \u0026 pricing, 27 against 15" ], "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, 91 against 78", "Agent ergonomics, 75 against 60", "Security \u0026 auth, 61 against 52", "Maintenance \u0026 community, 83 against 74", "Transparency \u0026 trust, 77 against 63" ], "also": null, "goodFor": "US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.", "slug": "plaid-identity-verification", "watchFor": "No public prices. Rates appear only after a Production application" } ], "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-plaid-identity-verification.json", "title": "Alloy vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/alloy-vs-plaid-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-entrust-identity-verification.json", "title": "ComplyCube vs Entrust Identity Verification (formerly Onfido)", "url": "https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification" }, { "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-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-plaid-identity-verification.json", "title": "Didit vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification" }, { "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/jumio-vs-plaid-identity-verification.json", "title": "Jumio vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification.json", "title": "Middesk vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.json", "title": "Persona vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.json", "title": "Plaid Identity Verification vs Shufti", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.json", "title": "Plaid Identity Verification vs Socure RiskOS", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.json", "title": "Plaid Identity Verification vs Stripe Identity", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.json", "title": "Plaid Identity Verification vs Sumsub", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.json", "title": "Plaid Identity Verification vs Trulioo", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.json", "title": "Plaid Identity Verification vs Veriff", "url": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff" }, { "json": "https://www.anchorterminal.com/compare/plaid-identity-verification-vs-vouched.json", "title": "Plaid Identity Verification vs Vouched", "url": "https://www.anchorterminal.com/compare/plaid-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-plaid-identity-verification.json", "title": "ComplyAdvantage vs Plaid Identity Verification", "url": "https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-identity-verification" } ], "scores": [ { "by": 16, "complycube": 84, "edge": "complycube", "key": "reliability", "name": "Reliability", "plaid-identity-verification": 68, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "complycube": 78, "edge": "plaid-identity-verification", "key": "schema", "name": "Schema \u0026 documentation", "plaid-identity-verification": 91, "weight": 13 }, { "by": 15, "complycube": 60, "edge": "plaid-identity-verification", "key": "ergonomics", "name": "Agent ergonomics", "plaid-identity-verification": 75, "weight": 13 }, { "by": 9, "complycube": 52, "edge": "plaid-identity-verification", "key": "security", "name": "Security \u0026 auth", "plaid-identity-verification": 61, "weight": 14 }, { "by": 12, "complycube": 27, "edge": "complycube", "key": "payments", "name": "Payments \u0026 pricing", "plaid-identity-verification": 15, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "complycube": 74, "edge": "plaid-identity-verification", "key": "maintenance", "name": "Maintenance \u0026 community", "plaid-identity-verification": 83, "weight": 7 }, { "by": 14, "complycube": 63, "edge": "plaid-identity-verification", "key": "transparency", "name": "Transparency \u0026 trust", "plaid-identity-verification": 77, "weight": 7 } ], "summary": "Plaid Identity Verification scores 67.1 (B) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. ComplyCube leads on reliability and payments \u0026 pricing. 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.", "plaid-identity-verification": "Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification", "json": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.md", "slim": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.min.md" }, "markdown": "Plaid Identity Verification scores 67.1 (B) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. ComplyCube leads on reliability and payments \u0026 pricing. 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- Plaid Identity Verification: grade B, 67.1/100, rank #278 of 1076. Markdown https://www.anchorterminal.com/tools/plaid-identity-verification.md · JSON https://www.anchorterminal.com/api/v1/tools/plaid-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 68\n- Payments \u0026 pricing, 27 against 15\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### Plaid Identity Verification (B)\n\nGood for: US, Canadian and UK companies that want KYC with data source checks, documents and selfies, especially those already on Plaid or wanting Monitor screening in the same flow.\n\nAhead on:\n- Schema \u0026 documentation, 91 against 78\n- Agent ergonomics, 75 against 60\n- Security \u0026 auth, 61 against 52\n- Maintenance \u0026 community, 83 against 74\n- Transparency \u0026 trust, 77 against 63\n\nWatch for: No public prices. Rates appear only after a Production application\n\n\n## Score by category\n\n| Category | Weight | ComplyCube | Plaid Identity Verification | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 84 | 68 | ComplyCube +16 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 91 | Plaid Identity Verification +13 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 75 | Plaid Identity Verification +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 61 | Plaid Identity Verification +9 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 27 | 15 | ComplyCube +12 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 74 | 83 | Plaid Identity Verification +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 63 | 77 | Plaid Identity Verification +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.7 · B** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | ComplyCube | Plaid Identity Verification |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | ComplyCube (Teemo Technology Ltd) | Plaid Inc. |\n| Hosted endpoint | `https://api.complycube.com` | no (local only) |\n| Transports | HTTP | HTTP |\n| Auth | API key | API 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 Plaid's developer policy and end-user terms. The OpenAPI file and client libraries are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-06 | 2026-10-13 |\n| Terms last updated | no date given | 2025-12-01 |\n| Privacy policy last updated | no date given | 2025-12-01 |\n| Customer content may train models | not found in the text | not found in the text |\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 | 1.2M npm/wk, 656k 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**Plaid Identity Verification.** Plaid Identity Verification has four typed endpoints in Plaid's public OpenAPI file, an idempotent create, a backend-only flow for data source checks and frequent changelog entries. Prices appear only after applying for Production, the secret has no scopes, and the rate-limit and error pages are disallowed to crawlers.\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### Plaid Identity Verification\n\n1. Pass `is_idempotent: true` to /identity_verification/create so a retry returns the existing session\n2. Use the backend-only flow (data source template, `gave_consent: true`) when you already hold the user's details. Documents and selfies need the person in Link\n3. Wait for the STATUS_UPDATED webhook or poll /identity_verification/get. Link's onSuccess doesn't mean the user passed\n4. Don't issue retries casually. Each retry is a new session billed again\n5. Enable Sandbox for Identity Verification on the Dashboard Products page before the first call\n\n## Questions\n\n### Which is better for AI agents, ComplyCube or Plaid Identity Verification?\n\nPlaid Identity Verification scores 67.1 (B) on agent readiness against ComplyCube's 63.7 (B), and leads in 5 of 7 scored categories. ComplyCube leads on reliability and payments \u0026 pricing.\n\n### Do ComplyCube and Plaid Identity Verification need an API key?\n\nBoth need an API key.\n\n### Can an agent call ComplyCube and Plaid Identity Verification without installing anything?\n\nComplyCube has a hosted endpoint at https://api.complycube.com. No hosted endpoint is listed for Plaid Identity Verification.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.json, and with the fewest tokens: https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"complycube\", \"b\": \"plaid-identity-verification\"}`. From a terminal: `anchor compare complycube plaid-identity-verification`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/complycube.json and https://www.anchorterminal.com/api/v1/tools/plaid-identity-verification.json\n\n## Other comparisons with ComplyCube or Plaid Identity Verification\n\n- [Alloy vs ComplyCube](https://www.anchorterminal.com/compare/alloy-vs-complycube.md)\n- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)\n- [ComplyCube vs Didit](https://www.anchorterminal.com/compare/complycube-vs-didit.md)\n- [ComplyCube vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/complycube-vs-entrust-identity-verification.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 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 Plaid Identity Verification](https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.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- [Jumio vs Plaid Identity Verification](https://www.anchorterminal.com/compare/jumio-vs-plaid-identity-verification.md)\n- [Middesk vs Plaid Identity Verification](https://www.anchorterminal.com/compare/middesk-vs-plaid-identity-verification.md)\n- [Persona vs Plaid Identity Verification](https://www.anchorterminal.com/compare/persona-vs-plaid-identity-verification.md)\n- [Plaid Identity Verification vs Shufti](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-shufti.md)\n- [Plaid Identity Verification vs Socure RiskOS](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-socure-riskos.md)\n- [Plaid Identity Verification vs Stripe Identity](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-stripe-identity.md)\n- [Plaid Identity Verification vs Sumsub](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-sumsub.md)\n- [Plaid Identity Verification vs Trulioo](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-trulioo.md)\n- [Plaid Identity Verification vs Veriff](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-veriff.md)\n- [Plaid Identity Verification vs Vouched](https://www.anchorterminal.com/compare/plaid-identity-verification-vs-vouched.md)\n- [ComplyAdvantage vs ComplyCube](https://www.anchorterminal.com/compare/complyadvantage-vs-complycube.md)\n- [ComplyAdvantage vs Plaid Identity Verification](https://www.anchorterminal.com/compare/complyadvantage-vs-plaid-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 Plaid Identity Verification", "url": "" } ], "description": "Plaid Identity Verification scores 67.1 (B) to ComplyCube's 63.7 (B) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ComplyCube B 63.7", "Plaid Identity Verification B 67.1", "scores" ], "h1": "ComplyCube vs Plaid Identity Verification", "image": "https://www.anchorterminal.com/assets/og/compare-complycube-vs-plaid-identity-verification.png", "path": "/compare/complycube-vs-plaid-identity-verification", "published": "2026-10-01", "section": "tools", "title": "ComplyCube vs Plaid Identity Verification for AI agents (2026)", "toc": null, "updated": "2026-10-14", "url": "https://www.anchorterminal.com/compare/complycube-vs-plaid-identity-verification" }, "tokens": { "markdown": 2800, "slim": 730 }, "version": 1 }