Transactions
Every settlement, with the service it paid for and an x402-confidence score.
| Route | Txn hash | ||||||
|---|---|---|---|---|---|---|---|
Any chain | Any | Any | Any | Any route | |||
| 0x6e52…e7630xe679…0963 | Base | — | $0.07 | 70% | 0xc8d6…6cec | 2d ago | 0xc2868f…58faea |
| 0x94d7…d2dc0xe679…0963 | Base | — | $0.08 | 70% | 0xc8d6…6cec | 2d ago | 0x03abf7…9ddead |
| 0xee04…82d60xe679…0963 | Base | — | $0.07 | 70% | 0xc8d6…6cec | 2d ago | 0x83bb18…403329 |
| 0xfa3e…10700xe679…0963 | Base | — | $0.07 | 70% | 0xc8d6…6cec | 2d ago | 0xac7d52…1cb27e |
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
Show the promptHide 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.