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
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa18d ago0x808462…5117ca
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa18d ago0xde7ddb…df5925
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa18d ago0xb850f5…1ec0c4
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa18d ago0x48afc7…a8a068
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa18d ago0xa86dd8…5f071d
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa19d ago0xb2d72a…0da781
0x2d16…87100xfe80…47eeBaseBase—$0.001100%fluxa19d ago0x561ba3…031660

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.