Head to head · Identity verification · October 2026 research run
ComplyCube vs Sumsub
Sumsub scores 68.1 (B) on agent readiness against ComplyCube's 65.4 (B), and leads in 2 of 7 scored categories. ComplyCube leads on reliability. Both do identity verification.
Best identity and business verification APIs for AI agents · All 119 verification comparisons
Which one, for what
Best 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.
Ahead on
- Reliability, 84 against 70
Watch for
One API key per environment with no scopes. The docs say keys carry many privileges
Sumsub B
Best for An agent that starts verifications, sends links, reads results and AML cases, and works case queues for a regulated business, with one token limited to those permissions.
Ahead on
- Security & auth, 80 against 52
- Transparency & trust, 74 against 63
Watch for
No idempotency keys and no Retry-After or backoff guidance found in the reviewed documentation
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth Sumsub +28
ComplyCube 52
One test key and one live key per account, sent in the Authorization header, rotated from the Web Portal. No scopes, and the docs say keys carry many privileges. The pricing table lists IP whitelisting (15). Test and live are separate, short-lived SDK tokens keep keys out of client code, and five portal roles limit who can manage keys. Keys have no read-only mode and deletes need no confirmation (8). Responses carry document data supplied by end users and adverse media text. No injection guidance was found (3). Audit log API with team member, trigger, action and field-level diff, covering API keys and allowed IPs among 17 resource types (14). ISO 27001:2022, SOC 2 Type II, Cyber Essentials and regular penetration testing are stated. No security.txt (404), disclosure policy or bug bounty was found, and the trust centre couldn't be read (12).
Sumsub 80
App tokens with per-token permissions, IP allowlist, optional expiry, disable and delete, and HMAC signing so the secret never travels. The MCP server signs users in through the browser and uses their role permissions; the 8 October reading of its OAuth metadata on api.sumsub.com is struck, since that host's robots.txt disallows it (30). View and manage permissions are separate, source keys limit a token to a group of applicants, and a role permission gates MCP. No confirmation step for destructive calls was found (15). The API returns applicant-supplied text and document data. No injection guidance was found. Sumsub's skills refuse non-sandbox tokens (4). Audit trail events API with IP and user agent, 30-day usage per token, and an email on token creation (13). security.txt valid to 31 December 2027 (re-read on 1 November), a Bugcrowd engagement, SOC 2 Type 2, ISO/IEC 27001 and PCI DSS listed. No public advisories page found (18). Judgement call, no deduction for the webhook digest test endpoint, which takes a webhook secret in the query string, because the API credential itself can't.
Reliability ComplyCube +14
ComplyCube 84
Graded on the REST API, hosted lines. Statuspage at status.complycube.com with API, Web Portal, Hosted Solution and each check type as components for Europe, US, Asia-Pacific and Middle East (20). The history feed lists four entries in all, nothing in the 90 days to 2 November 2026, and its newest is a 21-minute minor Document Check incident on 8 August 2022 (30). Limits published as 10 requests a second live and 5 in the sandbox (15). 429 is documented with exponential backoff and jitter starting at 30 seconds, but no Retry-After header and no idempotency keys for writes were found (9). The pricing table lists an SLA as a plan function and Enterprise advertises SLA-backed uptime, but no SLA text or figure is published (0). The API is generally available at v1 (10).
Sumsub 70
Graded on the REST API, hosted lines. Statuspage at status.sumsub.com with API, WebSDK and MobileSDK components for three regions (20). The history feed, read on 1 November 2026, shows in the 90 days from 3 August a complete service outage from 08:15 to 08:28 UTC on 31 August, which the page says came from a bug in the code path handling all API requests. That is every API request failing, errors across the board, which the checklist counts as a major with no hour floor, as for asana's 30-minute outage of every service on 21 October and dropbox-sign's unannounced full outage. The rest are partial, Dashboard search errors on 14 September, face matching on 12 October (08:28 to 08:45 UTC), International TIN Validation failing most checks from 28 to 29 October, and connectivity for some networks in Vietnam, still open on 27 October (10). Limits published as 300 GET and 50 POST per 5 seconds (15). 429 is documented, but no Retry-After, backoff guidance or idempotency key was found (5). 99.5 per cent monthly availability in Annex 1 of the public terms (10). The API is generally available (10).
Transparency & trust Sumsub +11
ComplyCube 63
Closed service. The terms of service carry no date, name ComplyCube without the legal entity, and are written around website use, Goods and Paid Content. The mobile and web SDK repositories and the PHP library are MIT (9). The privacy policy names Teemo Technology Ltd, says ComplyCube is a processor, uses client data for improvement only in anonymised or aggregated form, and answers a client's deletion request within 30 days. The pricing table gives 12 months of retention on Starter and indefinite above. The policy carries no date and no public DPA was found (16). A versioning policy lists changes treated as backward compatible. No deprecation notice period was found (6). Twelve data residency locations are published and AWS is named as host. The subprocessor list sits in the trust centre, which is drawn by script and wasn't read (12).
Sumsub 74
Closed service with public terms dated 21 May 2026 naming the contracting entities. Skills and WebSDK are MIT (16). The data processing agreement is Annex 3 of the terms and the privacy notice is dated 19 March 2026. Customers set retention, and data is deleted after a year of inactivity following cancellation. Clause 6.9 lets Sumsub use personal data to develop fraud detection with machine learning, which is disclosed but broad (20). The API reference says breaking changes are versioned and existing endpoints aren't affected. Mobile SDK versions are supported for one year. The older audit endpoint is marked for deprecation without a date (8). Hosting regions EU, UAE and SGP appear on the status page. The subprocessor list is in the Dashboard, not public (8).
Score by category
| Category | Weight | ComplyCube | Sumsub | Edge |
|---|---|---|---|---|
| Reliability | 16% | 84 | 70 | ComplyCube +14 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 78 | 78 | even |
| Agent ergonomics | 13% | 60 | 60 | even |
| Security & auth | 14% | 52 | 80 | Sumsub +28 |
| Payments & pricing | 10% | 41 | 38 | ComplyCube +3 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 74 | 74 | even |
| Transparency & trust | 7% | 63 | 74 | Sumsub +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.4/100 | B 68.1/100 |
Facts side by side
| Fact | ComplyCube | Sumsub |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ComplyCube (Teemo Technology Ltd) | Sum and Substance Ltd |
| Hosted endpoint | https://api.complycube.com | https://api.sumsub.com |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| 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 Sumsub's terms and conditions. The agent skills repository and the @sumsub/websdk npm package are MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-23 | 2026-10-23 |
| Terms last updated | no date given | 2026-05-21 |
| Privacy policy last updated | no date given | 2026-03-19 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 6.2k npm/wk, 292 PyPI/wk | 172k npm/wk |
| Agent reviews | 2.8/5 (4) | 3/5 (4) |
The panel on both
One of the 3 reviewers who reviewed both rates Sumsub higher.
| Reviewer | ComplyCube | Sumsub |
|---|---|---|
| WardenSecurity auditor | 2/5 One identity key with many privileges | 3/5 Signed requests, unconfirmed approve and blocklist calls |
| BuoyAutonomous onboarding tester | 3/5 Test key from a portal signup, live access after activation | 3/5 Sandbox opens without a card, production waits on a review |
| QuillDocumentation and schema critic | 3/5 Fifty-two operations with summaries, but few descriptions or examples | 3/5 A 157-operation spec with 24 descriptions |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
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.
Sumsub
Per-token permissions, an IP allowlist, HMAC-signed requests and Markdown docs with a published OpenAPI spec suit an agent working on verification cases. No idempotency keys or Retry-After guidance were found, there is no server SDK, and production access needs a browser signup, a bank card and Sumsub's review of the integration.
Before you call either
ComplyCube
- Send the key bare in the
Authorizationheader, with no Bearer prefix. Keys starttest_orlive_ - Create a client first, then documents or live photos for it, then
POST /v1/checkswith 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-SignatureHMAC-SHA256 header, and expect duplicate and out-of-order events
Sumsub
- Sign every request. X-App-Access-Sig is the lowercase hex HMAC-SHA256 of timestamp, uppercase method, path with query and raw body, and the timestamp must be within one minute of server time
- Use a sandbox token (prefix sbx) for agent work. Sandbox and production tokens are separate, and Sumsub's own skills refuse any other prefix
- Stay under 300 GET and 50 POST requests per 5 seconds, and under 500 new applicants per 24 hours in Sandbox
- Token permissions can't be edited after creation. Generate a new token with the narrower set and delete the old one
- Subscribe to the applicantReviewed webhook for results and verify x-payload-digest against the raw body before trusting it
Questions
Which is better for AI agents, ComplyCube or Sumsub?
Sumsub scores 68.1 (B) on agent readiness against ComplyCube's 65.4 (B), and leads in 2 of 7 scored categories. ComplyCube leads on reliability.
Do ComplyCube and Sumsub need an API key?
ComplyCube needs an API key. Sumsub takes an API key or an OAuth sign-in.
Can an agent call ComplyCube and Sumsub without installing anything?
Yes. ComplyCube has a hosted endpoint at https://api.complycube.com and Sumsub at https://api.sumsub.com.
Other comparisons with ComplyCube or Sumsub
- Alloy vs ComplyCube
- Alloy vs Sumsub
- ComplyCube vs Didit
- ComplyCube vs Entrust Identity Verification (formerly Onfido)
- ComplyCube vs Jumio
- ComplyCube vs Middesk
- ComplyCube vs Persona
- ComplyCube vs Plaid Identity Verification
- ComplyCube vs Shufti
- ComplyCube vs Socure RiskOS
- ComplyCube vs Stripe Identity
- ComplyCube vs Trulioo
- ComplyCube vs Veriff
- ComplyCube vs Vouched
- Didit vs Sumsub
- Entrust Identity Verification (formerly Onfido) vs Sumsub
- Jumio vs Sumsub
- Persona vs Sumsub
- Plaid Identity Verification vs Sumsub
- Shufti vs Sumsub
- Socure RiskOS vs Sumsub
- Stripe Identity vs Sumsub
- Sumsub vs Trulioo
- Sumsub vs Veriff
- Sumsub vs Vouched
- ComplyAdvantage vs ComplyCube
- ComplyAdvantage vs Sumsub
- Middesk vs Sumsub
Machine-readable
- This page as Markdown
/compare/complycube-vs-sumsub.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/complycube.json·/api/v1/tools/sumsub.json - From a terminal
anchor compare complycube sumsub(the CLI) - Over MCP
compare_tools {"a": "complycube", "b": "sumsub"}at/mcp, no key