Digital Product Passports · personal and business Wallets · accountable agents

Our world, flourishing.

Carry credentials across life and work. Keep products useful through repair, reuse and trade. Work with people, organisations and agents, with clear permissions and evidence of what happened.

Create a Product Passport Open Wallet See an accountable repair

Product Passport creator

Work from a complete example, a governed profile, or data you already have.

Select a product. The same workspace changes in place: fields, source mapping, evidence, identity level and carrier. The default garment is ready for the repair journey below.

Complete example

Immediate result Editable item record · sources mapped · carrier ready

Continue in the creator

This example changes locally in your browser. Continue when you want the full creator, mappings and validation views.

Recipient views

Give each recipient the detail and actions their role requires.

Access and precision are separate decisions. A field can be shared as an exact value, range, threshold, proof, reference or protected fact while its canonical source remains intact.

Selected fieldFibre composition

source retained

62% organic cotton · 31% recycled nylon · 7% elastane

Recipient: Tailor
Access: View item measurements · append repair event
Precision: Exact item measurements and composition
Protected: Dye formula · supplier prices

Meaning and evidence remain attached supplier declaration → canonical material composition → recipient projection Continue with this view

Personal and business Wallets

Carry what matters across life and work.

Discover possibilities you can trust, choose which ones to pursue, and act with people, organisations and agents. Decide what to share and what to authorise, while shaping your own life and caring for the world around you.

See the request, authority and expected result before you decide.

Open Web Wallet See this Wallet decision

Test a Wallet Native Wallet · controlled beta Trust workspace

VVerifable WalletPersonal context · illustrative request

Ready to review

Alter one garment

Allow an independent tailor to repair item 0438.

Requested by the garment owner · counterparty qualification verified for this example

Acting as: Garment owner · personal Wallet
Counterparty: Independent tailor · cross-border service
Share: Item measurements · composition · repair instructions
May do: Read selected fields · append one repair event
Terms: One item · seven days · agreed price
Expected return: Signed repair event · receipt · updated care note

Local decision preview · signing happens in the Wallet

Accountable agents

Let agents carry work forward while authority stays visible.

Follow one repair: an agent prepares the permitted item view and a bounded alteration for the owner to consider. The Wallet keeps visible who it serves, what may be shared and changed, when authority ends, and what evidence should return.

Authority arrives

Established service partner

Principal: Manufacturer service organisation
Proof: Enterprise identity chain · destination policy
Scope: Repair partner role · this product family · active contract
Expires: When the service relationship ends

Common bounded operation

View repair measurements
Propose alteration
Append accepted repair event

A repairer can price one alteration from the permitted item view. The accepted event returns evidence for the invoice; design files and supplier terms keep their governed views.

Policy and result

Authority input modelled
Policy request shaped
Checkpoint determined by policy
Receipt fields assembled

Choose a route, then preview the same operation model.

Inspect the operation envelope

{
  "principal": "did:web:service.example",
  "agent": "urn:agent:service-repair-assistant",
  "resource": "urn:product:item:work-jacket:0438",
  "action": "appendRepairEvent",
  "proposal": { "repair": "shorten sleeves", "quote": { "amount": "68.00", "currency": "EUR" } },
  "limits": { "item": "0438", "expiresIn": "7d" },
  "policy": "destination-decision",
  "result": "attributableRepairReceipt",
  "commercialHandoff": "evidenceForInvoice"
}

Explore accountable agents Open the Wallet Playground

Implementation and interoperability status

On 10 August 2026, Lumoin committed Verifable to the OpenID Foundation AIIM OAuth/CIMD/ID-JAG MCP Security Interoperability Event. The full operation and authority contract is implemented, and the hosted OAuth-protected MCP reference is now integration-tested in Verifable.Server. Its named public origin is not activated here, and partner-result evidence remains to be recorded. KYA-OS is the named portable DID/VC authority route beside it. The public Sandbox and Wallet Playground make Wallet ceremonies and their protocol outcomes inspectable; the MCP and ID-JAG proving loop belongs to the separate agentic interop case.

