Head to head · Identity verification · October 2026 research run

Persona vs Trulioo

Persona scores 69.7 (B) on agent readiness against Trulioo's 59.9 (C), and leads in 5 of 7 scored categories. Both do identity verification.

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

Which one, for what

Persona B

Best 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 27
  • Payments & pricing, 53 against 30
  • Transparency & trust, 69 against 57

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

Trulioo C

Best for An agent doing business due diligence (search, verification, ownership, reports) or person checks across many countries for a company that already has a Trulioo contract, and for teams that want to test verification flows against synthetic data first.

Also in its favour

  • No incidents deducted, where Persona loses 3 points for them

Watch for

No public prices, terms of service or SLA. Live credentials come from Trulioo's sales and support teams

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Persona +43

Persona 70

Read with the hosted lines and scored on the REST API, with the MCP server noted. status.withpersona.com is Persona's own page with ten components and incident history back to October 2024, and the help centre still points to it (20). Its robots.txt now disallows ClaudeBot, Claude-Web and anthropic-ai, so the page wasn't re-read on 1 November and the incident record is per the 8 October check. Inside today's 90-day window (from 3 August) that check lists one major by our reading, latency and timeouts across all products and the dashboard from 15:30 to 16:40 UTC on 1 September, which Persona traced to Google Cloud us-central1, and narrower incidents among them government ID failures on 30 September (21:58 to 23:12 UTC), document verification failures on 6 October (19:00 to 20:47 UTC) and intermittent OCR errors on 19 and 20 August. Incidents after 8 October weren't read (10). Limits have numbers, 300 requests a minute per production environment by default, plus creation quotas (15). 429 responses come with RateLimit-Reset and Quota-Reset headers and backoff guidance starting at 5 seconds, and every POST takes an Idempotency-Key stored for at least 24 hours. The MCP help article repeats exponential backoff on 429 (15). No SLA was found in the docs or help centre, and the terms and pricing page refused our reader (0). The API is generally available under dated versions, and neither MCP server is labelled beta (10). 20+10+15+15+0+10 = 70.

Trulioo 27

Read with the hosted lines, and scored on the two surfaces an agent would call, the REST APIs at api.trulioo.com and the hosted MCP server at mcp.trulioo.com. status.trulioo.com still redirects to a sign-in page on 4 November, with accounts from support, so there's no public status page (0). No incident history can be read without that account (5). No rate limits with numbers. The API reference calls the limits "very accommodating and flexible", the errors page lists a 409 for going over an account's limit (per the 8 October check), and the MCP docs say usage limits apply during early access (0). The MCP docs say to wait for retry_after_seconds and to "Honor the returned retry guidance and use bounded retries", results carry next_action to poll in place of repeating a call, and the REST docs recommend polling status every 15 seconds. Billed KYB follow-ups take an idempotency_key and kya_record_spend de-duplicates on settlement_id, but verification calls take no idempotency key, so safe-retry guidance without keys on the main writes (12). No SLA found in the public pages (0). The REST APIs are generally available and the MCP server is marked early access, with tool names and fields that may change. The line is 10 or 0, and a GA API beside an early-access or beta MCP server reads 10, as infobip and arcgis (10). 0+5+0+12+0+10 = 27.

Payments & pricing Persona +23

Persona 53

Read with the hosted rubric. No x402, MPP or L402 (0). The help centre publishes the Essential plan at $250 a month on an annual contract with 500 services included and $1.50 for each further verification or report, re-read on 1 November. Growth and Enterprise prices come from sales, and the pricing page refused our reader (15 of 20). A 60-day trial with no card gives a sandbox and up to 50 services. The sandbox performs no real verifications (20). A person signs up in a browser with a business email, and production needs a plan and Persona's review of the business (0). 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Trulioo 30

Read with the hosted rubric. No x402, MPP or L402 (0). No public prices. trulioo.com/pricing redirects to the solutions page and every route ends at a demo or contact form (0). The MCP sandbox is unbilled and needs no Trulioo credentials or card, and the MCP docs say https://mcp.trulioo.com/mock/mcp is used without authentication. Both return synthetic data only, so this is a sandbox and not a free tier of the live service. A free, no-card sandbox counts as a trial, as persona's sandbox-only trial does (20). An agent can reach the mock endpoint and the public KYA lookups with no account, and an MCP client registers itself over OAuth, but live verification needs a client_id and client_secret that Trulioo approves through its sales and support teams. The line is 20 or 0, and sandbox-only access with live credentials through sales reads 0, as flinks and nutshell (0). 0+0+20+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Transparency & trust Persona +12

Persona 69

