The guided journey
Follow one booking from instruction to evidence.
The ATR is hashed before payment. That hash becomes part of the USDC transaction on Arc. The narrator can explain the mechanism while you move through the live site.
The mechanism
Three acts. One ATR.
- 01
Agree
When your agent books, the seller’s terms for exactly what is being bought, room, dates, price, cancellation timeline, are assembled into an Agentic Transaction Record (ATR) for the buyer and the seller. The ATR is named by its hash, SHA-256 over its exact bytes.
- 02
Pay on Arc
Your agent checks the record, then pays in USDC on Arc at Integra Binder’s door. The ATR’s hash becomes the payment’s nonce, a transaction-level link between the payment and the exact record bytes. For this demonstration a booking settles 1/10,000 of its stated price.
- 03
Verify
A buyer, seller, auditor, or arbitrator holding the ATR can recompute its hash and check it against the chain. If the booking is questioned, the record shows what was recorded when it was made.
The complete tour
13 chapters across ten pages; two of them return to a page you have already seen, doing something harder; one is still to come.
- 1
Ask your agent, accept the deal
A live demonstration of Acme’s booking agent. It chooses a fictional catalogue offer, shows the sample terms and guarantees, and, when you accept, your buyer agent books and pays for it.
- 2
At the desk: the guarantee, provable
The hotel’s screen. The desk looks up the booking and sees the agreement it is bound to, verified from the chain, and what it must do if it cannot deliver.
- 3
The catalogue as a travel site
The seller’s real hotel offers, from the same catalogue an agent reads at /api/offers. Filter by city; every card shows the terms that will end up in the record.
- 4
Checkout: your agent checks the record, then pays
The moment the agreement is fixed. Your buyer agent asks to book; Integra Binder assembles a record of exactly what is being bought, on what terms, and asks for payment against it.
- 5
Paid on Arc, bound to the record
The confirmation, with the transaction on Arc whose nonce is the record’s hash.
- 6
Verify any booking from the chain
Paste a transaction hash from Arc and see which record its payment names, and whether that record still matches.
- 7
The seller’s legal front door
The seller’s discovery document at /.well-known/legal-context.json, the way an agent learns where the terms are before it buys.
- 8
Terms you can prove
The seller’s standing terms, published with a hash and served byte-for-byte identical every time.
- 9
Why Arc
Why this demo settles on Arc, Circle’s blockchain built around USDC.
- 10
Four levels of trust
The protocol’s four levels, from a recorded hash to a fully anchored, identity-bound record.
- 11
Agent-to-agent negotiation
A live demonstration of Acme’s booking agent. It chooses a fictional catalogue offer, shows the sample terms and guarantees, and, when you accept, your buyer agent books and pays for it.
- 12
A dispute, settled by the record
The hotel’s screen. The desk looks up the booking and sees the agreement it is bound to, verified from the chain, and what it must do if it cannot deliver.
- 13
Finance export
Every settled booking exported as an accounting feed, each line pointing at its record and its transaction on Arc.