Head to head · Business verification · October 2026 research run

Middesk vs Sumsub

Sumsub scores 68.1 (B) on agent readiness against Middesk's 57.5 (C), and leads in 6 of 7 scored categories. Both do business verification.

Best identity and business verification APIs for AI agents · All 119 verification comparisons

Which one, for what

Middesk C

Best for An agent onboarding or re-checking US businesses for a bank, lender or marketplace that already holds a Middesk contract, with registry, TIN, sanctions and lien data in one object.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No public price. Fees are set in an order form, and every docs page ends with a prompt to contact sales

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

  • Reliability, 70 against 62
  • Security & auth, 80 against 56
  • Payments & pricing, 38 against 15
  • Maintenance & community, 74 against 64
  • Transparency & trust, 74 against 62

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 +24

Middesk 56

Revocable API keys split by environment, sub-account keys managed through the API, and OAuth 2.0 with read_only and read_write scopes and a revoke endpoint. OAuth access tokens don't expire, there's no consent screen, and an API key carries full account access (24). A read_only token is limited to GET, the sandbox is a separate host and key, and an IP allowlist applies. The MCP server advertises only read_write, and no approval step for billable writes was found in the API (12). Responses carry text from websites, adverse media and an LLM-written analyst summary, and no guidance on prompt injection was found (3). Actions record who changed a business and what changed, and a timeline endpoint lists events. No log of API calls for the operator was found (7). SOC 2 Type II audited annually and a Vanta trust centre. No security.txt, disclosure policy or bug bounty found (10). All per the 8 October check, not re-read on 4 November.

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.

Payments & pricing Sumsub +23

Middesk 15

No x402, MPP or L402 (0). No public price. Fees are set in an order form and middesk.com/pricing returns 404 (0). A sandbox with mock data comes with an account, and the vendor's plugin README says trial accounts issue test keys. We couldn't establish how a trial is opened or whether it needs a card, so half credit (10). Access starts with a demo request and a dashboard sign-in (0). All per the 8 October check, not re-read on 4 November. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 10 is 15.

Sumsub 38

No x402, MPP or L402 (0). Per-verification prices are public for two plans ($1.35 and $1.85, with $149 and $299 monthly minimums). Business verification, transaction monitoring and fraud prevention are quoted by sales (15). Sandbox mode is free without a card and returns test results only. The trial of 50 real checks asks for bank card details (10). Signup, token creation and MCP sign-in all need a person in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

Transparency & trust Sumsub +12

Middesk 62

Closed service with public terms last updated 21 August 2026, and MIT plugins (15). The terms bar training generative AI models on customer data and limit ML training to de-identified data. The privacy policy of 2 November 2025 keeps data as long as necessary with no periods, and no public DPA was found (14). The API change policy promises advance notice and an opt-out for breaking changes without a notice period, the terms give 60 days' notice before data is withdrawn, and the changelog labels breaking changes (10). Socure is named for identity checks. No subprocessor list or data location was found outside the trust centre, which we couldn't read (4). All per the 8 October check, not re-read on 4 November.

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).

Maintenance & community Sumsub +10

Middesk 64

Latest changelog entry 5 October 2026, 30 days before 4 November, per the 8 October check, not re-read on 4 November (30). Nine dated entries between 20 July and 5 October, at least three of them after 6 August (20). Closed service with a weekly changelog, a help centre and support in standard hours under the terms. No public issue tracker or community channel was found (9). No official SDK, and the MCP server isn't in the official registry. The middesk/plugins repository (plugins at 0.1.0, no tags or releases) has five commits from 16 September to 8 October 2026, the last two editing the verify skills (3). No published packages, and the plugins repository has no CI (2).

Sumsub 74

