Head to head · Sanctions screening · October 2026 research run
ComplyAdvantage vs Middesk
Middesk scores 57.5 (C) on agent readiness against ComplyAdvantage's 52.1 (D), and leads in 3 of 7 scored categories. ComplyAdvantage leads on agent ergonomics and security & auth. Both do sanctions screening.
Best identity and business verification APIs for AI agents · All 119 verification comparisons
Which one, for what
Best for An agent that screens customers and companies against sanctions, politically exposed person and adverse media data, keeps them under monitoring and works the resulting alerts and cases.
Ahead on
- Agent ergonomics, 67 against 56
- Security & auth, 71 against 56
Watch for
No public status page or incident history was found. status.complyadvantage.com could not be reached
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.
Ahead on
- Reliability, 62 against 42
- Maintenance & community, 64 against 8
- Transparency & trust, 62 against 51
Watch for
No public price. Fees are set in an order form, and every docs page ends with a prompt to contact sales
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.
Maintenance & community Middesk +56
ComplyAdvantage 8
No changelog or release notes were found (/changelog answers 404 on 4 November), so the only dates are docs page timestamps, with the getting started guide updated on 16 September 2026, the rate limiting guide on 28 August and the /v3/token reference on 12 August. These record an edit, not a dated API change, and page dates that record no change don't set recency, so no dated release or API change was found (0). No dated changelog entries (0). Support by email and a ticket portal, with a help centre whose credential article was updated in September 2026, per the 8 October check. No public community channel found (5). No official SDK (0). The OpenAPI spec and Postman collection are current with the reference pages (3). 0+0+5+0+3 = 8.
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).
Reliability Middesk +20
ComplyAdvantage 42
Graded on the Mesh REST API, hosted lines. No public status page was found. status.complyadvantage.com could not be reached on 8 October or 4 November, and none is linked from the site, the docs or the help centre (0). No readable incident history (5). Default limits published as 1,000 requests a minute in production and 300 in Sandbox, re-read on 4 November (rate limiting guide updated 28 August 2026) (15). Ratelimit-Limit, Ratelimit-Remaining and Ratelimit-Reset headers are documented, an idempotency key header exists on the rescreen workflow and two workflows are described as safe to resend, but the Mesh docs give no backoff guidance (12). No SLA found in public (0). The API is generally available (10). The idempotency key sits on a side workflow, not on customer creation, so this is the settled 12. 0+5+15+12+0+10 = 42.
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).
Security & auth ComplyAdvantage +15
ComplyAdvantage 71
OAuth2 client credentials with per-credential permissions, optional expiry, 24-hour tokens and deactivation that invalidates issued tokens. Credentials can't be edited, and the older username and password token flow is still supported (28). View and manage permissions are separate and a creator can only grant permissions they hold. No confirmation step for deletes was found (14). Results include third-party adverse media text and customer-supplied data. No injection guidance was found (3). Audit log endpoints for the account, cases, customers, roles, transactions and users (14). The vendor's own Mesh security article (21 January 2025, re-read on 4 November) lists "ISO27001 compliance" and "SOCII compliance" among the platform's certifications. No security.txt, disclosure policy, bug bounty or trust centre was found. That is people-data-labs' and fireworks-inference's record for ISO 27001 and SOC 2 claims with no disclosure route (12). No deduction for the older API accepting a key in the query string, because the graded Mesh API takes the token in a header only. On 4 November security.txt still answers 404. 28+14+3+14+12 = 71.
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.
Agent ergonomics ComplyAdvantage +11
ComplyAdvantage 67
List responses are partial records sized with page_size. No field selection was found (15). page_number, page_size, attribute, range and substring filters and sort on 48 operations, described as most list endpoints (18). Errors follow one structure with title, status, detail, an identifier and a timestamp (16). X-ComplyAdvantage-Idempotency-Key on one operation, two workflows described as idempotent, and 409 on concurrent requests for one external identifier (12). No official SDK was found, and a token must be fetched every 24 hours. A Postman collection is published (6). Per the 8 October check; the spec's single idempotency header on the rescreen workflow is unchanged on 4 November. 15+18+16+12+6 = 67.
Middesk 56
List endpoints return a simplified business item, and a few reads take include, but the full Business object is large (the Markdown reference page for create business is 1.4 MB) and field selection through GraphQL is early access. The MCP server has eleven tools per the vendor's README (14). page and per_page with has_more and total_count, and filters on signals, mail and sub-accounts. The spec shows no filters on the business list (15). Errors are a JSON array of messages with an optional parameter, with no machine-readable codes (12). No idempotency key header. external_id is an idempotency key for sub-accounts only, lien continuations return the one in flight, and MCP annotations couldn't be read (8). Only name and addresses are required to create a business, but no official SDK was found in any language (7). All per the 8 October check, not re-read on 4 November.
Transparency & trust Middesk +11
ComplyAdvantage 51
Closed service. The only public terms cover the website (re-read on 4 November), and no service agreement or API terms were found (8). The privacy notice of 12 June 2026 sets out controller and processor roles, transfer safeguards and 30-day backup retention for removed database entries. No public data processing agreement or retention period for customers' screening data was found (14). A versioning policy lists what counts as backwards compatible, the older API's 2018 deprecation gave two years' notice with dates, and the Mesh spec marks 5 operations deprecated without dates, unchanged on 4 November (GET and POST /v2/alerts/mutes, a mute DELETE, GET /v2/cases/states and GET /v2/iam/permissions) (10). Six regional API hosts are named in the webhooks guide. No subprocessor list was found (8). The privacy notice is per the 8 October check. 8+14+10+8 = 40.
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.
Score by category
| Category | Weight | ComplyAdvantage | Middesk | Edge |
|---|---|---|---|---|
| Reliability | 16% | 42 | 62 | Middesk +20 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 82 | 82 | even |
| Agent ergonomics | 13% | 67 | 56 | ComplyAdvantage +11 |
| Security & auth | 14% | 71 | 56 | ComplyAdvantage +15 |
| Payments & pricing | 10% | 15 | 15 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 8 | 64 | Middesk +56 |
| Transparency & trust | 7% | 51 | 62 | Middesk +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 52.1/100 | C 57.5/100 |
Facts side by side
| Fact | ComplyAdvantage | Middesk |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | IVXS UK Limited (trading as ComplyAdvantage) | Middesk, Inc. |
| Hosted endpoint | https://api.mesh.complyadvantage.com | https://api.middesk.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service. No service agreement is published, and the terms page on complyadvantage.com covers the website only | Proprietary service under Middesk's Business Verification Terms and Conditions. The Claude Code and Codex plugins on GitHub are MIT |
| Tools exposed | none | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-16 | 2026-10-05 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | 2026-06-12 | no date given |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | none | 2 stars |
How the scores have moved
Verdicts
ComplyAdvantage
The Mesh API has a public OpenAPI 3.0.3 spec with 165 described operations, per-credential permissions and audit log endpoints, which suits an agent screening customers and working alerts. No status page, changelog, SDK, service agreement or subprocessor list was found in public, and access starts with a paid plan bought by a person.
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.
Before you call either
ComplyAdvantage
- Exchange the access key and secret at
POST /v3/tokenfor a bearer token. It lasts 24 hours and can't be refreshed, so request a new one before expiry - Ask for a credential with only the permissions the task needs. Permissions can't be edited later, and each reference page names the ones a call requires
- Create a screening configuration first and keep its
configuration_identifier. Creating and screening a customer needs it - Give each customer a unique external identifier. A concurrent request for the same identifier returns 409 with a pointer to the first workflow
- Read
Ratelimit-RemainingandRatelimit-Reseton every response. A 429 body is onlyAPI rate limit exceeded
Middesk
- Match the key to the host.
mk_testkeys work only at https://api-sandbox.middesk.com/v1 andmk_livekeys only at https://api.middesk.com/v1 - Name the
ordersonPOST /v1/businesses. Omitting them places a verification order plus every package the account runs automatically, all billed - Send
address_line1andaddress_line2. The API ignoresaddress_line_1without an error - A 201 means the business was created, not verified. Wait for the
business.updatedwebhook or poll untilstatusleavespending - Stay under 20 requests a second per account, and in sandbox wait the seconds in
Retry-Afterafter a 429 on business creation
Questions
Which is better for AI agents, ComplyAdvantage or Middesk?
Middesk scores 57.5 (C) on agent readiness against ComplyAdvantage's 52.1 (D), and leads in 3 of 7 scored categories. ComplyAdvantage leads on agent ergonomics and security & auth.
Do ComplyAdvantage and Middesk need an API key?
ComplyAdvantage uses an OAuth sign-in. Middesk takes an API key or an OAuth sign-in.
Can an agent call ComplyAdvantage and Middesk without installing anything?
Yes. ComplyAdvantage has a hosted endpoint at https://api.mesh.complyadvantage.com and Middesk at https://api.middesk.com/v1.
Other comparisons with ComplyAdvantage or Middesk
- Alloy vs Middesk
- ComplyCube vs Middesk
- Didit vs Middesk
- Entrust Identity Verification (formerly Onfido) vs Middesk
- Jumio vs Middesk
- Middesk vs Plaid Identity Verification
- Middesk vs Stripe Identity
- Middesk vs Veriff
- Middesk vs Vouched
- Alloy vs ComplyAdvantage
- ComplyAdvantage vs ComplyCube
- ComplyAdvantage vs Didit
- ComplyAdvantage vs Entrust Identity Verification (formerly Onfido)
- ComplyAdvantage vs Jumio
- ComplyAdvantage vs Persona
- ComplyAdvantage vs Plaid Identity Verification
- ComplyAdvantage vs Shufti
- ComplyAdvantage vs Socure RiskOS
- ComplyAdvantage vs Sumsub
- ComplyAdvantage vs Trulioo
- ComplyAdvantage vs Veriff
- ComplyAdvantage vs Vouched
- Middesk vs Persona
- Middesk vs Shufti
- Middesk vs Socure RiskOS
- Middesk vs Sumsub
- Middesk vs Trulioo
Machine-readable
- This page as Markdown
/compare/complyadvantage-vs-middesk.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/complyadvantage.json·/api/v1/tools/middesk.json - From a terminal
anchor compare complyadvantage middesk(the CLI) - Over MCP
compare_tools {"a": "complyadvantage", "b": "middesk"}at/mcp, no key