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
0x1f3c…abd30x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0xd2f468…559ad8
0x74d2…35da0x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0x7a28c7…40767f
0x527a…8e170x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0x5cca7f…0799a5
0x8150…49190x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0x5adfa8…8ceeef
0x97b2…b85f0x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0xdf8e04…e58187
0xae75…d3610x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0x48f11f…79f392
0x0d87…0edf0x17cd…7905BaseBasex402 service$0.05100%coinbase48d ago0x7a3e6c…74cb98

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.