Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x2e36…f6320xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0xed5453…dce5a5
0xccab…80ae0xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0xefcd7d…908cff
0xccab…80ae0xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0xa3fa0c…f18dd3
0x5a56…3dee0xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0x9d154c…cd7211
0x0e0f…fe150xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0x2c8488…79b8ea
0x7578…68370xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0x2aaef7…369987
0x0e0f…fe150xd850…f111Basex402 service$0.001100%Payer-submitted81d ago0xec8712…34f24d

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.