# Persona > Persona is an identity verification platform from Persona Identities, Inc. Its REST API and hosted MCP server create inquiries, run government ID, selfie, document and database verifications, screen people and businesses against watchlists, and manage review cases. - Canonical: https://www.anchorterminal.com/tools/persona - Markdown: https://www.anchorterminal.com/tools/persona.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/persona.min.md (~2,080 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/persona.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 ## Overview **Grade B · 69.5/100 · rank #148 of 629 · #1 in Identity & business verification · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Persona Identities, Inc. (https://withpersona.com) | | Kind | HTTP API | | Category | Identity & business verification (https://www.anchorterminal.com/categories/identity-verification) | | Transport | HTTP | | Endpoint | `https://mcp.withpersona.com` | | Auth | API key · Self-serve API key, sent as `Authorization: Bearer ` to https://api.withpersona.com/api/v1. A browser sign-up with a business email gives a sandbox key (`persona_sandbox_...`) at once. A production key (`persona_production_...`) needs a plan and Persona's approval of the organisation. Each key can be limited to about 50 read and write permissions per resource, given its own rate limit and an IP allowlist, and expired through the dashboard or the API. A new key has every standard permission until someone limits it. The MCP server at https://mcp.withpersona.com takes the same key. Its help article says OAuth is coming and isn't available yet (checked 2026-10-08). | | Pricing | Paid ($250 / mo) · The Essential plan starts at $250 a month on a 12-month contract with 500 verifications or reports a month included, then $1.50 for each further one, per the help centre. Growth and Enterprise are priced through sales. A 60-day trial with no card gives sandbox access and up to 50 services, so an agent can build and test without a contract, but the sandbox performs no real verifications. A Startup Programme gives eligible small companies 500 free verifications a month for a year. The pricing page itself refused our reader (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI file, the MCP tool list or the help centre's plan articles (checked 2026-10-08). | | Licence | Proprietary service under Persona's terms of service. The `persona` JavaScript client on npm is MIT | | Tools exposed | 190 | | Packages | npm: `persona` | | Docs | https://docs.withpersona.com/getting-started | | llms.txt | https://docs.withpersona.com/llms.txt | | Last release | 2026-09-29 | | npm downloads / week | 570,188 | | API | REST with JSON API responses at https://api.withpersona.com/api/v1. OpenAPI 3.1 for version 2025-12-08 with 191 paths and 231 operations (117 POST, 85 GET, 19 DELETE, 10 PATCH) and 141 webhook definitions | | MCP server | Hosted and stateless at https://mcp.withpersona.com, 190 tools generated from the API, same API key in the `Authorization` header, same rate limits. No annotations, no toolsets, OAuth not yet available | | Checks | Government ID (with NFC and AAMVA), selfie, document, database (many countries, eCBSV, TIN, phone carrier), email and phone verifications. Reports include watchlist, politically exposed person, adverse media, business watchlist, business lookup, business registrations and associated persons, crypto address watchlist, phone risk and email address | | Credentials | Bearer API key per environment (`persona_sandbox_...`, `persona_production_...`), about 50 permissions such as `inquiry.read` and `report.write`, IP allowlist, per-key rate limit, expiry endpoint. Payload filters that restrict visible records are Enterprise only | | Rate limits | 300 requests a minute per production environment by default, shared by all keys, plus per-product creation quotas. `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset` and `Quota-*` headers on responses. Environments above 1,000 a minute may have a ramp-up limit | | Retries | `Idempotency-Key` on every POST, stored for at least 24 hours. 429 with exponential backoff advised, starting at 5 seconds | | Response size | `fields` on 213 operations and `include` on 181, cursor pagination with `page[after]`, `page[before]` and `page[size]` from 1 to 100 (default 10), search endpoints for inquiries, accounts, cases and webhook events | | Errors | HTTP status plus an `errors` list with `title` and `details`. Every operation documents 400, 401, 403 and 429. `Request-Id` header on each response | | Versioning | Dated versions set per key or with `Persona-Version`. The docs name 2025-12-08 as the latest and keep seven versions back to 2020-05-18. Breaking changes ship only in a new version | | Webhooks | HMAC SHA-256 in a `Persona-Signature` header with a timestamp, secret rotation through the API, event filters, attribute allowlists and blocklists, optional OAuth client credentials on deliveries | | Audit | API logs with request and response kept for up to two weeks, user audit logs for up to six months through a production key | | Retention | Data is kept until the customer redacts it through the API, the dashboard or a Workflow step. Organisation-wide redaction policies run from 2 days to 2 years and are switched on by Persona on request | | Sandbox | Free 60-day trial with no card and up to 50 services. Sandbox runs no real verifications and has a pass or fail toggle. Watchlist and politically exposed person hits can be triggered with test names | | Certifications | SOC 2 Type II and ISO 27001 per the help centre. security.txt valid until 17 February 2027, with disclosure through a Bugcrowd form | | Status | status.withpersona.com, Persona's own page, ten components (API, Dashboard, Reports, Verifications, Database Verifications, Workflows, Graph, Inquiries and Collections, Webhooks, Cases) with incident history back to October 2024 | | Capabilities | kyc.identity, kyc.business, kyc.documents, kyc.screening, kyc.cases | | Tags | hosted, paid, sandbox, api-key, mcp, openapi, llms-txt, webhooks, json-api, status-page, soc2, iso27001 | | JSON | https://www.anchorterminal.com/api/v1/tools/persona.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 70 | 14.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 85 | 13.8 | | Agent ergonomics | 13% | 16.2 | 74 | 12.0 | | Security & auth | 14% | 17.5 | 73 | 12.8 | | Payments & pricing | 10% | 12.5 | 35 | 4.4 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 46, provenance 90) | 7% | 8.8 | 68 | 6.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **69.5 → B** | ### Why each score - Reliability 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 (20). It lists 11 incidents between 10 July and 8 October 2026, six marked degraded and five partial outage. One is 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. The others are narrower, 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 (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 (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. The MCP server isn't labelled beta, though OAuth for it is still to come (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 85: A public OpenAPI 3.1 file for version 2025-12-08 has 191 paths, 231 operations and 141 webhook definitions, and the MCP server returns typed input schemas for 190 tools (25). llms.txt per docs version and for the help centre, and any page as Markdown by adding `.md` (10). Operation descriptions are short, with a median of 61 characters and 50 of 231 under 40, though guides for each product say when to use inquiries, transactions, verifications and reports (12 of 20). The spec carries 1,070 enums and 2,720 required lists, but the versioning page tells clients not to treat string values as fixed enumerations. In the MCP list 13 tools have an empty input schema, `create-an-api-key` among them, and four contain `$ref` pointers that resolve to nothing in the tool definition (12 of 15). Every operation documents 400, 401, 403 and 429 responses, and guides carry curl requests and sample payloads. The spec file itself has no example values (11 of 15). Dated API versions and a changelog with an RSS feed (15). The two spec links printed at the foot of the versioned llms.txt return 404, and the working file is at /openapi/api-reference.json. - Agent ergonomics 74: Scored on the REST API. `fields` is accepted on 213 operations and `include` on 181, so a caller can drop related objects and attributes. Default inquiry responses in JSON API form are large, and the MCP server lists 190 tools in about 117 KB with no toolsets and without `fields` or `include` (20 of 25). Cursor pagination with `page[size]` from 1 to 100, filters on 17 list operations, and search endpoints for inquiries, accounts, cases and webhook events (18 of 20). Errors are an HTTP status with `title` and `details` such as "data.attributes.name is missing", with advice per status code. There's no list of machine-readable error codes (14 of 20). `Idempotency-Key` on every POST with parameter checking. The MCP tools carry no readOnlyHint or destructiveHint and don't expose the idempotency header (16 of 20). No official server-side SDK was found. The npm, iOS, Android and React Native packages are clients for the end-user flow, and API examples are raw HTTP in curl, Ruby, Python and JavaScript (6 of 15). - Security & auth 73: Bearer API keys per environment, each limited to about 50 read and write permissions per resource, with an IP allowlist, a per-key rate limit, an expiry endpoint and written rotation steps. A new key has every standard permission until someone limits it, and key management permissions are off by default (27 of 30). A read-only key is possible and Persona recommends one dedicated key per agent. Redaction is irreversible with no confirmation step, the MCP server exposes all 190 tools whatever the key allows, and payload filters that restrict visible records are Enterprise only. An investigation lock can block redaction of a verification (12 of 20). Responses carry end-user input, document extractions, adverse media and website content. The MCP article asks customers to check their own security requirements and to use a read-only key, with no prompt-injection guidance found (4 of 15). API logs for two weeks and user audit logs for six months, both through the API, and a `Request-Id` on every response (15). security.txt valid until 17 February 2027, a disclosure form run on Bugcrowd, and SOC 2 Type II and ISO 27001 per the help centre. No public advisories or bounty terms were found, and the trust centre needs JavaScript we couldn't read (15 of 20). - Payments & pricing 35: 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. 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). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 75: The latest API changelog entry is 29 September 2026 (30). Four dated entries in the last 90 days, on 15 July, 18 August, 24 August and 29 September (20). A closed service with a changelog and RSS feed, a help centre, a community Slack and a support form in the dashboard. Persona says it can't guarantee support for trial and Startup Programme accounts, and we didn't test a channel (10 of 15). The official packages are clients for the end-user flow. The npm `persona` package reached 5.9.0 on 16 September 2026, and no server-side SDK was found (10 of 15). The npm package is MIT with regular releases. Its source repository and CI aren't linked from the package (5 of 10). - Transparency & trust 68: 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). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (18 items): https://www.anchorterminal.com/fixes/persona.md (JSON https://www.anchorterminal.com/fixes/persona.json) ### What we couldn't check - unchecked: withpersona.com marketing pages (home, pricing, security, terms of service, privacy policy, DPA and sub-processor pages) answered our reader with a bot check (HTTP 403), so the terms, the privacy policy, any SLA and any sub-processor list were not read - unchecked: the trust centre at trust.withpersona.com, which needs JavaScript, so certification reports and any published sub-processors were not confirmed there - unchecked: security incidents, advisories or vendor post-mortems in the last 12 months. Persona's blog and trust pages were unreadable, so the deduction is 0 on what we could read - unchecked: whether customers on API versions before 2021-08-18 had notice before the backfilled `extraction-results` attribute was removed on 13 April 2026 - unchecked: whether the trial sign-up asks for a card (the help centre says it doesn't) and whether a failed verification counts as a billable service - unchecked: sandbox rate limits, and whether the MCP server appears in the official MCP registry - The versioning page names 2025-12-08 as the latest version, while the `Persona-Version` header on the create-inquiry reference page also lists 2026-09-29 - The API keys page describes the `mcp.access` permission as access to a Machine Learning Classification Platform, which is unrelated to the Model Context Protocol server ### Sources - docs index for agents: (seen 2026-10-08) - versioned docs index and spec links: (seen 2026-10-08) - OpenAPI 3.1 file: (seen 2026-10-08) - API introduction and Enterprise-only API integration: (seen 2026-10-08) - API quickstart: (seen 2026-10-08) - API keys, permissions and rotation: (seen 2026-10-08) - rate limits and quotas: (seen 2026-10-08) - idempotency: (seen 2026-10-08) - pagination: (seen 2026-10-08) - errors: (seen 2026-10-08) - response body, fields and include: (seen 2026-10-08) - versioning policy: (seen 2026-10-08) - API changelog: (seen 2026-10-08) - environments and sandbox: (seen 2026-10-08) - security, IP allowlist and webhook source addresses: (seen 2026-10-08) - API logs: (seen 2026-10-08) - webhook signatures: (seen 2026-10-08) - create an inquiry reference: (seen 2026-10-08) - MCP server help article: (seen 2026-10-08) - MCP server tool list (unauthenticated tools/list): (seen 2026-10-08) - plans, trial and Essential plan price: (seen 2026-10-08) - Startup Programme: (seen 2026-10-08) - plan cancellation and contract term: (seen 2026-10-08) - customer support by plan: (seen 2026-10-08) - security and privacy overview: (seen 2026-10-08) - redaction and redaction policies: (seen 2026-10-08) - security reports and Bugcrowd form: (seen 2026-10-08) - help centre index: (seen 2026-10-08) - status page data: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - npm package: (seen 2026-10-08) - npm weekly downloads: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 90/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Persona Identities, Inc. | 20/20 | | Domain age | withpersona.com, registered 2018-09-24 (8 years) | 11/15 | | Endpoint on the vendor's domain | mcp.withpersona.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | status.withpersona.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The help centre footer reads "2026 Persona Identities, Inc.", and the `persona` npm package names Persona Identities, Inc. as author. The API answers at api.withpersona.com and the MCP server at mcp.withpersona.com, both withpersona.com subdomains. withpersona.com/.well-known/security.txt gives security@withpersona.com, an expiry of 17 February 2027 and a note that disclosure runs through Bugcrowd. The terms and privacy URLs are the ones the status page links to. Both pages, and the rest of withpersona.com, answered our reader with a bot check (HTTP 403), so their text wasn't read. RDAP for withpersona.com gives a registration date of 2018-09-24 and MarkMonitor Inc. as registrar. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://withpersona.com/legal/terms-of-service), read 2026-10-08. Our reader couldn't read it (the page answered HTTP 403 to our reader). **Privacy policy** (https://withpersona.com/legal/privacy-policy), read 2026-10-08. Our reader couldn't read it (the page answered HTTP 403 to our reader). ## Live (updated 2026-10-08 17:36 UTC) - Right now: up, HTTP 405, 134 ms, checked 2026-10-08 17:36 UTC (get on `https://mcp.withpersona.com`) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 157 ms · p95 430 ms - Vendor status page: unknown, no machine-readable status found - npm `persona` 5.9.0 - security.txt: valid, expires 2027-02-17T08:00:00.000Z - Always current: https://www.anchorterminal.com/api/v1/live/persona.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Essential plan | $250 | per month (plan) | 12-month contract, 500 verifications or reports a month included, unused ones don't roll over | | Additional verification or report on the Essential plan | $1.50 | per transaction | Each service beyond the 500 included a month | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.1 file with 231 operations and 141 webhook definitions, plus llms.txt and a Markdown copy of every docs page - API keys take about 50 read and write permissions per resource, an IP allowlist, their own rate limit and an expiry endpoint - `Idempotency-Key` on every POST, cursor pagination, and `fields` and `include` parameters that trim responses - API logs kept for two weeks and user audit logs for six months, both readable through the API - Dated API versions selected per key or per request with `Persona-Version`, and a changelog with an RSS feed ## Weaknesses - Production access needs Persona's approval and a 12-month plan from $250 a month, and API-only integration is limited to Enterprise plans - Eleven incidents on the status page since 10 July 2026, five marked partial outage, most on document and government ID verifications - The MCP server lists all 190 tools whatever the key allows, with no annotations, toolsets or read-only subset, and OAuth isn't available yet - No official server-side SDK was found. The npm, iOS, Android and React Native packages are clients for the end-user flow - The marketing site, terms, privacy policy and pricing page answered our reader with a bot check, and no SLA was found in the docs or help centre ## Before you call it (notes for agents) 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` ## Connect First request: ```bash curl --request POST \ --url https://api.withpersona.com/api/v1/inquiries \ --header 'Persona-Version: 2023-01-05' \ --header 'accept: application/json' \ --header 'authorization: Bearer persona_sandbox_YOURAPIKEY' \ --header 'content-type: application/json' \ --data '{"data":{"attributes":{"inquiry-template-id":"itmpl_YOURTEMPLATEID","fields":{"name-first":"Jane","name-last":"Doe","birthdate":"1994-04-12"}}}}' ``` Through letme (picks today, calling later): https://letme.dev/persona (letme picks it for kyc.business, the top-graded tool for the job, letme picks it for kyc.cases, the top-graded tool for the job, letme picks it for kyc.documents, the top-graded tool for the job, letme picks it for kyc.identity, the top-graded tool for the job, letme picks it for kyc.screening, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Sumsub | B | 68.5 | 167 | kyc.identity, kyc.business, kyc.documents, kyc.screening, kyc.cases | no | https://www.anchorterminal.com/tools/sumsub.md | | Middesk | C | 59 | 389 | kyc.business, kyc.screening, kyc.cases, kyc.identity | no | https://www.anchorterminal.com/tools/middesk.md | | Trulioo | C | 58.2 | 406 | kyc.identity, kyc.business, kyc.documents, kyc.screening | no | https://www.anchorterminal.com/tools/trulioo.md | | Grep AI | B | 64.4 | 252 | kyc.business, kyc.screening, kyc.documents | no | https://www.anchorterminal.com/tools/grep-ai.md | | Veriff | C | 61.1 | 334 | kyc.identity, kyc.documents, kyc.screening | no | https://www.anchorterminal.com/tools/veriff.md | | Jumio | C | 55 | 461 | kyc.identity, kyc.documents, kyc.screening | no | https://www.anchorterminal.com/tools/jumio.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The OpenAPI 3.1 file for version 2025-12-08 has 191 paths, 231 operations and 141 webhook definitions, served at https://docs.withpersona.com/openapi/api-reference.json. The two spec links at the foot of the versioned llms.txt return 404 (source: ) - The hosted MCP server answers `tools/list` without a key and returns 190 tools in about 117 KB, with no annotations and no toolsets. Calls need an API key (source: ) - API keys carry per-resource read and write permissions, and Persona's own advice is one dedicated key per agent with only the permissions it needs (source: ) - Every POST accepts an `Idempotency-Key` header. Persona stores the first status code and body for at least 24 hours and replays them, including 500 errors (source: ) - Redaction endpoints permanently delete personal data from an inquiry, account, verification, report, case or transaction and can't be undone. An investigation lock on a verification blocks redaction (source: ) - status.withpersona.com lists 11 incidents between 10 July and 8 October 2026, five marked partial outage, among them latency and timeouts across all products from 15:30 to 16:40 UTC on 1 September that Persona traced to Google Cloud us-central1 (source: ) - API-only use, where verifications, reports and transactions are created directly with no Persona-hosted flow, is limited to Enterprise plans (source: ) ## Compare - [Jumio vs Persona](https://www.anchorterminal.com/compare/jumio-vs-persona.md): C 55 vs B 69.5 - [Persona vs Sumsub](https://www.anchorterminal.com/compare/persona-vs-sumsub.md): B 69.5 vs B 68.5 - [Persona vs Trulioo](https://www.anchorterminal.com/compare/persona-vs-trulioo.md): B 69.5 vs C 58.2 - [Persona vs Veriff](https://www.anchorterminal.com/compare/persona-vs-veriff.md): B 69.5 vs C 61.1 - [Middesk vs Persona](https://www.anchorterminal.com/compare/middesk-vs-persona.md): C 59 vs B 69.5 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on withpersona.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "persona", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Persona on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Persona on Anchor Terminal](https://www.anchorterminal.com/badges/persona.svg)](https://www.anchorterminal.com/tools/persona) ``` Plain link: ```html Persona on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Persona is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/persona-dark.png - Light: https://www.anchorterminal.com/assets/share/persona-light.png