Overview
A shop an AI agent can buy from, with proof of what was agreed
This shop was built in three parts, and each one is shown in this panel.
- Studio build. A written description sent to the Integra Demo Studio became a complete shop in about four and a half minutes.
- AI design. The Studio's shop was finished: official logos, real product photos from Printify, a light look.
- Full functionality, added with Claude. Card payments through Stripe and printing and shipping through Printify, in test mode for now.
The point: the appliance comes with every Studio shop
Every shop the Studio makes is wired to Integra's appliance from its first minute, without the shop writing any of it. For every purchase the appliance issues an agreement record: what was sold, at what price, to whom it is paid, and under which terms. The record's SHA-256, called H, rides inside the payment itself, so a payment can only settle to the payee its agreement names, and anyone can later prove which terms a buyer accepted, from public data alone.
| What the shop wrote | a description, and about 580 lines the Studio's model generated: pages, product list, terms, look |
|---|
| What it got for free | about 28,000 lines of Integra's kit: the appliance's agreement records, payment bound to H, proof pages, and doors for AI agents (UCP, MCP, A2A, MPP, AP2, x402) |
|---|
| How it rates | Integra Lens: all four stages for the Studio shop: Discoverable, Agreeable, Transactable, Provable |
|---|
Two shops, one design
- The Studio shop (integra-lens-merch-live.demos.integraledger.net) is fully wired to the appliance. AI agents buy there on a test network, and every purchase has its agreement record and proof page.
- This shop (integralens.store) takes card payments through Stripe and sends orders to Printify. Each Stripe payment carries the hash of the terms the buyer accepted; recording those orders as agreements in the appliance is the next step.
Part 1 of 3 · Generated by the Integra Demo Studio
Studio build
The shop began as a written description sent to the Integra Demo Studio (studio.integraledger.net). Here it is exactly as the Studio generated it, with nothing changed by hand:
![]()
The prompt, in two parts
Make the Integra Lens Merch Shop: official merchandise for Integra Lens … and for the Legal Context Protocol (LCP) … Design it as a polished, modern apparel brand's shop … The seller is Integra Ledger, Inc. Prices are in US dollars, exclude sales tax, and hold until 2026-12-31.
The second part asked for complete terms of sale (ordering, payment, shipping, 30-day returns, refunds, liability, privacy, governing law), an artwork licence (the printed images may be used only as part of the product). One long prompt was cut off at the model's limit; two shorter turns built cleanly.
What the Studio produced
| Built in | about 4½ minutes, two turns |
|---|
| Written by the model | about 580 lines: pages, product list (business.json), terms, look |
|---|
| Supplied by the kit | about 28,000 lines: checkout, the appliance's agreements, agent doors, proof pages |
|---|
| Studio's own checks | 12 of 12 passed: build, every page at desktop and phone width, contrast, every product taken to checkout as an agent shops |
|---|
| Integra Lens | all four stages |
|---|
A gap found on the way: the Studio could not state the seller's legal name, the tax basis or how long prices hold. That was added to the Studio the same day (Studio v2), and the shop generated again.
Open the Demo Studio ↗
Part 2 of 3 · The design pass
AI design
The Studio's shop was finished in a separate, visible pass, with AI tools and by hand.
- Official logos. The Integra Lens and LCP marks are the real artwork files. An image model never draws a logo here: on its own it garbles lettering.
- Photographs. The hero and the sweatshirt's photos are Printify's own mockups of the real blank it prints on, made in Printify's mockup tool and read through its API.
- A light look in place of the Studio's dark one, a two-column product page, and faults in the generated code fixed: a button whose label was green on green, and a React hook used out of order.
- Print files for Printify: 4500 × 5400 px at 300 DPI, transparent, with the official marks.
The Studio's own checks were run again after the pass: 12 of 12. The design pass touched only the shop's own files; the appliance wiring in the kit was left exactly as the Studio made it.
See the designed Studio shop ↗Its Lens report ↗
Part 3 of 3 · Added with Claude
Full functionality
This shop, integralens.store, is the designed shop made fully working for people paying by card, in test mode for now: nothing is charged, printed or shipped.
The terms, by their hash
The terms of sale are published at /terms.md, and their SHA-256 at /.well-known/legal-context.json, where the Legal Context Protocol says an agent should look. At checkout the buyer agrees to them, and the hash travels inside the Stripe payment (lcp:sha256:0xb49f…6adf), so the payment records which terms were accepted.
Payment: Stripe
Check out with Stripe opens Stripe's own checkout page, which takes the card and the shipping address. Until real payments open it runs in Stripe's test mode. Beside it, a For developers box opens the same checkout in test mode, with the test card 4242 4242 4242 4242 (any future date, any CVC, any ZIP). Prices come from the shop's own list on its server, never from the browser.
Printing and shipping: Printify
A paid order goes to Printify through its API: product, colour, size, quantity and address. A test order is created labelled TEST, do not print and held, so it costs nothing and can be seen in full.
A real test run
| Bought | 1 × Wear the Standard Sweatshirt, Light Blue / M |
|---|
| Stripe | pi_3UMbseGxdkO4DZqd1b9c8eFO, paid, $5.99 ($1.00 + $4.99 shipping) |
|---|
| Terms | carried in the payment by their hash |
|---|
| Printify | 6ac1888b3b4f4b99e90077ce, held as a TEST order |
|---|
Not yet
Card orders are not yet recorded as agreements in the appliance: the Stripe payment carries the terms' hash, but there is no agreement record or proof page for it yet. That is the next step, and the Studio shop shows what it will look like.
Try it: buy the sweatshirtThe run's details ↗Stripe's receipt ↗
Deep dive
The appliance: what every Studio shop is wired to
Integra's appliance is the service that turns a purchase into an agreement anyone can check. A Studio shop is wired to it by Integra's kit, so the shop itself writes none of what follows: it describes its products and terms in business.json, and the kit does the rest.
1 · An agreement for every purchase
When a buyer, a person or an AI agent, starts to buy, the appliance issues an agreement record for that purchase: the offer, the price and currency, the network and token, who is paid, the address and hash of the terms, and what the buyer gave (a name, an address, a size). The record's SHA-256 is H.
2 · H rides inside the payment
The payment carries H itself. On the x402 rail the buyer's signed USDC authorization (EIP-3009) uses H as its nonce; under MPP and AP2 it rides in the credential and the mandates. Integra's facilitator settles a payment only to the payee of the agreement at the H it carries. So the money cannot go anywhere the agreement does not say, and the payment on the public ledger points back to its agreement.
3 · The agreement store
The record is kept in the agreement store (atr.demos.integraledger.net): written by the appliance under a signature, and readable by anyone as its exact bytes at /atr/<H>. Hash those bytes and you get H again. (The demonstration store keeps an agreement for 30 days.)
4 · A proof page for every purchase
Every purchase gets /proof/<H> on the shop: the agreement, hashed again in your browser; the same value shown in each of the places it lives; where the money went; the agent's signature, where there was one; and each check as a command to run yourself.
5 · Doors for AI agents, all carrying H
| HTTP and x402 | /buy/<offer> answers 402 with a payment challenge that names H |
|---|
| UCP | checkout over REST (/checkout-sessions) and over MCP (create_checkout … complete_checkout), with orders and webhooks |
|---|
| A2A | an agent card and the skills search_catalog, get_terms, negotiate, buy |
|---|
| MPP, AP2 | the same agreement, carried in MPP's credential and AP2's mandates |
|---|
| Published | legal-context.json, terms.md, the UCP profile, OpenAPI, llms.txt, the AI catalog, the MCP server card |
|---|
A real purchase you can check
On 3 October 2026, Integra Lens made a test purchase from the Studio shop. We checked every link of it:
| H | 0x50ecfbf0acd3456730ff83829437393b161fc5542f54b341d0802bea1415134a |
|---|
| The agreement record | 2,958 bytes at the agreement store; its SHA-256 is exactly H |
|---|
| The payment | 0xf6380eaa…a379e on Base Sepolia, succeeded, carrying H |
|---|
| Integra Lens | verified the binding from public data alone: the stage Provable |
|---|
Its proof page ↗The agreement record ↗The payment ↗
How easy it is
- Describe the shop to the Studio. It writes
business.json (products, prices, terms, seller) and the pages.
- Publish. The kit wires the appliance, the payment binding, the proof pages and every agent door. No line of it is the shop's to write.
- Check it with Integra Lens. This shop's Studio version reaches all four stages.
For card payments, as on integralens.store, the same pattern applies: issue the agreement, carry H in the payment's metadata, and keep the record in the store. That is the next step here.
For developers
Specs
What an agent reads on integralens.store
/.well-known/legal-context.json | the terms' address, format and SHA-256 (Legal Context Protocol) |
|---|
/terms.md | the terms of sale, as served and hashed |
|---|
/products.json | the catalogue, in Shopify's format |
|---|
/llms.txt, /sitemap.xml | where an agent starts |
|---|
| product pages | schema.org data: price, currency, tax basis, delivery, how long the price holds |
|---|
The shop's API
POST /api/checkout | opens a Stripe Checkout session, priced on the server |
|---|
POST /api/stripe/webhook | Stripe's signed notice of a paid order; sends it to Printify |
|---|
| Printify | POST /v1/shops/{shop}/orders.json, held unless approved |
|---|
Integra Lens's results
| The Studio shop | all four stages · 25 checks met |
|---|
| integralens.store | Discoverable and Agreeable · 17 checks met. Card checkout is built for people; the agent-payment stages belong to the Studio shop. |
|---|
How it runs
integralens.store is a Cloudflare Worker: the pages are static files, and only /api/* runs code. Secrets (Stripe, Printify) live in Cloudflare, never in the code. The Studio shop runs on Integra's demo hosting, with the appliance, the agreement store, the facilitator and the buyer agent behind it.
This shop's Lens report ↗Check any site with Integra Lens ↗
