Start a recordOpen app
Trust tools

Trust and data tools

Tools for inspecting the identities, credentials, and product data the Verifable platform works with. Each tool states what it accepts, what it checks, and where the processing happens.

Check an identity or service

Resolves DIDs: did:key in process, did:web fetched server-side. Shows the resolution envelope and the DID document.

Open the resolver — /resolver/

Check a credential

Paste a W3C VCDM 2.0 credential and get a step-by-step diagnostic result: format detection, parsing, issuer resolution, proof verification, validity, and a final verdict. It reads JSON-LD Data Integrity credentials, verified on the server.

Open the credential checker

Validate DPP and UNTP data

Battery-passport credentials in the Regulation (EU) 2023/1542 shape get SHACL-gated, field-level feedback while a passport is being created. UNTP credential families — DPP, DCC, DTE, DIA, DFR — are issuable and verifiable in the sandbox.

Create a passport — /product-passports/issue/ · Issue and verify UNTP credentials — /sandbox/

Inspect CBOR

Paste CBOR hex and get linked hex and Extended Diagnostic Notation views, hover-linked to each other.

Open the CBOR tab in the developer playground — /playground/#cbor

Veritas Workbench

Run SPARQL queries, inspect RDF with source diagnostics and validate data against SHACL shapes. The public Workbench also inspects OWL 2 source; it does not run OWL reasoning.

Open Veritas Workbench — /veritas/editor/

How these tools handle your input

  • Pasted data is parsed defensively and never executed.
  • DID resolution for did:web happens server-side, on the Verifable origin, at /did/resolve.
  • Credential verification in the playground happens on the Verifable server, at /vc/verify.
  • Use synthetic data in public tests. Input is sent to the configured Verifable service; identifier and status lookups can require external services.

More from Verifable