Transactions

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

All listed chains.

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x061c…d4990x5d51…d60dBaseBasex402 service$0.50100%coinbase121d ago0xfb31f4…f55b33
0x061c…d499Navi WeatherBaseBaseNavi WeatherWeather$0.004100%coinbase121d ago0x3a4884…80f7bf
0x061c…d4990x1f01…9a2fBaseBasex402 service$0.00670%0x2772…8c17122d ago0xa1ef1e…ec2345
0x061c…d4990x325b…d430BaseBaseStableEnrichExa$0.01100%coinbase122d ago0xd95b96…d0fe9b
0x061c…d4990x8c05…8ddeBaseBasex402 service$0.05100%coinbase122d ago0x028233…010e3b
0x061c…d4990x6302…ad57BaseBaseTripadvisorTravel$0.01100%payAI122d ago0x3cf2ed…c57706

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. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

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