Transactions

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

All listed chains.

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%payAI9d ago0x29b6cb…46b29c
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%payAI9d ago0xd05c1a…0b5d6c
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%payAI9d ago0xc5dc90…3dcf7b
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%coinbase9d ago0x07b092…69028a
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%coinbase9d ago0x912ff7…deb93d
0xc8f9…38f20x79a7…f94cBaseBasex402 service$0.01100%coinbase9d ago0xe00d6e…dd96b9

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.