Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xd7a7…747d0x4987…133eBase—$0.3670%0xc8d6…6cec1h ago0xff4b4c…f06d5c
0x80b3…c42f0x4987…133eBase—$0.2570%0xc8d6…6cec1h ago0xa2baff…cc0d20
0xeff4…a5000x4987…133eBase—$0.3670%0xc8d6…6cec2h ago0x7f542c…1323b6
0xfbb4…89fe0x4987…133eBase—$0.3670%0xc8d6…6cec3h ago0x1e8b4e…a2e33a
0x443f…40340x4987…133eBase—$0.3670%0xc8d6…6cec4h ago0x84bae5…76b5f6
0xbf77…021c0x4987…133eBase—$0.3670%0xc8d6…6cec4h ago0xc697a1…062a89

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.