# Alloy vs Didit

> Didit scores 75 (BB) to Alloy's 52.4 (D) for identity verification. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/alloy-vs-didit
- Markdown: https://www.anchorterminal.com/compare/alloy-vs-didit.md (~2,550 tokens)
- Slim: https://www.anchorterminal.com/compare/alloy-vs-didit.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/alloy-vs-didit.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-14

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

- Alloy: grade D, 52.4/100, rank #782 of 1076. Markdown https://www.anchorterminal.com/tools/alloy.md · JSON https://www.anchorterminal.com/api/v1/tools/alloy.json
- Didit: grade BB, 75/100, rank #63 of 1076. Markdown https://www.anchorterminal.com/tools/didit.md · JSON https://www.anchorterminal.com/api/v1/tools/didit.json
- Best identity and business verification APIs for AI agents: https://www.anchorterminal.com/best/identity-verification/index.md
- All 119 verification comparisons: https://www.anchorterminal.com/compare/identity-verification/index.md

## Which one, for what

### Alloy (D)

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

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

### 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 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

| Category | Weight | Alloy | Didit | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 59 | 80 | Didit +21 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 73 | 88 | Didit +15 |
| Agent ergonomics | 13% (16.2 this run) | 52 | 69 | Didit +17 |
| Security & auth | 14% (17.5 this run) | 49 | 76 | Didit +27 |
| Payments & pricing | 10% (12.5 this run) | 0 | 60 | Didit +60 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 72 | 82 | Didit +10 |
| Transparency & trust | 7% (8.8 this run) | 62 | 63 | Didit +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **52.4 · D** | **75 · BB** | |

## Facts side by side

| Fact | Alloy | Didit |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | First Mile Group, Inc. (Alloy) | Didit Identity Spain, S.L. |
| Hosted endpoint | no (local only) | `https://verification.didit.me` |
| Transports | HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Alloy's terms of service. The @alloyidentity/web-sdk capture package is MIT | Proprietary service under Didit's Business Terms and Conditions. The MCP server in didit-protocol/mcp is MIT |
| Tools exposed | none | 156 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `me.didit/mcp` |
| Last release | 2026-10-05 | 2026-10-08 |
| Terms last updated | 2026-03-12 | 2026-09-23 |
| Privacy policy last updated | no date given | 2026-10-07 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 21k npm/wk | 0 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/alloy-vs-didit.json, and with the fewest tokens: https://www.anchorterminal.com/compare/alloy-vs-didit.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "alloy", "b": "didit"}`. From a terminal: `anchor compare alloy didit`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/alloy.json and https://www.anchorterminal.com/api/v1/tools/didit.json

## Other comparisons with Alloy or Didit

- [Alloy vs ComplyCube](https://www.anchorterminal.com/compare/alloy-vs-complycube.md)
- [Alloy vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/alloy-vs-entrust-identity-verification.md)
- [Alloy vs Jumio](https://www.anchorterminal.com/compare/alloy-vs-jumio.md)
- [Alloy vs Middesk](https://www.anchorterminal.com/compare/alloy-vs-middesk.md)
- [Alloy vs Persona](https://www.anchorterminal.com/compare/alloy-vs-persona.md)
- [Alloy vs Plaid Identity Verification](https://www.anchorterminal.com/compare/alloy-vs-plaid-identity-verification.md)
- [Alloy vs Shufti](https://www.anchorterminal.com/compare/alloy-vs-shufti.md)
- [Alloy vs Socure RiskOS](https://www.anchorterminal.com/compare/alloy-vs-socure-riskos.md)
- [Alloy vs Stripe Identity](https://www.anchorterminal.com/compare/alloy-vs-stripe-identity.md)
- [Alloy vs Sumsub](https://www.anchorterminal.com/compare/alloy-vs-sumsub.md)
- [Alloy vs Trulioo](https://www.anchorterminal.com/compare/alloy-vs-trulioo.md)
- [Alloy vs Veriff](https://www.anchorterminal.com/compare/alloy-vs-veriff.md)
- [Alloy vs Vouched](https://www.anchorterminal.com/compare/alloy-vs-vouched.md)
- [ComplyCube vs Didit](https://www.anchorterminal.com/compare/complycube-vs-didit.md)
- [Didit vs Entrust Identity Verification (formerly Onfido)](https://www.anchorterminal.com/compare/didit-vs-entrust-identity-verification.md)
- [Didit vs Jumio](https://www.anchorterminal.com/compare/didit-vs-jumio.md)
- [Didit vs Middesk](https://www.anchorterminal.com/compare/didit-vs-middesk.md)
- [Didit vs Persona](https://www.anchorterminal.com/compare/didit-vs-persona.md)
- [Didit vs Plaid Identity Verification](https://www.anchorterminal.com/compare/didit-vs-plaid-identity-verification.md)
- [Didit vs Shufti](https://www.anchorterminal.com/compare/didit-vs-shufti.md)
- [Didit vs Socure RiskOS](https://www.anchorterminal.com/compare/didit-vs-socure-riskos.md)
- [Didit vs Stripe Identity](https://www.anchorterminal.com/compare/didit-vs-stripe-identity.md)
- [Didit vs Sumsub](https://www.anchorterminal.com/compare/didit-vs-sumsub.md)
- [Didit vs Trulioo](https://www.anchorterminal.com/compare/didit-vs-trulioo.md)
- [Didit vs Veriff](https://www.anchorterminal.com/compare/didit-vs-veriff.md)
- [Didit vs Vouched](https://www.anchorterminal.com/compare/didit-vs-vouched.md)
- [Alloy vs ComplyAdvantage](https://www.anchorterminal.com/compare/alloy-vs-complyadvantage.md)
- [ComplyAdvantage vs Didit](https://www.anchorterminal.com/compare/complyadvantage-vs-didit.md)