What is Pactwright?
AI agents can already pay for things over HTTP. With x402, a seller answers 402 Payment Required, the agent pays in USDC on Stellar and retries. That covers paying. It doesn’t cover what happens when the purchase goes wrong: the translation comes back in the wrong language, half the pages are missing, or nothing arrives at all. An agent has no one to call, so the rules for getting the money back have to be part of the payment.
Pactwright makes each purchase a pact:
- Before paying, the buyer and seller agree on a condition, for example “a Portuguese translation of at least 4 pages”. Only its hash goes on-chain, so it can’t change later.
- The buyer locks a cap, the most it will pay, in a Soroban contract.
- The seller delivers and signs a receipt over the exact bytes it delivered.
- A verifier checks the delivery against the condition. A model reads the delivery; plain, deterministic rules decide. The verifier signs the verdict.
- The contract pays the seller what the verdict allows and returns the rest to the buyer. If the verifier or the seller goes silent, deadlines return the money automatically.
- The outcome becomes a receipt anchored on-chain, so anyone can check later what was paid and why.
The pieces
Section titled “The pieces”| Repository | What it is | License |
|---|---|---|
| Pactwright-contracts | The pact escrow contract (Rust, Soroban), its tests and the hashing test vectors |
MIT |
| Pactwright-Kit | TypeScript: the agent SDK, seller middleware, MCP tools, CLI, and the verifier service | Apache-2.0 |
| Pactwright-studio | The public record: indexes pacts, anchors receipts, shows each pact’s timeline and checks certificates | MIT |
Payments go through Accensa’s x402 facilitator, which has a pact scheme for opening escrow.
Where things stand
Section titled “Where things stand”Pactwright runs on Stellar testnet. The contract, the verifier, the facilitator and Studio are deployed there, and every scenario (allow, deny, partial delivery, silence, disputes, metered use) has run as real testnet transactions. It is not audited, nothing is on npm yet, and there is no mainnet deployment. Status and evidence has the details and the transaction links.
Where to go next
Section titled “Where to go next”- New here? Read A pact, step by step, then try the Quickstart.
- Selling an API? Sell behind a pact.
- Building an agent? Buy as an agent.
- Checking our claims? Who you have to trust and Testnet deployments.
We never DM first; there is no token or airdrop. Security issues go to a repo's SECURITY.md, not chat. Testnet only — not audited.