Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x7fd9…b529Kronos Crypto Data & ForecastsBaseKronos Crypto Data & ForecastsLiquidations$0.02100%coinbase24d ago0x28bf60…58e923
0x7fd9…b529Kronos Crypto Data & ForecastsBaseKronos Crypto Data & ForecastsLiquidations$0.02100%coinbase24d ago0xfebe47…3b2d11
0x7fd9…b5290x9dba…0df8Basex402 service$0.00670%0x1360…66fa24d ago0xb1f3d3…e4ee7d
0x7fd9…b5290x4466…125eBasex402 service$0.01100%coinbase24d ago0x09574a…101a50
0x7fd9…b5290x3831…3442BaseHyperliquid Market DataHyperliquid$0.01100%coinbase24d ago0x7160cf…b25539
0x7fd9…b5290xbeeb…831bBasex402 serviceFunding-rate$0.01100%coinbase24d ago0xc60064…3e6d48

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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.