Rank #4 of 6 in Identity Verification & KYC
Access
Install
npm install personaTry itExperimental
See what an agent can do with Persona before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si https://api.withpersona.com/api/v1/inquiries | head -3 # keyless → 401recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Biometric liveness — stories about biometric liveness in this arenaBiometric livenessevidence →
Stories about biometric liveness in this arena
Data checks — stories about data checks in this arenaData checksevidence →
Stories about data checks in this arena
Document coverage — stories about document coverage in this arenaDocument coverageevidence →
Stories about document coverage in this arena
Idv agent access — stories about idv agent access in this arenaIdv agent accessevidence →
Stories about idv agent access in this arena
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dxevidence →
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Privacy retention — stories about privacy retention in this arenaPrivacy retentionevidence →
Stories about privacy retention in this arena
Verification flows — stories about verification flows in this arenaVerification flowsevidence →
Stories about verification flows in this arena
Verification orchestration — stories about verification orchestration in this arenaVerification orchestrationevidence →
Stories about verification orchestration in this arena
Watchlist screening — stories about watchlist screening in this arenaWatchlist screeningevidence →
Stories about watchlist screening in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Persona stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Official SDKs · Scoped API keys · MCP server · Machine-readable spec · Versioning policy · Official CLI · An agent can operate the verification pipeline — create sessions, poll outcomes, retrieve extracted data, and trigger re-checks through the API or an MCP surface with scoped credentials · See verification funnel analytics — pass rates, drop-off points, completion time by country and document type — to know what verification is costing me in signups
Subscribe to events via webhooks
✓7/10
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
—–
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
✓8/10
Explore an interactive API reference with runnable examples
—–
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—–
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Biometric liveness — stories about biometric liveness in this arenaBiometric liveness
Stories about biometric liveness in this arena
The vendor documents specific defenses against AI-generated faces, deepfakes, and camera-injection attacks — named detection capabilities, not just a marketing mention of fraud
—–
The platform detects repeat and duplicate identities across verifications — the same face or document resurfacing under different names is flagged automatically
—0/10
Selfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed video
—–
Data checks — stories about data checks in this arenaData checks
Stories about data checks in this arena
Verify identity against authoritative databases without documents — SSN, national registries, or credit-header data — for lower-friction flows where a doc scan is overkill
—0/10
Verify businesses, not just people — registry lookups, UBO identification, and documented KYB flows that chain into KYC on the owners
—–
Enrich verifications with phone, email, and device risk signals — carrier checks, address history, device fingerprint — as additional documented check types
—0/10
Document coverage — stories about document coverage in this arenaDocument coverage
Stories about document coverage in this arena
The platform verifies government IDs from a documented breadth of countries and document types — passports, national IDs, driver licenses, residence permits — with the supported list published
—0/10
Verified sessions return the extracted document fields as structured data — name, date of birth, document number, address, expiry — retrievable via the API, not just a pass/fail flag
—–
Idv agent access — stories about idv agent access in this arenaIdv agent access
Stories about idv agent access in this arena
Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on
~6/10
An agent can operate the verification pipeline — create sessions, poll outcomes, retrieve extracted data, and trigger re-checks through the API or an MCP surface with scoped credentials
—–
Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx
Sandboxes, test modes, webhooks, and how fast a developer gets to a working integration
A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review results
~6/10
The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented
~4/10
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
~5/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Privacy retention — stories about privacy retention in this arenaPrivacy retention
Stories about privacy retention in this arena
The vendor documents how biometric data is handled lawfully — GDPR bases, US biometric statutes like BIPA, and the consent language my flow needs — so legal review has something to review
—–
Control what happens to collected identity data — documented retention windows and a redaction or deletion API that scrubs PII on demand
—–
Verification flows — stories about verification flows in this arenaVerification flows
Stories about verification flows in this arena
Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
✓7/10
I get native iOS, Android, and web SDKs with guided camera capture — glare, blur, and edge detection coaching the user to a usable document photo on the first try
—–
Send a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or seller
~6/10
A person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-run
~5/10
Verification orchestration — stories about verification orchestration in this arenaVerification orchestration
Stories about verification orchestration in this arena
See verification funnel analytics — pass rates, drop-off points, completion time by country and document type — to know what verification is costing me in signups
—–
Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record
~4/10
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy
~6/10
Watchlist screening — stories about watchlist screening in this arenaWatchlist screening
Stories about watchlist screening in this arena
Screening is not one-shot — previously verified users are continuously re-screened against watchlist updates, and changes raise events I can act on
—–
Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface
—0/10
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | full | 8/10 | Cclaimed | |
Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself C Hosted flows | developer | Verification flows — stories about verification flows in this arenaVerification flows | 3 | full | 7/10 | Cclaimed | |
A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review results C Sandbox | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 3 | partial | 6/10 | Cclaimed | |
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy C Workflows | ops lead | Verification orchestration — stories about verification orchestration in this arenaVerification orchestration | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Cclaimed | |
The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented C Session api | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 3 | partial | 4/10 | Cclaimed | |
The platform verifies government IDs from a documented breadth of countries and document types — passports, national IDs, driver licenses, residence permits — with the supported list published C Doc types | ops lead | Document coverage — stories about document coverage in this arenaDocument coverage | 3 | none | 0/10 | ||
An agent can operate the verification pipeline — create sessions, poll outcomes, retrieve extracted data, and trigger re-checks through the API or an MCP surface with scoped credentials C Agent operations | ai-native user | Idv agent access — stories about idv agent access in this arenaIdv agent access | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Selfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed video C Liveness | risk analyst | Biometric liveness — stories about biometric liveness in this arenaBiometric liveness | 3 | none | untested | none yet | |
Send a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or seller C No code | ops lead | Verification flows — stories about verification flows in this arenaVerification flows | 2 | partial | 6/10 | Cclaimed | |
Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on C Agent decisions | ai-native user | Idv agent access — stories about idv agent access in this arenaIdv agent access | 2 | partial | 6/10 | Cclaimed | |
A person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-run C Reuse | developer | Verification flows — stories about verification flows in this arenaVerification flows | 2 | partial | 5/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Cclaimed | |
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling C Webhooks | developer | Integration dx — sandboxes, test modes, webhooks, and how fast a developer gets to a working integrationIntegration dx | 2 | partial | 5/10 | Cclaimed | |
Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record C Review | ops lead | Verification orchestration — stories about verification orchestration in this arenaVerification orchestration | 2 | partial | 4/10 | Cclaimed | |
Enrich verifications with phone, email, and device risk signals — carrier checks, address history, device fingerprint — as additional documented check types C Risk signals | developer | Data checks — stories about data checks in this arenaData checks | 2 | none | 0/10 | ||
Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface C Screening | ops lead | Watchlist screening — stories about watchlist screening in this arenaWatchlist screening | 2 | none | 0/10 | ||
The platform detects repeat and duplicate identities across verifications — the same face or document resurfacing under different names is flagged automatically C Duplicate detection | risk analyst | Biometric liveness — stories about biometric liveness in this arenaBiometric liveness | 2 | none | 0/10 | ||
Verify identity against authoritative databases without documents — SSN, national registries, or credit-header data — for lower-friction flows where a doc scan is overkill C Db checks | developer | Data checks — stories about data checks in this arenaData checks | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control what happens to collected identity data — documented retention windows and a redaction or deletion API that scrubs PII on demand C Redaction | ops lead | Privacy retention — stories about privacy retention in this arenaPrivacy retention | 2 | none | untested | none yet | |
I get native iOS, Android, and web SDKs with guided camera capture — glare, blur, and edge detection coaching the user to a usable document photo on the first try C Native sdks | developer | Verification flows — stories about verification flows in this arenaVerification flows | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Screening is not one-shot — previously verified users are continuously re-screened against watchlist updates, and changes raise events I can act on C Monitoring | ops lead | Watchlist screening — stories about watchlist screening in this arenaWatchlist screening | 2 | none | untested | none yet | |
See verification funnel analytics — pass rates, drop-off points, completion time by country and document type — to know what verification is costing me in signups C Analytics | founder | Verification orchestration — stories about verification orchestration in this arenaVerification orchestration | 2 | none | untested | none yet | |
The vendor documents how biometric data is handled lawfully — GDPR bases, US biometric statutes like BIPA, and the consent language my flow needs — so legal review has something to review C Consent | founder | Privacy retention — stories about privacy retention in this arenaPrivacy retention | 2 | none | untested | none yet | |
The vendor documents specific defenses against AI-generated faces, deepfakes, and camera-injection attacks — named detection capabilities, not just a marketing mention of fraud C Deepfake defense | risk analyst | Biometric liveness — stories about biometric liveness in this arenaBiometric liveness | 2 | none | untested | none yet | |
Verified sessions return the extracted document fields as structured data — name, date of birth, document number, address, expiry — retrievable via the API, not just a pass/fail flag C Extraction | developer | Document coverage — stories about document coverage in this arenaDocument coverage | 2 | none | untested | none yet | |
Verify businesses, not just people — registry lookups, UBO identification, and documented KYB flows that chain into KYC on the owners C Kyb | ops lead | Data checks — stories about data checks in this arenaData checks | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 41 stories with headroom
What would move Persona’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Idv agent access — stories about idv agent access in this arenaAn agent can operate the verification pipeline — create sessions, poll outcomes, retrieve extracted data, and trigger re-checks through the API or an MCP surface with scoped credentials
nonemoves PA Scoreimpact 30
Evidence shows a general REST API, webhooks, sandbox, and docs for inquiries/workflows, but nothing about scoped API credentials for agent use, session polling/re-check triggering designed for AI agents, or any MCP surface at all.
Document coverage — stories about document coverage in this arenaThe platform verifies government IDs from a documented breadth of countries and document types — passports, national IDs, driver licenses, residence permits — with the supported list published
nonemoves PA Scoreimpact 30
The evidence pack covers Persona's API, webhooks, sandbox, workflows, inquiry templates, and reports, but none of the cited docs actually publish a supported list of countries or document types (passports, national IDs, driver licenses, residence permits).
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI-model training data usage or opt-out controls for Persona; the docs cover identity verification, workflows, and testing but nothing about AI training data policies.
Biometric liveness — stories about biometric liveness in this arenaSelfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed video
nonemoves PA Scoreimpact 30
The evidence pack covers general Persona API/product features (webhooks, sandbox, workflows, reports, hosted flow) but contains no documentation of selfie/liveness verification mechanics or anti-spoofing defenses against printed photos, screens, or replayed video.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
Evidence covers identity verification, workflows, webhooks, and testing tools but contains no mention of AI-generated insights or suggestions derived from user data within the product.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Showing the top 8 of 41 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map9 surfaces · 17 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Integration testing docs7 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Test against a sandbox environment without touching production data
- A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review results
- The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented
- Do everything through the API that I can do in the UI
- Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
Webhooks docs7 stories
- Drive the product through a documented public API
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on
- Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
- Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
Workflows docs7 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on
- Do everything through the API that I can do in the UI
- A person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-run
- Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record
- Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy
Inquiry templates docs6 stories
- Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on
- Do everything through the API that I can do in the UI
- Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
- Send a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or seller
- Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record
- Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy
API reference5 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented
- Do everything through the API that I can do in the UI
Environments docs5 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Test against a sandbox environment without touching production data
- A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review results
- Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
Inquiries docs4 stories
- The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented
- Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myself
- Send a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or seller
- A person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-run
Reports docs3 stories
- Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch on
- The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documented
- Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the record
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si https://api.withpersona.com/api/v1/inquiries | head -3 # keyless → 401reproduced$ curl -si https://api.withpersona.com/api/v1/inquiries | head -3 # [redacted]less → 401 HTTP/2 401 date: Tue, 15 Sep 2026 19:35:48 GMT content-type: application/json
$curl -sL https://docs.withpersona.com/llms.txt | head -3reproduced$ curl -sL https://docs.withpersona.com/llms.txt | head -3 # Persona ## Instructions for AI Agents
$curl -s -X POST https://docs.withpersona.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # keyless initialize completes with serverInforeproduced$ curl -s -X POST https://docs.withpersona.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>' # [redacted]less initialize completes with serverInfo
"serverInfo":{"name":"fern-docs-mcp-server","version":"1.0.0"}
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
1 of 9 testable claims verified · 0 contradicted → integrity 11/100
10 distinct capability claims found in Persona’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
1
Verified
8
Unverified
0
Contradicted
8
Undersold
Verified (1)
“API lets you integrate identity verification, risk assessment, and compliance into your app”
Drive the product through a documented public APIfullproof ↗
Unverified (10)
“Webhooks notify your service about events on any Persona resource”
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without pollingpartialproof ↗
“Webhooks notify your service about events on any Persona resource”
“Sandbox mode lets you test integrations without real verifications or usage charges”
Test against a sandbox environment without touching production datafullproof ↗
“Sandbox mode lets you test integrations without real verifications or usage charges”
A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review resultspartialproof ↗
“Inquiry templates configure screens, verifications, decisioning, and theming for a use case”
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploypartialproof ↗
“Workflows automate repetitive manual decisions and reduce manual review time”
Define rules that trigger actions automatically on eventspartialproof ↗
“Dynamic Flow Templates enable custom UIs and dynamic data-collection fields with adaptive friction”
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploypartialproof ↗
“Hosted Flow lets you redirect users to a Persona-hosted verification page with no frontend code”
Launch a complete document-plus-selfie verification with a hosted or drop-in flow — create a session server-side, redirect or embed, and read the result — without building capture UI myselffullproof ↗
“Simulate Actions let you programmatically trigger inquiry/verification lifecycle states for testing”
A sandbox lets me exercise every outcome before going live — documented test documents, personas, or magic values that deterministically produce pass, fail, and review resultspartialproof ↗
“Using the same reference ID links multiple inquiries to the same account”
A person verified once can be recognized and reused across sessions or products — documented re-verification and reuse of a prior passed check instead of forcing a full re-runpartialproof ↗
Undersold (8)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Verification outcomes come back structured enough for an agent to decide on — machine-readable check results, risk signals, and failure reasons an automated onboarding flow can branch onpartialproof ↗
The whole verification lifecycle is drivable through the API — create a session, get its status, retrieve results and captured media, and cancel or redact it — with every step documentedpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Send a verification to someone with a no-code link or QR code — no engineering ticket to verify a one-off customer, contractor, or sellerpartialproof ↗
Borderline verifications land in a manual review queue with the full evidence — document images, extracted fields, check results — and reviewer decisions feed back into the recordpartialproof ↗
Claims outside our story set (1)
Real capability claims found in Persona’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Reports provide additional end-user information beyond what's submitted in an inquiry”
source ↗
Business model
Free Starter plan with self-serve signup; Growth and Enterprise tiers exist but per-verification prices aren't published (the pricing page itself is bot-walled) — paid tiers are effectively quote-based.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