The changelog's latest entry covers 19 to 23 October 2026, and agent skills 1.6.0 shipped on 30 October (30). Weekly changelog entries through August, September and October (20). Closed service with a dated changelog, a support site and a feedback tool in the MCP server. Response times weren't measurable (10). The WebSDK on npm was at 2.9.0 per the 8 October check (npm didn't resolve on 1 November) and mobile SDKs have their own changelogs (MobileSDK 1.47 in the week of 19 October), but there is no server SDK and no entry in the official MCP registry (8). The skills repository has had four releases since 3 August (1.3.0 to 1.6.0), and the signing examples took dependency updates until 11 June 2026. No CI workflows in either (6).

Reliability Sumsub +8

Middesk 62

Graded on the REST API with the hosted-service lines, per the 8 October check, not re-read on 4 November. Middesk's website terms bar any automated use of the Site, including robots and data gathering tools, and this run pauses such hosts pending a ruling. status.middesk.com is a Statuspage site on Middesk's own domain, per the 8 October check (20). The 8 October incident reading came from the page's /api/ path, which its robots.txt disallows, so it is struck, and with nothing readable today the window from 6 August is unread (5). 20 requests a second per customer is published (15). 429 is a documented status with Retry-After for sandbox business creation, and safe retries are documented for sub-account creation (external_id) and lien continuations. No general idempotency key was found, so this is safe-retry guidance on some writes (12). No SLA in the public terms (0). REST v1 is generally available (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).

Score by category

CategoryWeightMiddeskSumsubEdge
Reliability16%6270Sumsub +8
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8278Middesk +4
Agent ergonomics13%5660Sumsub +4
Security & auth14%5680Sumsub +24
Payments & pricing10%1538Sumsub +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6474Sumsub +10
Transparency & trust7%6274Sumsub +12
Negative events≤1500
TotalC 57.5/100B 68.1/100

Facts side by side

FactMiddeskSumsub
KindHTTP APIHTTP API
VendorMiddesk, Inc.Sum and Substance Ltd
Hosted endpointhttps://api.middesk.com/v1https://api.sumsub.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under Middesk's Business Verification Terms and Conditions. The Claude Code and Codex plugins on GitHub are MITProprietary service under Sumsub's terms and conditions. The agent skills repository and the @sumsub/websdk npm package are MIT
Tools exposed11none
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-052026-10-23
Terms last updatedno date given2026-05-21
Privacy policy last updatedno date given2026-03-19
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesyes
Popularity2 stars172k npm/wk
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

Middesk

A public OpenAPI 3.1 contract for 87 operations, llms.txt, Markdown docs and a dated weekly changelog make the REST API readable to an agent, and OAuth has a read-only scope. Access is sales-led. No price, self-serve signup or official SDK was found, and the hosted MCP server rejects sandbox keys.

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

Middesk

  1. Match the key to the host. mk_test keys work only at https://api-sandbox.middesk.com/v1 and mk_live keys only at https://api.middesk.com/v1
  2. Name the orders on POST /v1/businesses. Omitting them places a verification order plus every package the account runs automatically, all billed
  3. Send address_line1 and address_line2. The API ignores address_line_1 without an error
  4. A 201 means the business was created, not verified. Wait for the business.updated webhook or poll until status leaves pending
  5. Stay under 20 requests a second per account, and in sandbox wait the seconds in Retry-After after a 429 on business creation

Sumsub

  1. 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
  2. Use a sandbox token (prefix sbx) for agent work. Sandbox and production tokens are separate, and Sumsub's own skills refuse any other prefix
  3. Stay under 300 GET and 50 POST requests per 5 seconds, and under 500 new applicants per 24 hours in Sandbox
  4. Token permissions can't be edited after creation. Generate a new token with the narrower set and delete the old one
  5. 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, Middesk or Sumsub?

Sumsub scores 68.1 (B) on agent readiness against Middesk's 57.5 (C), and leads in 6 of 7 scored categories.

Do Middesk and Sumsub need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Middesk and Sumsub without installing anything?

Yes. Middesk has a hosted endpoint at https://api.middesk.com/v1 and Sumsub at https://api.sumsub.com.

Other comparisons with Middesk or Sumsub

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.