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