PactwrightWhen an AI agent pays for something, Pactwright holds the money in escrow on Stellar until a verifier checks the delivery against terms agreed before payment. The seller is paid what the delivery earned; the rest goes back.
Live on Stellar testnet. Not audited yet.
4072556402d709463f7cb888a4a9e03b061d906f0b7ca5c49ebb2eec4e7d5c55
A real pact on testnet, 29 October 2026. See it in Studio
An agent has no one to call. So the rules for getting money back are part of the payment.
| If | Then |
|---|---|
| The delivery is wrong | The verifier signs DENY and the buyer gets the whole cap back |
| Only part arrives | The seller is paid for what arrived; the rest returns, in the same transaction |
| Nothing arrives | No verdict comes, and after the deadline the money goes back to the buyer |
| The verifier goes silent | The same: the silence policy agreed up front applies |
| The seller never collects | After the settle deadline, anyone can return the money to the buyer |
| Someone forges or replays a verdict | Rejected: each verdict is signed and bound to one pact and one set of terms |
Nobody can move the escrow outside these rules. Not the seller, not the verifier, not the admin: there is no function that could.
1.00 USDC locked in escrow.
b0103116…290d1a5dThe verifier read the translation and approved 1.00 USDC.
0225f78b…bc8650db1.00 USDC to the seller, 0.00 back to the buyer.
1f4ab38c…23e44924Then the outcome becomes a receipt, anchored on-chain in a batch, so anyone can check later what was paid and why.
Find a seller, buy under a pact, wait for the verdict and keep the certificate. As a TypeScript SDK or as MCP tools.
Buy as an agentOne middleware call puts a route behind a pact: terms in the 402, payment checked before you serve, a signed receipt after.
Sell behind a pactWho can do what, what the contract guarantees, the known limits, and the testnet transactions behind every claim.
Who you have to trust