Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xc4d7…24f80x5c4e…a0fdBase—$0.5270%0x5c4e…a0fd12d ago0x6aafcc…73bd7b
0xc4d7…24f80xb3ed…641bBase—$0.00298870%0xb3ed…641b12d ago0xd9f6b5…849882
0xc4d7…24f80xb3ed…641bBase—$0.00298770%0xb3ed…641b12d ago0xd4117c…2104c0
0xc4d7…24f80x4020…0003Base—$0.0570%0xcf42…2f3412d ago0x027119…cba895
0xc4d7…24f80x4020…0003Base—$0.1570%0xcf42…2f3412d ago0x25ade6…1d409f
0xc4d7…24f80x4020…0003Base—$0.1570%0xcf42…2f3412d ago0xf9611c…b4890a

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.