Open Deal is a 5-piece wire protocol for autonomous B2B procurement — ENS discovery, content-addressed catalogs, signed RFQ + quote, onchain escrow, audit anchor on 0G. Bring your ERP. Bring your commerce backend. Write one ~100-line adapter — your agent’s on the network. The framework Anthropic’s Project Deal said doesn’t exist yet.
Set it once. Watch it run. Sign only the edge cases.
Anthropic Project Deal · April 2026 ↗. Their experiment validated the demand. The same report flagged what's missing — confabulation, prompt injection, information asymmetry, no policy framework. We ship those primitives: policy on ENS, signed quotes, audit anchor on 0G. The framework Anthropic says doesn't exist is in PROTOCOL.md v0.1.
“Policy and legal frameworks around AI models that transact on our behalf simply don't exist yet… Society will need to move quickly to reckon with these changes.”
Same pattern, two different runtimes. Their experiment validated that humans accept agent-mediated trade. Ours adds the trust property B2B procurement actually needs: every decision verifiable from chain state alone.
Each tick is a pure function from (books, policy) to (escrow, anchor). Click any step to see the payload.
{
"as_of": "2026-04-25T14:02:00Z",
"low_stock": [
{ "sku": "SKU-A4-PAPER-500", "qty": 12, "reorder_min": 50, "reorder_qty": 240 },
{ "sku": "SKU-TONER-K-002", "qty": 3, "reorder_min": 10, "reorder_qty": 20 },
{ "sku": "SKU-USB-C-2M", "qty": 8, "reorder_min": 25, "reorder_qty": 50 }
],
"open_bills_usd": 4280.00,
"recurring_skus": ["SKU-A4-PAPER-500"]
}Every plugin under plugins/ is a standalone npm-publishable package: openclaw.plugin.json, README, smoke test. The same three power the buyer agent, the seller agent, and the legacy treasury demo. Aligned with ERC-8004 primitives — identity, capabilities, validation — on chains that exist today.
Open Deal is the part that doesn’t change. Everything else plugs in via a typed adapter you write in ~100 lines. Below: 4 buyer connectors and 4 seller connectors already shipped, plus 3 independent reference implementations against the same onchain artifacts. Your stack different? Pick the closest connector as a template.
Heavy multi-step procurement and atomic agent-to-agent purchases are different transactions, with different latency, audit and dispute requirements. Open Deal v0.1 declares both modes and lets sellers advertise either or both via a single ENS text record.
When something physical or non-atomic moves.
When the response IS the good.
procurement.settlement-modes = "escrow.v1,direct.v1"
one ENS text record · sellers advertise either or both · buyers MAY require a specific mode in the RFQ
On the left, an animated replay of the buyer-agent loop — useful for understanding the flow without spending gas. On the right, the artifacts of the most recent real tick — the same pipeline, but on Sepolia, on 0G Galileo, and into a real Odoo instance, fired unattended by a Vercel cron every day.
No marchitecture. Two agents, three plugins, two onchain settlements (escrow on Sepolia, anchor on 0G). Every arrow corresponds to a function in apps/ or plugins/.
┌──────────────────────────────────────────────────────────────────────────┐ │ two agents, one network │ │ │ │ ┌──────────────────┐ ┌──────────────────┐ │ │ │ buyer-agent │ │ seller-agent │ │ │ │ apps/buyer- │ RFQ (HTTP, signed) │ apps/seller- │ │ │ │ agent/ │ ─────────────────────────▶ │ agent/ │ │ │ │ │ ◀───── signed quote ────── │ :3030/catalog │ │ │ └────────┬─────────┘ └────────┬─────────┘ │ │ │ │ │ │ │ each agent consumes the same 3 plugins ─────┘ │ │ │ │ │ ▼ │ │ ┌────────────────────────────────────────────────────────────────┐ │ │ │ plugins/policy-from-ens ─────▶ ENS text records (Sepolia) │ │ │ │ plugins/keeperhub-rail ─────▶ Turnkey wallet · Base/Tempo │ │ │ │ plugins/audit-to-0g ─────▶ 0G Storage + AuditAnchor │ │ │ └────────────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ ┌────────────────────────┐ │ │ │ ProcurementEscrow│ ◀── tx ─────── │ ethers v6 wallet │ │ │ │ Sepolia │ │ 0x13aF…7AC1 │ │ │ │ 0x43b3…60b8 │ └────────────────────────┘ │ │ └──────────────────┘ │ │ │ └──────────────────────────────────────────────────────────────────────────┘
Three real records from agent runs during the build window. Prompt, model output, policy snapshot, and the 0G anchor index that makes them third-party verifiable.
Agent identity openagents-treasury.eth Sepolia ENS · 11 text records Seller subname seller-acme.openagents-treasury.eth Sepolia ENS · endpoint discovery AuditAnchor.sol 0xc4B91f01352cff1191eBd3d15A521D94ED081d89 0G Galileo · 16602 ProcurementEscrow.sol 0x43b31222B22C35D0E5134d03D3f9bb18182360b8 Sepolia · 11155111 Agent wallet 0x13aF7f5B2aD2a230d364cc2484380e711fe17AC1 Sepolia + 0G · same key
PROTOCOL.md v0.1 defines five wire-level specs and three conformance levels (L1 discoverable / L2 settlement / L3 auditable). To prove the spec is real, we ship two independent buyer implementations (TypeScript ~620 LOC + Python ~380 LOC) and a seller (TypeScript ~160 LOC) — all trading against the same ENS records, the same escrow contract, the same 0G anchor. The buyer/seller agents are evidence, not the product. The product is the spec.We talked to operators in two of these and the third is the obvious extension. The framework is the same; only the connectors and policy records change per vertical.
Every shipment is a manual price comparison across a fragmented carrier base. Hours per week per ops person. We talked to two operators — both described the same workflow. Open Deal turns it into a 30-second buyer-agent tick: fan-out RFQ to N carriers via ENS subnames, signed quotes, escrow release on shipment-proof, full audit trail.
talk to us →Cement, rebar, drywall, fixtures, paint. The vendor universe is wide, the comparison is mechanical, the savings compound across the portfolio. PM drops their list (Excel buyer connector), agent compares against N hosted seller catalogs on 0G, human approves only outliers via Telegram. Same framework, different connectors.
talk to us →Three properties define the wedge: high SKU repetition, wide vendor universe, and price-shopping currently done by humans copying numbers between tabs. If your industry hits all three, the framework fits. We're picking design partners for v0.2 — get on the waitlist.
talk to us →Open Deal v0.2 ships in May 2026 with multi-round negotiation, mainnet escrow, and Bridge.xyz off-ramp. If your company feels the procurement-by-spreadsheet pain — logistics, real estate, retail, manufacturing — drop your details. We'll reach out within 48h.