# Persona vs Veriff

> Persona scores 69.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 6 of 7 scored categories. Veriff leads on payments & pricing. Both do kyc identity. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/persona-vs-veriff
- Markdown: https://www.anchorterminal.com/compare/persona-vs-veriff.md (~2,000 tokens)
- Slim: https://www.anchorterminal.com/compare/persona-vs-veriff.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/persona-vs-veriff.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-08

Persona scores 69.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 6 of 7 scored categories. Veriff leads on payments & pricing. Both do kyc identity.

- Persona: grade B, 69.5/100, rank #148 of 629. Markdown https://www.anchorterminal.com/tools/persona.md · JSON https://www.anchorterminal.com/api/v1/tools/persona.json
- Veriff: grade C, 61.1/100, rank #334 of 629. Markdown https://www.anchorterminal.com/tools/veriff.md · JSON https://www.anchorterminal.com/api/v1/tools/veriff.json

## Which one, for what

### Persona (B)

Good for: A company that already runs Persona and wants an agent to create inquiries from templates, read verification and report results, screen against watchlists and work review cases with a permission-limited key.

Ahead on:
- Reliability, 70 against 62
- Agent ergonomics, 74 against 43
- Security & auth, 73 against 63

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Production access needs Persona's approval and a 12-month plan from $250 a month, and API-only integration is limited to Enterprise plans

### Veriff (C)

Good for: A team that needs document and selfie verification with public per-verification prices and a trial, and that can run a webhook receiver and HMAC signing.

Ahead on:
- Payments & pricing, 40 against 35

Watch for: No server-side SDK and no MCP server. Official packages cover only browser and mobile capture


## Score by category

| Category | Weight | Persona | Veriff | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 62 | Persona +8 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 82 | Persona +3 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 43 | Persona +31 |
| Security & auth | 14% (17.5 this run) | 73 | 63 | Persona +10 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Veriff +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 75 | 74 | Persona +1 |
| Transparency & trust | 7% (8.8 this run) | 68 | 67 | Persona +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.5 · B** | **61.1 · C** | |

## Facts side by side

| Fact | Persona | Veriff |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Persona Identities, Inc. | Veriff OÜ |
| Hosted endpoint | `https://mcp.withpersona.com` | no (local only) |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Paid | Pay per use |
| x402 | no | no |
| Licence | Proprietary service under Persona's terms of service. The `persona` JavaScript client on npm is MIT | Proprietary service. The npm capture SDKs are ISC (@veriff/js-sdk, @veriff/incontext-sdk) and MIT (@veriff/react-native-sdk) |
| Tools exposed | 190 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-29 | 2026-10-02 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | couldn't be read | 2026-04-16 |
| Customer content may train models | couldn't be read | yes |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 570k npm/wk | 32 stars, 110k npm/wk |

## Verdicts

**Persona.** The REST API has a public OpenAPI 3.1 file, llms.txt, API keys with per-resource permissions, idempotency keys on every POST and a 60-day sandbox trial with no card. Production needs a business review and a 12-month plan from $250 a month. The status page lists 11 incidents since 10 July 2026, including 70 minutes of timeouts across all products.

**Veriff.** Per-verification prices are public from $0.80, with a 15-day trial of 50 sessions and no card. Each endpoint page is Markdown with an OpenAPI 3.0 fragment. There is no server SDK, MCP server or idempotency key, most calls need an HMAC signature, and the status page shows nine incidents between 20 July and 7 October 2026.

## Before you call either

### Persona

1. Ask for a dedicated key limited to the permissions the task needs. A new key has every standard permission until it's limited
2. Send `Persona-Version` on every call and an `Idempotency-Key` on every POST. A replayed key returns the first result, including a 500
3. Treat redact calls as irreversible. They permanently delete personal data and cascade to downstream objects
4. Stay under 300 requests a minute in production, read `RateLimit-Remaining` and `Quota-Remaining`, and back off on 429 because rejected requests still count
5. Use `fields` and `include` to cut response size. Through MCP these parameters aren't exposed, and only 14 tools take `filter`

### Veriff

1. Take the base URL from the integration's API keys page. Send X-AUTH-CLIENT on every call and store verification.id from POST /v1/sessions
2. Sign POST and PATCH bodies, and the session ID on GET and DELETE, with HMAC-SHA256 in X-HMAC-SIGNATURE. POST /v1/sessions needs no signature
3. Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
4. Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
5. Poll GET /v1/sessions/{id}/decision until `verification` is not null, or accept webhooks within 5 seconds and treat duplicates as normal

## Questions

### Which is better for AI agents, Persona or Veriff?

Persona scores 69.5 (B) on agent readiness against Veriff's 61.1 (C), and leads in 6 of 7 scored categories. Veriff leads on payments & pricing.

### Do Persona and Veriff need an API key?

Both need an API key.

### Can an agent call Persona and Veriff without installing anything?

Persona has a hosted endpoint at https://mcp.withpersona.com. No hosted endpoint is listed for Veriff.


## For agents

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

## Other comparisons with Persona or Veriff

- [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md)
- [Jumio vs Veriff](https://www.anchorterminal.com/compare/jumio-vs-veriff.md)
- [Middesk vs Veriff](https://www.anchorterminal.com/compare/middesk-vs-veriff.md)
- [Persona vs Sumsub](https://www.anchorterminal.com/compare/persona-vs-sumsub.md)
- [Persona vs Trulioo](https://www.anchorterminal.com/compare/persona-vs-trulioo.md)
- [Sumsub vs Veriff](https://www.anchorterminal.com/compare/sumsub-vs-veriff.md)
- [Trulioo vs Veriff](https://www.anchorterminal.com/compare/trulioo-vs-veriff.md)
- [Middesk vs Persona](https://www.anchorterminal.com/compare/middesk-vs-persona.md)