01 /
Verification primitives
Connect identity, document, business, and compliance evidence to a defined workflow. Keep the purpose and review requirements explicit.

Trust API / Programmable infrastructure
An integration layer for verification, credentials, trust context, and lifecycle events—designed to connect the evidence behind a product decision.
One integration. An accountable lifecycle.
Evidence expires. Credentials change. Decisions may be disputed. Trust infrastructure must help a product understand what happened, what remains valid, and what needs review.
Trust API’s architectural role is to connect those primitives without asking every team to invent its own language for verification, proof, and accountability.
The integration foundation
01 /
Connect identity, document, business, and compliance evidence to a defined workflow. Keep the purpose and review requirements explicit.
02 /
Design for authenticated event delivery, retry handling, and lifecycle changes—not just the first successful request.
03 /
Carry provenance, reasons, and review context into the product experience. Evidence should remain inspectable after a decision.
Integration model
Scope the evidence and purpose. Mutating requests require authentication, authorisation, and idempotency.
Validate the event source and signature, account for retries, and distinguish pending work from a final outcome.
Present the evidence and reasons. Escalate high-risk or disputed outcomes through an authorised human review path.
Illustrative request · not executable
POST /v1/verifications
Idempotency-Key: vrf_local_demo
{"kind":"individual","channel":"web"}Use arrow keys to scroll when the sample overflows.
This simplified example illustrates a verification request. It omits authentication and is not a complete or validated endpoint contract. No request is sent from this page.

Built by people. Accountable to people.
For a product team, a reliable trust workflow includes the moments when evidence is missing, an event arrives twice, or a person challenges a result.
The aim is to make those states understandable to builders and the people using their products—not hide uncertainty behind a success badge.
Security is the operating condition
Tenant isolation, scoped access, rate limits, idempotency, and audit integrity belong at the integration boundary. Sensitive personal data should not be exposed in client code or logs.
This page describes the product architecture. It does not certify endpoint availability, latency, compliance coverage, or production readiness. Validate the actual contract and environment before integration.
Review the security approachContinue into the implementation model
Explore API reference material and developer guides before choosing the evidence, event, and review paths your product needs.