Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x226e…25880xf62f…a973Basex402 service$0.01100%payAI22m ago0x79577e…33dd56
0x226e…25880xf62f…a973Basex402 service$0.01100%payAI35m ago0xa713ea…af3c04
0x226e…25880xf62f…a973Basex402 service$0.01100%payAI49m ago0x5a2e4e…1d2900
0x226e…25880xf62f…a973Basex402 service$0.01100%payAI1h ago0x0a885c…c0c071
0xb3cd…f2470xf62f…a973Basex402 service$0.01100%payAI1h ago0x3b53ad…aeb81c
0x0a7c…69e20xf62f…a973Basex402 service$0.01100%payAI11h ago0xc3cff7…606bfc
0x9137…3f5a0xf62f…a973Basex402 service$0.01100%payAI22h ago0x68f38d…76a8b3

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.