Evaluate the proof before you integrate it.
This is a short way into the material: follow a live flow, inspect its artifacts, and then use the reference documentation for endpoints, protocol details, and deployment boundaries. It is an orientation page, not a replacement for the docs.
Four useful places to start.
Each route has a different job: documentation explains the interface, the wallet flow exercises standards-based messages, evidence records what was observed, and demos make a narrow decision visible.
Read the interface and the limits.
Start with the implementation guides, API entry points, selective-disclosure concepts, rejection behavior, and production-boundary notes. Use this route when you need the long-form technical reference.
Open reference docs →
wallet round-tripWalk an OID4VCI and OID4VP flow.
Issue a demo credential and request a minimally disclosed age presentation using a compatible wallet path. The page identifies its demo issuer, holder binding, and trust-anchor limits as part of the flow.
Open the wallet round-trip →
artifacts and claimsInspect what the results are based on.
Trace published statements to dated artifacts, local conformance runs, wallet-interoperability records, test outcomes, and the claims register. A result should be independently inspectable, not merely persuasive.
Open evidence →
live demo catalogObserve a bounded decision live.
Run the reference demonstrations for age verification, organizational proof, agent delegation, payment controls, and governed risk. Each says what executes on this deployment and what remains simulated or reference-grade.
Browse live demos →
Test the small thing first.
- Choose one decision. Start with a threshold, a holder-bound action, a delegation cap, or a verifier rule—not a broad identity rewrite.
- Run the matching reference flow. Watch the accepted and rejected paths, then inspect the response and the stated demo boundary.
- Read the artifacts and interface. Match the evidence to the relevant documentation before deciding what would be required for your own deployment.
Use the live flow as a question, not a promise.
If a reference path fits your evaluation, the longer docs and evidence ledger make it possible to frame a scoped technical discussion without treating a demo as a production commitment.