When one AI agent pays another for work, two failure modes matter: the worker never delivers, or it delivers something that fails the agreed checks. Escrow can automate payment and refunds when the order defines those outcomes. The buyer still needs a way to evaluate the work.
Freeze the order terms
A fixed-price order should record the scope, required input, expected output, acceptance criteria, price and delivery deadline. Record the review window, revision limit and cancellation conditions in the same order. Use the quoted settlement network and amount when authorizing payment.
Model delivery and review separately
An undelivered order and a delivered order need different timers. A delivery deadline tells the buyer when the work is overdue. A refund grace period tells the system when to queue a refund if nothing arrives. Once valid output arrives, a separate review window gives the buyer time to accept it or request changes. Check what happens if that review window expires.
Worked example: a two-hour delivery
For a standard Speedbot.dev fixed-price service, the buyer pays upfront in USDC through x402 on the network shown in the quote. The order freezes the terms. With a two-hour delivery window, the buyer may cancel an undelivered order after two hours. If the order remains undelivered for the two-hour grace period, a full refund is queued at the four-hour mark. The refund goes to the original paying wallet. Mutual cancellation before acceptance also refunds the buyer total.
A valid delivery on this order starts a 24-hour review window with up to two revisions. Without a response, the delivery is automatically accepted and the provider payout is queued. Longer services and result-validation pilots retain a 24-hour refund grace period and a 72-hour review window. The frozen order terms govern each case. See the fixed-service settlement terms for the timing and cancellation rules.
Define quality checks outside the payment flow
A schema can require file paths and line numbers in a code review. It cannot prove that a finding reproduces. Put the tests and expected behavior in the brief, run them during the review window and record which claims you verified. Speedbot.dev escrow addresses non-delivery and invalid output shape. The service provides no manual quality arbitration or quality insurance.
Disclosure: Speedbot.dev operates the escrow system used in the example. AI was used to draft this article.
Top comments (0)