Most demos end as a screenshot.
You click a button. Something green appears. You believe the author — or you don't. Tomorrow the tab is gone, and the “proof” is a PNG in a blog post.
We already ship live rails for an agent economy: attested readings, pay-per-call invoke, settlement that can refuse to pay. What was missing was a portable object after the click — something a stranger can reopen, fetch as bytes, and check offline.
So we closed that loop.
use.modelmarket.dev → Run live request → portable AWR/2 receipt → verify.modelmarket.dev with ?receipt_url=…
No account. No “trust our backend.” The Hub seals a signed work receipt; the verifier checks the signature in your browser.
The thesis (one sentence)
If your proof dies when the tab closes, it was never a proof — it was theater.
What you touch (two minutes)
Open the portal. Stay on EN. Scroll to Live proof.
Same weather capability the catalogue sells (~$0.001). The public demo still shows the catalogue price; sandbox demos are charged $0 with a remaining-request counter.
Click Run live request.
You get a signed reading — device, seq, Ed25519 attestation, latency — and then the part that matters:
“The object survives this tab.” Copy proof link · Verify signature locally · Open receipt JSON.
That purple card is not a UI flourish. It is a W3C Verifiable Credential (AWR/2) issued by the Hub (did:key:…), with a canonical receipt_url on the marketplace host.
What “portable” means here
| Step | What happens |
|---|---|
| 01 LIVE | A real reading (e.g. om-wx-01) |
| 02 GAIA | Attested envelope (Ed25519 · seq) |
| 03 HUB | Seals an AWR/2 work receipt + public receipt_url
|
| 04 VERIFY | Anyone opens the verifier with that URL |
The share link looks like:
https://verify.modelmarket.dev/?receipt_url=https://modelmarket.dev/ai-market/v2/p/provenance/receipt/urn:uuid:…
Paste it in another browser. Incognito. Someone else's machine. The verifier fetches the JSON and checks eddsa-jcs-2022 locally.
L0 on purpose: signed by its issuer, and nothing more. No TEE theater on this demo path.
What a valid receipt proves — and what it does not
This is the line we refuse to blur:
It proves: this issuer signed these claims, and the bytes were not altered.
It does not prove: that the physical sensor is truthful, that the model “really ran,” or that the weather outside your window matches the number.
Attribution ≠ physical truth. Pay-on-Verified settlement and LIVE vs SIM labeling on ATLAS exist for the honesty gaps a signature alone cannot close.
Humans get honesty on a map. Agents buy the reading behind the pin. Same provenance grammar.
Why this changed the portal
The five doors article was about finding the rails.
Portable proofs are about leaving with evidence.
HN comment, investor chat, design-partner email — you no longer paste vibes. You paste a URL that either verifies or fails closed. That is the Basescan-shaped habit for physical invoke: citeable, durable, boring in the best way.
Same pattern lands on the idea lab demos (Fire + Weather, Verified Watchbox): invoke → capsule → verify. One object class everywhere.
Try it
- use.modelmarket.dev → Run live request
- Copy proof link or Verify signature locally
- Optional: curl the same SKU from the page (visitor header included in the snippet)
Repo (MIT): github.com/alexar76/aicom
Verifier source / npm: @alexar76/awr-verify
Map: atlas.modelmarket.dev
If it helped, a ⭐ on the repo is the softest possible thank-you. Brutal feedback on the proof UX is better.
—
AIMarket — verifiable provenance · agent economy · crypto optional
Top comments (0)