Transactions

Every settlement, with the service it paid for and an x402-confidence score.

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xbb5d…71a90x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0x64299c…285474
0x843b…c4a70x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0x3bdecd…767d9c
0x843b…c4a70x6302…ad57BaseTripadvisorTravel$0.15100%payAI19d ago0xfdeaaa…6b7d63
0xc9c7…16700x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0xf96141…a2f916
0xbb5d…71a90x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0x8de468…f8cc30
0x1400…b8bd0x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0xff4305…9b3934
0x1400…b8bd0x6302…ad57BaseTripadvisorTravel$0.01100%payAI19d ago0xa875c0…c6ba82

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will pull the settlement ledger and summarise what is moving over the free read API. No key, no account.

GET api.roundhouseai.io/v0/transactions

Open skill.md
Show the prompt
Using Roundhouse, show me the most recent x402 settlements and tell me what stands out —
which merchants are being paid, typical amounts, and anything unusual.

curl -s 'https://api.roundhouseai.io/v0/transactions?limit=100'

Amounts are USD; `x402_probability` below 0.5 means the payment is probably not x402.
Report per-payer and per-merchant figures only — site-wide totals live at https://roundhouseai.io/stats.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.