How Veriff’s scores are calculated
The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.
verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10
PA Score19/100
Agent-ready 37.8 × 0.30 = 11.34
API quality 10.0 × 0.20 = 2.00
Openness 8.6 × 0.20 = 1.72
Built-in AI 10.0 × 0.15 = 1.50
Automation 15.6 × 0.15 = 2.34
(11.34 + 2.00 + 1.72 + 1.50 + 2.34) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 18.90 ÷ 1.00 = 18.9
Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.
Agent-ready37.8/100×0.30 of the PA blend
Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.
Point an agent at llms.txt or agent-oriented docsweight 2
2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max
- [probe] https://devdocs.veriff.com/llms.txt“PROBE llms.txt: HTTP 200 at https://devdocs.veriff.com/llms.txt # Veriff Dev Documentation > Knowledge base documentation for Veriff Dev Documentation. ## v1 - [Getting Started](htt”
- [claimed-docs] https://devdocs.veriff.com/llms.txt“Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Run the product headlessly / in CI for automationweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] https://devdocs.veriff.com/docs/how-to-create-an-integration.md“Any verification session done in the test integrations **do not count towards paid usage**.”
- [claimed-docs] https://devdocs.veriff.com/docs/verification-session-decisions.md“You can trigger decisions for test integration sessions.”
- [claimed-docs] https://devdocs.veriff.com/docs/service-quality-testing.md“Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
Plug MCP servers into this product so it can use their toolsweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Connect an agent via an official MCP serverweight 3
3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max
- [claimed-docs] https://devdocs.veriff.com“Pass end-user data via API and check out endpoint behavior”
- [claimed-docs] https://devdocs.veriff.com“Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] https://devdocs.veriff.com“Set up webhooks to get responses from Veriff”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Use an official CLIweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Drive the product through a documented public APIweight 3
3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max
- [claimed-docs] https://devdocs.veriff.com“Pass end-user data via API and check out endpoint behavior”
- [claimed-docs] https://devdocs.veriff.com/apidocs/veriff-public-api-guides.md“the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security.md“Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpose.”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Issue scoped/least-privilege API credentials for an agentweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com/apidocs/veriff-public-api-guides.md“the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security.md“Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpose.”
Build against official SDKsweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com“Bring the end-user to verification flow using web or native SDKs”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security.md“Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpose.”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Subscribe to events via webhooksweight 2
2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com“Set up webhooks to get responses from Veriff”
- [claimed-docs] https://devdocs.veriff.com/apidocs/veriff-public-api-guides.md“the shared secret key, used to create the X-HMAC-SIGNATURE header”
- [claimed-docs] https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security.md“Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpose.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
Agent-ready = 68.0 ÷ 180 × 100 = 37.8
API quality10.0/100×0.20 of the PA blend
The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.
Explore an interactive API reference with runnable examplesweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Download a machine-readable API spec (OpenAPI or equivalent)weight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
- [probe] https://devdocs.veriff.com/llms.txt“PROBE llms.txt: HTTP 200 at https://devdocs.veriff.com/llms.txt # Veriff Dev Documentation > Knowledge base documentation for Veriff Dev Documentation. ## v1 - [Getting Started](htt”
Test against a sandbox environment without touching production dataweight 1
1 (weight) × 7 (quality) × 1.0 (full) = 7.0 of 10 max
- [claimed-docs] https://devdocs.veriff.com/docs/how-to-create-an-integration.md“Any verification session done in the test integrations **do not count towards paid usage**.”
- [claimed-docs] https://devdocs.veriff.com/docs/verification-session-decisions.md“You can trigger decisions for test integration sessions.”
- [claimed-docs] https://devdocs.veriff.com/docs/service-quality-testing.md“Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
Rely on versioned APIs with a documented deprecation policyweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
API quality = 7.0 ÷ 70 × 100 = 10.0
Openness8.6/100×0.20 of the PA blend
Can you leave, inspect, or self-host — data export, open source, portability.
Do everything through the API that I can do in the UIweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] https://devdocs.veriff.com“Set up webhooks to get responses from Veriff”
- [claimed-docs] https://devdocs.veriff.com/docs/hmac-authentication-and-endpoint-security.md“Veriff uses the HMAC-SIGNATURES (as `x-hmac-signature` header or `VRF-HMAC-SIGNATURE` header) and allowed IP lists and ranges for that purpose.”
- [claimed-docs] https://devdocs.veriff.com/llms.txt“Learn how to manually review and manage verification sessions in the Veriff Customer Portal.”
- [claimed-docs] https://devdocs.veriff.com/docs/verification-session-decisions.md“Manually: the **Verifications page in the** Veriff Customer Portal”
- [claimed-docs] https://www.veriff.com/pricing“Export verification session details to PDF”
- [probe] https://devdocs.veriff.com/openapi.json“PROBE openapi: all candidate paths 404 (https://devdocs.veriff.com/openapi.json, https://devdocs.veriff.com/swagger.json, https://devdocs.veriff.com/api/openapi.json, https://devdocs.veriff.com/.well-known/openapi.json)”
Export all of my data in open formats and leaveweight 3
3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max
- [claimed-docs] https://www.veriff.com/pricing“Export verification session details to PDF”
Read the product's source under an open licenseweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Self-host the core productweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Openness = 6.0 ÷ 70 × 100 = 8.6
Built-in AI10.0/100×0.15 of the PA blend
Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.
Get AI-generated insights and suggestions from my data inside the productweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Set up automations that run autonomously in the backgroundweight 2
2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max
- [claimed-docs] https://devdocs.veriff.com“Set up webhooks to get responses from Veriff”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
- [claimed-docs] https://devdocs.veriff.com/docs/verification-session-decisions.md“You can trigger decisions for test integration sessions.”
Delegate tasks to a built-in AI assistant inside the productweight 3
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Operate the product with natural-language commandsweight 2
2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Built-in AI = 6.0 ÷ 60 × 100 = 10.0
Automation15.6/100×0.15 of the PA blend
Depth of automation primitives — rules, scheduling, bulk operations, webhooks.
Perform bulk operations across many items at onceweight 2
2 (weight) × 2 (quality) × 0.6 (partial) = 2.4 of 20 max
- [claimed-docs] https://devdocs.veriff.com/docs/service-quality-testing.md“Batch upload tests are **sometimes** agreed with Veriff onboarding team and are **very use case specific**.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Use this endpoint to **initiate a new verification session** for an end-user. Every verification flow begins with creating a session.”
- [claimed-docs] https://devdocs.veriff.com/apidocs/v1sessions.md“Secondary: Poll `GET /v1/sessions/{id}/decision` endpoint”
Define rules that trigger actions automatically on eventsweight 3
3 (weight) × 3 (quality) × 0.6 (partial) = 5.4 of 30 max
- [claimed-docs] https://devdocs.veriff.com“Set up webhooks to get responses from Veriff”
- [claimed-docs] https://devdocs.veriff.com/docs/verification-session-decisions.md“You can trigger decisions for test integration sessions.”
Schedule recurring jobs or workflowsweight 2
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Version, review, and roll back my automationsweight 1
n/a — not applicable to this product: excluded from numerator and denominator
no evidence cited — the verdict rests on absence of evidence, re-checked on refresh
Automation = 7.8 ÷ 50 × 100 = 15.6