Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xda2a…30cd0x9324…5884Base—$0.0870%0xc8d6…6cec1d ago0xb3d561…29322b
0xaa84…c3d70x9324…5884Base—$0.0870%0xc8d6…6cec1d ago0x73b1a9…a0c0df
0x20c8…dece0x9324…5884Base—$0.0870%0xc8d6…6cec1d ago0xbad4f5…decfbf
0xdf12…6f760x9324…5884Base—$0.0670%0xc8d6…6cec1d ago0x38ee26…684f72
0x646b…ff010x9324…5884Base—$0.0870%0xc8d6…6cec1d ago0x561fea…3c63cb
0x7e23…db880x9324…5884Base—$0.0870%0xc8d6…6cec2d ago0x0ea1cc…1f2b5f

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.