The developer map of Verifable
Verifable issues Digital Product Passports and the facts around them — signed as W3C Verifiable Credentials, addressed as DIDs, held in wallets, and checked against policy by a PDP before anything is handed back. This page is the developer-facing map of that system: the consoles you can click through, the operations the server actually exposes, and the documents that describe it all in a form a machine can read.
The public query surface uses a shared, temporary example graph. It is separate from your issued records and is available through the Veritas Workbench. DID resolution, CBOR inspection, and credential/passport tools live in the Playground below. If you'd rather read the plain-language story first, start at the homepage.
- UNTP
- W3C VC 2.0
- SD-JWT VC
- OpenID4VCI
- OpenID4VP
- OpenID Federation
- EUDI ARF
- ISO 18013-5
- ISO/IEC 18975
- GS1 Digital Link
- JSON-LD
- SHACL
- SPARQL 1.2
Consoles
Choose a public tool or a signed-in console. Access, storage and supported operations vary by surface; the API reference documents server operations, not every local editor action.
Sign in with existing access or use an invitation. The entry page shows the methods enabled by that deployment; developer access is not a public sign-in method.
Receive supported credentials and inspect activity. Web and native Wallet storage and presentation capabilities are listed separately on the Wallet page.
Resolve a DID or a product identifier straight through the server — no browser CORS wall.
Every agent's entitlements, activity, and pending access requests.
Configure OAuth clients and the relying-party (CIR) register.
PDP decisions, SSF streams, events, and a trace lookup — Day-2 observability.
DID resolution, a CBOR inspector, and credential/battery/building-passport tools, side by side.
API reference
Rendered live from the same OpenAPI document the server emits at build time — grouped the way the consoles above actually use it. Open the raw contract directly at /openapi/verifable-server.json for tooling, codegen, or an agent that wants the whole shape at once.
Machine-readable facts
Use the OpenAPI contract for server operations, Facts for capability status and evidence, and llms.txt for an agent-readable index. All three are linked below.
- /openapi/verifable-server.json The raw OpenAPI 3.1.1 contract — every operation rendered above.
- Facts Each claim with its current status, supporting evidence and known limitations.
- /llms.txt The agent-readable index — the same facts, indexed for an LLM's first read.
- github.com/Lumoin/Verifiable Source.
Self-describing as did:web:verifable.eu.