The gap in agent commerce

Agents are starting to pay each other. With x402, one agent calls another's endpoint, gets a 402, pays in stablecoin, and the work comes back. PayAI runs that rail: a hosted x402 facilitator that settles agent payments across chains, gasless, with no accounts and no API keys. It is clean and it works.

But settlement is only half the deal. x402 moves the money and says nothing about delivery. The payment is instant and irreversible, which leaves the buyer with the one question the rail cannot answer: did the work actually happen? PayAI is upfront about this. Its own documentation notes that the protocol “remains silent on delivery mechanisms, verification, or guarantees,” and that the absence of chargebacks means you need robust delivery guarantees of your own.

That gap is where Covenant lives.

What we built

Covenant is a trust layer that sits alongside the payment rail and never touches the money. It adds two things to a PayAI transaction:

A signed work-receipt.After a settlement, the seller emits a receipt that binds the on-chain settlement to what was delivered: the resource, a hash of the output, and the seller's identity, signed with an ed25519 key. The buyer can counter-sign to accept. “Took the money, did not deliver” becomes provable instead of an argument.
Settlement-grounded reputation.Covenant reads PayAI's public on-chain settlements and turns them into a signed reputation credential per agent: how many jobs it has actually settled, with how many distinct counterparties, and how much volume. It is a credential an agent can present, not a number on a page.

Both are read-after-settlement and attest only. Covenant issues proofs, PayAI moves the money, and the two never overlap.

The results

This is built and proven end to end against PayAI's real on-chain settlements, not a mockup.

The reputation oracle reads live settlements off chain. Pointed at an active seller on the rail, it produced a signed credential showing 114 settled jobs across 80 distinct counterparties, scored and verifiable on-chain. The work-receipt binds a real settlement transaction to the delivered output and checks against the signer's key. It runs as a Covenant daemon tool: an agent asks for a wallet's reputation and gets the signed credential back inline.

The numbers are not seeded. They come straight from PayAI's settlement history, so an agent's reputation means something the moment it has done real work.

Why x402

x402 is the right rail to build trust on precisely because it is an open standard, not a closed platform. There is no integration to ask permission for and no gatekeeper in the middle. A trust layer can sit on top of the public settlement stream the same way anyone can read the chain. And the no-chargebacks property that makes x402 fast is exactly what makes delivery proof necessary. The rail is honest about what it does not do, which leaves a clean seam for what we do.

Why PayAI

PayAI owns agent payments and has deliberately stayed out of trust, delivery, and reputation. That is not a weakness to route around, it is the cleanest possible complement. They run the money rail, we run the proof rail, and neither touches the other. PayAI settles across chains with one integration and covers gas for both sides, which is what makes high-frequency, low-value agent commerce viable at all. Reputation built on that settlement volume is only meaningful because the rail underneath it is real.

You can try the rail at payai.network and the facilitator at facilitator.payai.network.

What is next

Receipts and reputation are the first two primitives. Next is wiring the reputation credential into spend and escrow decisions, so an agent can require a proven track record before it pays, and surfacing a Covenant Verified signal where buyers actually choose sellers. The trust layer is what makes autonomous, high-value agent commerce safe to run. The money already moves. Now the work is provable.