VerifableStart a record
Lab

Build the request, decision and receipt.

Start with a working exchange, shape the data, inspect each handoff and carry the result into your own application. Choose the surface that matches the job in front of you.

Inspect one bounded agent operation

Tailor repair contract

Two authority rails, proved through the same operation.

The enterprise and portable routes must converge on the same resource, requested action, field view, policy decision, proposed change and attributable receipt.

Interoperability track

OAuth, CIMD and ID-JAG

CIMD server resolution, ID-JAG mint and redeem, RFC 9207 issuer handling, client creation and a dual-era OAuth-protected MCP server binding are implemented and tested in VerifableSystem. On 10 August 2026, Lumoin committed Verifable to the OpenID AIIM MCP Security Interoperability Event. The current /mcp/{segment} binding has four tools: resolve_did, sparql_query, public dpp_chain_walk and governed product_passport_get. The passport read derives caller, tenant, represented principal and disclosure tier from the validated token, applies AuthZEN and records trace-linked dpp.passport.read action evidence. This public origin advertises no callable endpoint and has no accepted partner result. The full product contract keeps represented authority, per-operation policy, permitted disclosure and attributable evidence together whenever a governed product operation is bound. Commitment is not certification.

Named target route

KYA-OS — portable DID/VC authority

This second offering sits beside OAuth/ID-JAG. The full portable-authority contract covers Entity Card and ZCAP-LD delegation, KYA headers, per-call proof, revocation and the Product Passport operation. This public deployment does not activate or provide end-to-end evidence for that binding.

Live runtime

Public interoperability Sandbox

Run Wallet issuance and presentation against the test tenant; inspect published Product Passport and trade profiles and the stages that are not yet executable.

Run the available ceremony →
Directory + runnable test

Wallet Playground

The France Identité-inspired pattern connects each wallet, issuer or verifier entry to its documentation and available test action. France Identité onboarding and a dated external exchange remain pending. This is separate from the Developer Playground.

Choose a system →
principal + agent resource + action limits + evidence policy + diff result + receipt

The full operation contract is the invariant. VerifableSystem now has a local stdio reference and a hosted Streamable HTTP server binding; product_passport_get is the integration-tested governed read over that hosted binding. This public origin publishes neither a hosted MCP URL nor partner evidence. Identity and authorization remain separate from the transport, while governed product operations keep their policy, disclosure and receipt contract.

Choose a working surface

Start from your task

Start with the public OpenAPI contract and the agent-readable capability boundary. Both stay on the same public origin as the working surfaces above.