Head to head · Kyc identity · October 2026 research run
Jumio vs Persona
Persona scores 69.5 (B) on agent readiness against Jumio's 55 (C), and leads in 6 of 7 scored categories. Both do kyc identity.
Which one, for what
Jumio C
Good for An enterprise with a Jumio contract that wants document, selfie and liveness checks, watchlist screening and Latin American, Thai and Australian database checks behind OpenAPI-described endpoints.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public price, free tier or trial. OAuth2 and workflow keys are activated by a Jumio account manager
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 65
- Schema & documentation, 85 against 73
- Agent ergonomics, 74 against 45
- Security & auth, 73 against 63
- Payments & pricing, 35 against 0
- Transparency & trust, 68 against 60
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
Score by category
| Category | Weight this run | Jumio | Persona | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 65 | 70 | Persona +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 73 | 85 | Persona +12 |
| Agent ergonomics | 13%16.2 | 45 | 74 | Persona +29 |
| Security & auth | 14%17.5 | 63 | 73 | Persona +10 |
| Payments & pricing | 10%12.5 | 0 | 35 | Persona +35 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 75 | 75 | even |
| Transparency & trust | 7%8.8 | 60 | 68 | Persona +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 55 · C | 69.5 · B |
Facts side by side
| Fact | Jumio | Persona |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Jumio Corporation | Persona Identities, Inc. |
| Hosted endpoint | no (local only) | https://mcp.withpersona.com |
| Transports | HTTP | HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service. No public service agreement was found. The @jumio/websdk npm package is marked UNLICENSED | Proprietary service under Persona's terms of service. The persona JavaScript client on npm is MIT |
| Tools exposed | none | 190 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-28 | 2026-09-29 |
| Terms last updated | no document linked | couldn't be read |
| Privacy policy last updated | 2026-08-04 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | couldn't be read | |
| Terms restrict benchmarking | couldn't be read | |
| Terms or service can change without notice | couldn't be read | |
| Arbitration or class-action waiver | couldn't be read | |
| Popularity | 72 stars, 2.1k npm/wk | 570k npm/wk |
Verdicts
Jumio
Five OpenAPI 3.0 files, an llms.txt index and OAuth2 clients limited to initiating or to retrieving and deleting make the API readable and containable. Access starts with an account manager, with no public price, trial or service agreement, and the status page shows four processing degradations and a 35-minute Singapore outage between 14 August and 2 October 2026.
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.
Before you call either
Jumio
- Use the host for the tenant's region (amer-1, emea-1 or apac-1). Tokens come from auth.<region>.jumio.ai/oauth2/token with the client ID and secret as Basic credentials
- Reuse the bearer token for its 60 minutes. Token requests are limited to 10 a second and new transactions to 1 a second per tenant
- Send a User-Agent header on every call. The Account API marks it required
- Don't blindly retry POST /api/v1/accounts. Each call creates an account and a transaction, and no idempotency key exists
- Wait for the callback or poll the status endpoint until PROCESSED before retrieving. Jumio's retry schedule starts at 40 seconds and stops after 940
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
Questions
Which is better for AI agents, Jumio or Persona?
Persona scores 69.5 (B) on agent readiness against Jumio's 55 (C), and leads in 6 of 7 scored categories.
Do Jumio and Persona need an API key?
Jumio uses an OAuth sign-in. Persona needs an API key.
Can an agent call Jumio and Persona without installing anything?
No hosted endpoint is listed for Jumio. Persona has a hosted endpoint at https://mcp.withpersona.com.
Other comparisons with Jumio or Persona
Machine-readable
- This page as Markdown
/compare/jumio-vs-persona.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/jumio.json·/api/v1/tools/persona.json - From a terminal
anchor compare jumio persona(the CLI) - Over MCP
compare_tools {"a": "jumio", "b": "persona"}at/mcp, no key