Head to head · Kyc identity · October 2026 research run
Didit vs Middesk
Didit scores 75 (BB) on agent readiness against Middesk's 59 (C), and leads in every scored category. Both do kyc identity.
Which one, for what
Didit BB
Good for A team that wants document, liveness, screening and business registry checks from one API with public prices and no sales step, and an agent that has to set itself up.
Ahead on
- Reliability, 80 against 73
- Schema & documentation, 88 against 82
- Agent ergonomics, 69 against 56
- Security & auth, 76 against 56
- Payments & pricing, 60 against 10
- Maintenance & community, 82 against 64
Also in its favour
- Agent-ready, a grade of BB or better
- Runs on your own machine
- Free to start without a card
Watch for
Three incidents marked major on status.didit.me from 22 July to 4 September 2026, each a partial outage of the core APIs traced to the primary database
Middesk C
Good 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
Score by category
| Category | Weight this run | Didit | Middesk | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 80 | 73 | Didit +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 82 | Didit +6 |
| Agent ergonomics | 13%16.2 | 69 | 56 | Didit +13 |
| Security & auth | 14%17.5 | 76 | 56 | Didit +20 |
| Payments & pricing | 10%12.5 | 60 | 10 | Didit +50 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 82 | 64 | Didit +18 |
| Transparency & trust | 7%8.8 | 63 | 61 | Didit +2 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 75 · BB | 59 · C |
Facts side by side
| Fact | Didit | Middesk |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Didit Identity Spain, S.L. | Middesk, Inc. |
| Hosted endpoint | https://verification.didit.me | https://api.middesk.com/v1 |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT | Proprietary service under Middesk's Business Verification Terms and Conditions. The Claude Code and Codex plugins on GitHub are MIT |
| Tools exposed | 156 | 11 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | me.didit/mcp | not listed |
| Last release | 2026-10-08 | 2026-10-05 |
| Terms last updated | 2026-09-23 | no date given |
| Privacy policy last updated | 2026-10-07 | no date given |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 0 stars, 27k npm/wk | 2 stars |
Verdicts
Didit
A self-serve verification API with public per-check prices, key registration by API, scoped keys and a 365-day audit log. The status page shows three incidents marked major between 22 July and 4 September 2026, each a partial outage of the core APIs, and the sub-processor list isn't public.
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
Didit
- Register with
POST https://apx.didit.me/auth/v2/programmatic/register/, thenverify-emailwith the emailed 6-character code. Use a real inbox, because reserved test domains return 500. - Send the key as
x-api-keytohttps://verification.didit.me/v3/. The JWT from registration works only onapx.didit.me. - Create a workflow before
POST /v3/session/.workflow_idis the only required field, and an unfinished session with the samevendor_datais returned again. - Read results from webhooks and use
GET /v3/session/{sessionId}/decision/for back-fill. Every per-feature result is a plural array. - The MCP server at
https://mcp.didit.me/mcptakes OAuth sign-in only, never an API key. Approvedidit:verificationalone when the task doesn't change workflows or keys.
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, Didit or Middesk?
Didit scores 75 (BB) on agent readiness against Middesk's 59 (C), and leads in every scored category.
Do Didit and Middesk need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Didit and Middesk without installing anything?
Yes. Didit has a hosted endpoint at https://verification.didit.me and Middesk at https://api.middesk.com/v1.
Other comparisons with Didit or Middesk
Machine-readable
- This page as Markdown
/compare/didit-vs-middesk.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/didit.json·/api/v1/tools/middesk.json - From a terminal
anchor compare didit middesk(the CLI) - Over MCP
compare_tools {"a": "didit", "b": "middesk"}at/mcp, no key