Head to head · Identity verification · October 2026 research run

Alloy vs Didit

Didit scores 75 (BB) on agent readiness against Alloy's 52.4 (D), and leads in every scored category. Both do identity verification.

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

Which one, for what

Alloy D

Best for Banks and fintechs that already run onboarding through Alloy and want an agent to submit journey applications, read decisions and work investigations.

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

Watch for

No public prices, trial or self-serve sign-up. Access starts with a demo request

Didit BB

Best 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 59
  • Schema & documentation, 88 against 73
  • Agent ergonomics, 69 against 52
  • Security & auth, 76 against 49
  • Payments & pricing, 60 against 0
  • Maintenance & community, 82 against 72

Also in its favour

  • Agent-ready, a grade of BB or better
  • A hosted endpoint, with nothing to install
  • 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

Score by category

CategoryWeight this runAlloyDiditEdge
Reliability16%205980Didit +21
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27388Didit +15
Agent ergonomics13%16.25269Didit +17
Security & auth14%17.54976Didit +27
Payments & pricing10%12.5060Didit +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87282Didit +10
Transparency & trust7%8.86263Didit +1
Negative events≤1500
TotalD 52.4/100BB 75/100

Facts side by side

FactAlloyDidit
KindHTTP APIHTTP API
VendorFirst Mile Group, Inc. (Alloy)Didit Identity Spain, S.L.
Hosted endpointno (local only)https://verification.didit.me
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidPay per use
x402nono
LicenceProprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MITProprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT
Tools exposednone156
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedme.didit/mcp
Last release2026-10-052026-10-08
Terms last updated2026-03-122026-09-23
Privacy policy last updatedno date given2026-10-07
Customer content may train modelsnot found in the textyes, with an opt-out
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity21k npm/wk0 stars, 27k npm/wk

Verdicts

Alloy

Alloy's public docs cover journeys, evaluations, entities, documents, cases and investigations, with llms.txt, Markdown pages, OpenAPI fragments and rate-limit headers with retry-after. Access is sales-led with no public price or trial, credentials have no scopes, there is no idempotency key or server SDK, and inputs vary by each customer's workflow.

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.

Before you call either

Alloy

  1. Get the account's base URL from the customer. Defaults are api.alloy.co and sandbox.alloy.co, and some accounts have their own hosts
  2. Use unique, prefixed external IDs in sandbox. Sandbox and Production share one data store
  3. Read alloy-ratelimit-remaining, and on 429 or 5xx wait for retry-after with exponential backoff and jitter
  4. Expect running after about 25 seconds on journey applications and wait for the webhook instead of resubmitting
  5. Send the workflow header with account-level keys, since inputs depend on the workflow configured

Didit

  1. Register with POST https://apx.didit.me/auth/v2/programmatic/register/, then verify-email with the emailed 6-character code. Use a real inbox, because reserved test domains return 500.
  2. Send the key as x-api-key to https://verification.didit.me/v3/. The JWT from registration works only on apx.didit.me.
  3. Create a workflow before POST /v3/session/. workflow_id is the only required field, and an unfinished session with the same vendor_data is returned again.
  4. Read results from webhooks and use GET /v3/session/{sessionId}/decision/ for back-fill. Every per-feature result is a plural array.
  5. The MCP server at https://mcp.didit.me/mcp takes OAuth sign-in only, never an API key. Approve didit:verification alone when the task doesn't change workflows or keys.

Questions

Which is better for AI agents, Alloy or Didit?

Didit scores 75 (BB) on agent readiness against Alloy's 52.4 (D), and leads in every scored category.

Do Alloy and Didit need an API key?

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

Can an agent call Alloy and Didit without installing anything?

No hosted endpoint is listed for Alloy. Didit has a hosted endpoint at https://verification.didit.me.

Other comparisons with Alloy or Didit

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.