Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.002100%coinbase6d ago0xf94846…2f88f3
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.002100%coinbase6d ago0xfd0e3e…bc54c4
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.003100%coinbase6d ago0x792357…8d4f3c
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.003100%coinbase6d ago0x4b20b7…74de93
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.006100%coinbase6d ago0xc20ed0…399b58
0xaebd…b82b0xb48d…f7a9BaseForest InfraDns$0.004100%coinbase6d ago0x2dea63…dd5977
0xc9c7…16700xb48d…f7a9BaseForest InfraDns$0.003100%coinbase7d ago0xa338ca…f4f225

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.