Docs / Start here
Who it is for
Three audiences meet in LOPW. An agent wants to pay only services that stand behind their promises. A seller wants to be that service. A platform wants to show or score bonds without a wallet.
Agents and the people who run them
Your agent pays small amounts, often, to services nobody vetted by hand. With the buyer SDK it reads a seller’s live state, stake and terms before paying, refuses anything outside its policy, verifies every receipt, and files a claim on its own when a promise is broken.
| You get | You do |
|---|---|
A policy the SDK enforces before money moves: minStake, requiredPredicates, minMaxClaim, requireWarranty | Install @lopw/buyer-sdk, create a LopwBuyer with a funded key, call agent.fetch(url) |
A warranty record with every check result, the breaches found and the time until which a claim is possible | Keep receipts until their claim windows close (the FileReceiptStore does this for you) |
| A payout from the seller’s stake when a breach is proven, in one transaction | Call agent.claim(warranty) inside the window |
Start with Getting started for agents.
API sellers
You already sell over x402. LOPW lets you say, in a form a machine can check, exactly what you promise and how much you are willing to lose if you break it. Agents with a policy read that before they pay; the stake is the signal.
| You get | You do |
|---|---|
| Offers and receipts signed automatically on every 402 and every paid response, with no change to verify or settle | Register a service with its terms and a dedicated Ed25519 signing key; deposit at least 100 USDC |
| Terms you choose: any subset of P1 to P6 with your own limits, and a claim window up to 24 hours | Add the lopw extension to your x402 resource server and report freshness or oracle evidence through two response headers |
Protection against over-exposure: one receipt pays at most max_claim, and at most 50% of stake can leave in one epoch | Keep stake above your minimum; rotate the signing key if it is ever exposed |
Start with Getting started for sellers.
Platforms, dashboards and marketplaces
Everything LOPW does on-chain is public: every service’s state and stake, every claim, every event. A read-only HTTP API serves it as JSON with cursor pagination, ETags and a live event stream, so an app, a mobile client or a directory can show bonds, rank services by stake, or alert on suspensions without running a node or holding a key.
Start with Getting started for app builders and the HTTP API reference.
Protocol engineers and researchers
The protocol reference describes every type, hash, predicate, function and error exactly as the contracts implement them, with shared test vectors. The deep dive covers the threat model, the economics and the reasoning behind each rule.