The same operation in different work

Use identity, recipient views, authority and receipts across fields.

Select a field below. The task changes while the accountable structure stays legible.

IdentityGarment item
Recipient viewMeasurements · instructions
AuthorityQualified tailor
WorkAlter · repair
ReceiptRepair event

A tailor receives the exact item information and one bounded update right.

Open this setup

Read the complete application matrix

Field	Identity	Recipient view	Authority and work	Receipt
Garment	Item	Measurements and instructions	Tailor repairs	Repair event
Equipment	Existing asset ID	Model, warranty and fault	Technician services	Maintenance event
Battery and electronics	Batch or item	Condition and handling	Collector or repairer assesses	Intake or second-life event
Packaging	Batch or pool	Material and reuse rules	Logistics actor returns or washes	Batch event
Metals	Material lot	Exact value, range, threshold or proof	Buyer or recycler processes	Material event
Buildings and reuse	Reclaimed component lot	Dimensions, condition and availability	Owner, inspector and receiving project match and reserve	Removal, receipt and reinstallation

Agent operation model

Inspect the exchange, handoff by handoff.

Begin with one repair job. See what the tailor receives, what stays protected, how the owner decides, and the JSON-RPC request a deployed MCP client can make. The item and outcome are illustrative. The hosted product_passport_get binding, policy-governed read and trace-linked action evidence are implemented and integration-tested; this public page does not execute them. Check the implementation evidence.

See the accountable operation Open the Lab contract

repair-job-0438 / worked exchange worked scenario · tested binding · public execution off

Result

A tailor can price one repair without seeing the design file or supplier terms.

The permitted view carries exact item measurements, composition and care instructions. The owner’s Wallet decides whether to accept the quote and allow one repair event.

Job: Shorten sleeves · 67 → 62 cm
Quote: €68 · independent tailor
Owner decision: Share repair view · allow one event
Expected return: Repair receipt · evidence for invoicing

{
  "@id": "urn:product:item:work-jacket:0438",
  "type": "RepairProposal",
  "repair": "Shorten sleeves from 67 cm to 62 cm",
  "quote": { "amount": "68.00", "currency": "EUR" },
  "requestedView": ["measurements", "composition", "care"],
  "requestedAction": "appendRepairEvent",
  "recipient": "independentTailor"
}

{
  "jsonrpc": "2.0",
  "id": "repair-view-0438",
  "method": "tools/call",
  "params": {
    "name": "product_passport_get",
    "arguments": { "productId": "urn:product:item:work-jacket:0438" }
  }
}

The validated token—not the request body—carries the caller, tenant, represented principal and disclosure tier. The hosted binding applies policy and records a trace-linked read; this public origin advertises no callable MCP endpoint.

Implementation evidence

One complete journey

A garment repair across organisations.

Follow one existing passport through a repair request, two ways authority can arrive, a precise decision and a returning receipt.

01 / 05 Existing passport record

Existing passport

The garment already carries identity, material facts and care information.

Existing product data and retained evidence already give this item a useful record.

Wallet request

Its owner asks for a repair and sees the expected result.

The request names the item, required fields, price, time window and the receipt that should return.

Two ways authority arrives

An established partner and an independent tailor converge on the same bounded task.

Each brings evidence of who they are and what they may do. The product owner’s policy applies to both.

Exact decision

The Wallet reveals the necessary measurements and repair right.

The approved view carries the measurements and repair right; design and commercial facts continue in their governed views.

Returning evidence

An accepted repair would return as an event and receipt.

The product record, warranty, contract and permitted reporting views can continue from the attributable result.

Explore the accountable operation

Many hands make light work

Choose what to work on next.

Start with something you want to make, repair, share or organise. Bring the relevant records, involve the right people and decide what to do next.

Create or import a product record Explore the Wallet Connect software or an agent Plan an organisational deployment