W Warranty

A refund layer for the Machine Payments Protocol

Agent payments are final.
Warranty makes them safe to make.

When an agent pays an MPP service in stablecoins, the money is gone, even if the service answers with an error, the wrong format, or nothing. Route the call through Warranty: it pays for you, checks the result against your contract, and refunds you automatically when a covered service fails.

–
Calls checked
–
Passed
–
Refunds paid
–
Refunded

Watch it happen

These buttons run a real agent with a funded test wallet against Flaky Weather, a paid service built to break on request. Real payments move on Tempo testnet each time.

How it works

🧾01
Quote

Your agent sends the URL it wants to buy from and a contract. Warranty reads the service's price and answers 402 with that price plus a premium.

💸02
Pay once

Your agent pays Warranty. Warranty pays the service from its own pool and collects the service's receipt.

🔍03
Check

Status, format, JSON shape, size, speed, receipt and price are checked against your contract.

🛡️04
Result or refund

Pass: you get the result and a signed certificate. Fail: the full amount goes back to your wallet, with the reason.

The price is a signal. The premium follows each service's track record: the more often it has failed, the more it costs to cover. An agent can read how reliable a service is from the 402, before spending anything.

Reliability scoreboard

Pass rate over the last 7 days of calls through Warranty. Always read it with the number of calls. No hidden formula.

ServicePass rateCallsMedian timeMost common failure
No calls recorded yet. Run the demo above.

Use it from your agent

One request. No sign-up and no API key: the payment is the authentication.

npx mppx https://warranty-mpp.vercel.app/api/call --network testnet -J '{
  "url": "https://warranty-mpp.vercel.app/api/flaky?mode=garbage",
  "contract": { "status": 200, "content_type": "application/json" }
}'

Agents can read the full guide at /llms.txt.

Honest limits

  • It checks form, not truth. Status, format, shape, size, speed, price and receipt can be checked automatically. Whether the data is correct cannot.
  • Test money. The pool and every refund are on Tempo testnet until this moves to mainnet.
  • New services are checked, not covered. A service needs a track record before failures are refunded. Otherwise anyone could run a broken service and collect refunds on it.
  • Small numbers. Scores come from few calls so far. Read the call count next to every percentage.