01 /
Understand the flow
Explore verification, evidence boundaries, review states, and the lifecycle of reusable proof.

Programmable trust / Developer platform
Explore the interfaces and patterns behind accountable verification, portable credentials, and governed trust workflows.
Reference preview / These marketing-side guides and examples are local frontend surfaces. API execution, production credentials, and live service status are not connected here.
One protocol. Clear boundaries.
Verification is not just a response code. It is a chain of evidence, decisions, and lifecycle events that your application needs to understand.
Start with the purpose of the request. Keep provenance attached, model review and expiry, and reveal only what the receiving workflow needs.
Start building your understanding
01 /
Explore verification, evidence boundaries, review states, and the lifecycle of reusable proof.
02 /
Review request, response, error, and webhook examples before planning an integration.
03 /
Understand typed requests, retries, server-side boundaries, and safe workflow composition.
Design the whole lifecycle
Build for the cases that matter: uncertainty, expired proof, revoked consent, and decisions that need a human.
Keep identity, tenant context, authorisation, and idempotency at the server boundary.
Model provenance and signed lifecycle events. Do not expose private evidence through public projections.
Show reasons, confidence, expiry, and an appeal path where the workflow requires them.

Built by people. For participation.
Your team should be able to focus on the experience you are creating, without hiding the trust decisions that support it.
Clear contracts and accountable workflows make it easier to reason together about what a system knows—and what still needs review.
Explore the toolkit
Local request and response examples. No production calls.
Operator workflow concepts for inspecting and replaying trust events.
Agent-ready patterns with scoped tools and explicit human review.
Reference journeys for verification and digital participation.
Starting points for evidence-aware frontend workflows.
Review the local change-log surface and its publication status.
Inspect the status preview; not a live operational health feed.
Begin with the model
Explore the verification guides before designing your integration. Keep production access, security review, and deployment readiness as explicit gates.