R

Recourse

A risk layer for x402 on Algorand

connecting… app — asset — agent — events

x402 gives agents the ability to pay. Recourse gives them a reason to trust what they are paying for.

Providers stake a bond on Algorand and publish a machine-readable SLA. Agents check reliability and bond coverage before paying. When a provider signs a response that violates its own published SLA, the agent proves it on chain and compensation comes out of that provider's bond — refund, slash and counter update in one atomic application call.

Algorand TestNet GoPlausible facilitator x402 · exact · AVM Machine to machine
—
Providers bonded
—
Total bonded
—
Claims upheld on chain
—
Slashed from bonds
—
x402 payments settled
Recourse app · TestNet
—
x402 payment settled
awaiting first payment
Bond deposit
awaiting bond
Upheld claim · refund + slash
awaiting first claim
Facilitator
GoPlausible
◆

Routing decision

Which provider the autonomous agent will pay next, and why
Waiting for the first routing decision…
An agent explores an unmeasured provider because its bond, not a reputation it cannot yet have, is what protects the buyer. Once there is enough evidence the score governs — and a provider whose bond is gone is removed from routing entirely.
Machine to machine. This page is an observer. It holds no keys and cannot pay for anything. The button starts an autonomous agent that holds its own Algorand keypair, declares its own spend limit, and then decides where its money goes with no human approving any individual payment.

Bonded providers

Live from box storage on Algorand TestNet
Loading providers…

Live call feed

Every x402 payment, verification and claim as it happens
No activity yet. Press Start the agent and it will begin buying over x402.