Rank #5 of 6 in Identity Verification & KYC
Access
Install
npm install @veriff/js-sdkTry itExperimental
See what an agent can do with Veriff 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 -X POST https://stationapi.veriff.com/v1/sessions -H 'Content-Type: application/json' -d '{}' # 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 Veriff 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 → Scoped API keys · MCP server · Machine-readable spec · Versioning policy · Official CLI · Full data export · 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
✓8/10
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
✓7/10
Explore an interactive API reference with runnable examples
—0/10
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
—0/10
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
~4/10
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
—0/10
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
—–
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
—0/10
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
~5/10
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
~5/10
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
~6/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
✓8/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
~3/10
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
~4/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
—0/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
~5/10
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploy
~3/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
—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
~6/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 | 0/10 | ||
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 | 8/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
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 | ||
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 | 0/10 | ||
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 | 0/10 | ||
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 | 0/10 | ||
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 | |
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 | |
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 | 7/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 | 8/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 | |
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 | partial | 5/10 | Tprobed | |
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 | 5/10 | Cclaimed | |
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 | partial | 4/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 | 3/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 | 3/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
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 | |
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 | untested | none yet | |
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 | partial | 6/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 | 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 | Tprobed | |
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 | 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 | Tprobed | |
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 | 4/10 | Cclaimed | |
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 | partial | 3/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 2/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 | none | 0/10 | ||
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 | ||
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 | 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 | ||
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 | 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 C Extraction | developer | Document coverage — stories about document coverage in this arenaDocument coverage | 2 | none | 0/10 | ||
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 | 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 | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 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 | none | 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 | |
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 | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 43 stories with headroom
What would move Veriff’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
Veriff is an identity verification SaaS with a REST API, SDKs, and webhooks, but no evidence of an official MCP server for agent connectivity; this is a fair axis for a SaaS API product, so absence of evidence yields none.
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 contains only API/SDK/webhook integration docs, HMAC auth, biometric liveness, and pricing add-ons — none of it lists supported countries or document types (passports, national IDs, driver licenses, residence permits) or points to a published coverage list.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Veriff's docs mention exporting verification session details to PDF for business customers reviewing cases, but there is no evidence of an end-user-facing mechanism to export all personal/identity data in open, machine-readable formats (JSON/CSV) and delete one's account.
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 training data opt-out or any privacy controls related to preventing use of user data for AI model training; the documentation covers verification API/SDK/webhook mechanics only.
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 APIs, webhooks, HMAC auth, manual review portal, and pricing add-ons, but nothing indicates AI-generated insights or suggestions surfaced to users from their data.
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".
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Veriff's API auth model is a single shared-secret HMAC key (X-HMAC-SIGNATURE) plus optional IP allowlisting, not a scoped/least-privilege credential system with per-agent roles or permissions.
Showing the top 8 of 43 — 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 map6 surfaces · 22 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs21 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Selfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed video
- 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
- 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
- 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
- Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
- 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
- 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
- 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
- Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface
devdocs.veriff.com15 stories
- Drive the product through a documented public API
- Build against official SDKs
- 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
- 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
- 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
- Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
- 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
- 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
- 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
Apidocs docs13 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Build against official SDKs
- Subscribe to events via webhooks
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- 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
- 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
- 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
- Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without polling
- 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
- 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
llms.txt7 stories
- Point an agent at llms.txt or agent-oriented docs
- 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
- 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
- Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface
OpenAPI spec6 stories
- Point an agent at llms.txt or agent-oriented docs
- Drive the product through a documented public API
- Build against official SDKs
- 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
- 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
- Do everything through the API that I can do in the UI
Pricing 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
- Do everything through the API that I can do in the UI
- Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surface
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 -X POST https://stationapi.veriff.com/v1/sessions -H 'Content-Type: application/json' -d '{}' # keyless → 401reproduced$ curl -si -X POST https://stationapi.veriff.com/v1/sessions -H 'Content-Type: application/json' -d '{}' # [redacted]less → 401
HTTP/2 401
content-type: application/json; charset=utf-8
$curl -sL https://devdocs.veriff.com/llms.txt | head -3reproduced$ curl -sL https://devdocs.veriff.com/llms.txt | head -3 # Veriff Dev Documentation > Knowledge base documentation for Veriff Dev Documentation.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
2 of 11 testable claims verified · 0 contradicted → integrity 18/100
15 distinct capability claims found in Veriff’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
2
Verified
9
Unverified
0
Contradicted
11
Undersold
Verified (2)
“End-users can be brought into the verification flow using web or native SDKs”
“A decision endpoint can be polled to retrieve session verification outcomes”
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 credentialspartialproof ↗
Unverified (14)
“End-user data can be passed via API and endpoint behavior checked out”
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 ↗
“End-users can be brought into the verification flow using web or native SDKs”
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 trypartialproof ↗
“Webhooks can be set up to receive verification responses from Veriff”
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without pollingpartialproof ↗
“Offers a no-code identity verification solution”
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 ↗
“An API endpoint creates a new verification session to start every verification flow”
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 ↗
“A decision endpoint can be polled to retrieve session verification outcomes”
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 ↗
“Test integration sessions do not count towards paid usage”
Test against a sandbox environment without touching production datafullproof ↗
“Test integration sessions do not count towards paid usage”
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 ↗
“Decisions can be manually triggered for test integration sessions to simulate outcomes”
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 ↗
“HMAC signatures and allowed IP lists/ranges are used to secure webhook and API communication”
Verification lifecycle events arrive as signed webhooks — created, processing, verified, requires-input — so my system reacts to outcomes without pollingpartialproof ↗
“Biometric Liveness solution detects that captured biometric data comes from a live person, reducing fraud risk”
Selfie checks match the live user to the document portrait with liveness detection — documented defenses against printed photos, screens, and replayed videopartialproof ↗
“Verification sessions can be manually reviewed and managed via the Verifications page in the Customer Portal”
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 ↗
“PEP & Sanctions check available as an add-on verification check”
Screen verified users against sanctions, PEP, and adverse-media watchlists as part of the same verification — one vendor, one API, one review surfacepartialproof ↗
“Batch upload of test verification sessions can be arranged for specific use cases with onboarding team”
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 ↗
Undersold (11)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
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 ↗
Do everything through the API that I can do in the UIpartialproof ↗
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 ↗
Configure verification logic without code — conditional steps, risk-based routing, country-specific requirements, and template changes that don't need an engineering deploypartialproof ↗
Claims outside our story set (2)
Real capability claims found in Veriff’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.
“A shared secret key is used to generate an HMAC signature header for request authentication”
source ↗“Verification session details can be exported to PDF”
source ↗
Business model
Published per-verification pricing: Essential $0.80 (min $49/month), Plus $1.39 (min $99), Premium $1.89 (min $209), enterprise above 5,000/month; 15-day free trial, 50 sessions, no card needed.
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
