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
0x388a…43770x6e8b…4e2eBaseBasex402 service$0.005100%coinbase133d ago0xe1a4fb…b8cfdc
0x388a…43770xbaf5…53ccBaseBasex402 service$0.03100%coinbase133d ago0x35a5b7…413cee
0x388a…43770x5721…8867BaseBasex402 service$0.001100%coinbase133d ago0x2dc3e6…5fd9a8
0x388a…43770x260f…82b0BaseBasex402 service$0.05100%coinbase133d ago0xc129d8…a205fa
0x388a…43770x6e8b…4e2eBaseBasex402 service$0.001100%coinbase133d ago0x8867b6…d8488c
0x388a…43770xd20f…7d0dBaseBaseNavi Web IntelligenceWeb-scraping$0.001100%coinbase133d ago0x4bcfcb…b139d2

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.