Transactions
Every settlement, with the service it paid for and an x402-confidence score.
| Route | Txn hash | ||||||
|---|---|---|---|---|---|---|---|
Any chain | Any | Any | Any | Any route | |||
| 0x2e62…f5f7Frantic | Base | Ausca Browser SessionBrowser | $88.00 | 100% | coinbase | 6d ago | 0xa69776…7a6497 |
| 0x2e62…f5f7Frantic | Base | Ausca Browser SessionBrowser | $495.00 | 100% | coinbase | 6d ago | 0x272877…95e282 |
| 0x2e62…f5f7Frantic | Base | Ausca Browser SessionBrowser | $110.00 | 100% | coinbase | 6d ago | 0x22a48d…322649 |
| 0x2e62…f5f7Frantic | Base | Ausca Browser SessionBrowser | $110.00 | 100% | coinbase | 6d ago | 0x4af156…6f9287 |
| 0x2e62…f5f7Frantic | Base | Ausca Browser SessionBrowser | $110.00 | 100% | coinbase | 6d ago | 0xd2be3b…6aa54c |
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.