Head to head · Kyc identity · October 2026 research run
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.
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 this run | Persona | Veriff | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 62 | Persona +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 82 | Persona +3 |
| Agent ergonomics | 13%16.2 | 74 | 43 | Persona +31 |
| Security & auth | 14%17.5 | 73 | 63 | Persona +10 |
| Payments & pricing | 10%12.5 | 35 | 40 | Veriff +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 75 | 74 | Persona +1 |
| Transparency & trust | 7%8.8 | 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
- Ask for a dedicated key limited to the permissions the task needs. A new key has every standard permission until it's limited
- Send
Persona-Versionon every call and anIdempotency-Keyon every POST. A replayed key returns the first result, including a 500 - Treat redact calls as irreversible. They permanently delete personal data and cascade to downstream objects
- Stay under 300 requests a minute in production, read
RateLimit-RemainingandQuota-Remaining, and back off on 429 because rejected requests still count - Use
fieldsandincludeto cut response size. Through MCP these parameters aren't exposed, and only 14 tools takefilter
Veriff
- 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
- 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
- Stay under 30 session creations a minute on Self-Serve, 600 on Enterprise. A 429 carries code 1004
- Don't blindly retry POST /v1/sessions. Each call makes a new session, which is billed on a live integration
- Poll GET /v1/sessions/{id}/decision until
verificationis 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.
Other comparisons with Persona or Veriff
Machine-readable
- This page as Markdown
/compare/persona-vs-veriff.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/persona.json·/api/v1/tools/veriff.json - From a terminal
anchor compare persona veriff(the CLI) - Over MCP
compare_tools {"a": "persona", "b": "veriff"}at/mcp, no key