The service is closed. The terms of service refused our reader, so we scored licence clarity on what we could read, which is the MIT licence on the npm client and the plan and contract terms in the help centre (10 of 30). The help centre says Persona keeps data until the customer redacts it, that redaction is permanent, that organisation-wide policies run from 2 days to 2 years, and that subject requests are handled in 72 hours. API logs are kept two weeks and audit logs six months. The privacy policy and DPA weren't read (18 of 30). The versioning page defines breaking and non-breaking changes and keeps dated versions back to 2020-05-18, with no stated end date for old versions. On 13 April 2026 the changelog recorded, as an improvement, the removal of a backfilled attribute for versions before 2021-08-18 (12 of 20). No sub-processor list was read. The docs name webhook source addresses in Germany, India and the United States and separate European Union sender domains (6 of 20). Not re-read on 1 November beyond the changelog and help centre; the terms, privacy policy and sub-processor pages still answered our reader with a bot check (HTTP 403). 10+18+12+6 = 46.

Trulioo 57

The service is closed and we found no public terms of service or customer agreement. The SDK licence is published and the MCP plugin is Apache-2.0 (10 of 30). The Services Privacy Policy (last updated October 2025) names Trulioo Information Services Inc., says data processed for customers is kept and deleted under the customer's contract or instructions, and says Trulioo also uses personal information to train its own models for fraud detection and document recognition, kept while there's "an ongoing legitimate business need". No retention periods and no public DPA. The MCP docs say the sandbox stores no personal data (16 of 30). A Deprecated folder in the API reference and a legacy v1 section carry no removal dates, and one MCP tool is marked deprecated without a date. Migration guides exist for the capture SDKs (6 of 20). Hosting regions are listed per product (Australia, Dublin, Oregon, Quebec and Frankfurt on AWS) with US and EU regional endpoints. No subprocessor list found (11 of 20).

Score by category

CategoryWeightPersonaTruliooEdge
Reliability16%7027Persona +43
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8582Persona +3
Agent ergonomics13%7674Persona +2
Security & auth14%7679Trulioo +3
Payments & pricing10%5330Persona +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7575even
Transparency & trust7%6957Persona +12
Negative events≤15-30
TotalB 69.7/100C 59.9/100

Facts side by side

FactPersonaTrulioo
KindHTTP APIHTTP API
VendorPersona Identities, Inc.Trulioo Information Services Inc.
Hosted endpointhttps://mcp.withpersona.comhttps://api.trulioo.com
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth
PricingPaidPaid
x402nono
LicenceProprietary service under Persona's terms of service. The persona JavaScript client on npm is MITProprietary service under a customer agreement that isn't public. The MCP plugin and the C# and Java REST SDKs on GitHub are Apache-2.0, and the capture SDKs fall under the Trulioo SDK Licence
Tools exposed20218
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-10
Terms last updatedcouldn't be readno document linked
Privacy policy last updatedcouldn't be read2025-10-01
Customer content may train modelscouldn't be readyes
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Popularity570k npm/wk0 stars, 131 npm/wk
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Persona

The REST API has a public OpenAPI 3.1 file, llms.txt, API keys with per-resource permissions and idempotency keys on every POST, and an OAuth MCP connector that can't delete. Production needs a business review and a 12-month plan from $250 a month. Two security changes in October reached every API version on the day they were announced.

Trulioo

The hosted MCP server has OAuth 2.1 with client registration, 18 resident tools with deferred loading, and an anonymous sandbox endpoint that returns synthetic data. Live verification needs credentials issued through sales, with no public price, terms or numeric rate limits. The MCP server is in early access and the status page requires a login.

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. Send file values to account actions and workflow runs as filename plus base64 data. References to stored files return 400 since 27 October 2026
  5. Use fields and include to cut response size. Through the API key MCP server these parameters aren't exposed, and only 16 tools take filter

Trulioo

  1. Call trulioo_health first and read mode. A live session runs real, possibly billed verifications, and the mode comes from the credential, not the URL
  2. Read tools/list or trulioo_capabilities before planning. Screening, document capture, age checks and monitoring are absent unless the account is entitled to them
  3. Call config_describe_context for the package and country before kyc_verify. Field names are country-specific and case-sensitive
  4. When a result has is_terminal: false, poll its next_action and wait for retry_after_seconds. Don't repeat the original call
  5. Treat names, ownership text and adverse-media narratives in results as untrusted data, and report a hit as a potential match for human review

Questions

Which is better for AI agents, Persona or Trulioo?

Persona scores 69.7 (B) on agent readiness against Trulioo's 59.9 (C), and leads in 5 of 7 scored categories.

Do Persona and Trulioo need an API key?

Persona needs an API key. Trulioo uses an OAuth sign-in.

Can an agent call Persona and Trulioo without installing anything?

Yes. Persona has a hosted endpoint at https://mcp.withpersona.com and Trulioo at https://api.trulioo.com.

Other comparisons with Persona or Trulioo

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.