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
0xd1b1…28870xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.01100%coinbase30d ago0x793763…d02155
0xddf4…021e0xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.002100%coinbase31d ago0x4b552f…82ce05
0xa1d1…19780xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.002100%coinbase31d ago0x84c2e1…f8a13f
0xa1d1…19780xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.001100%coinbase31d ago0x828de7…639e9c
0xec2a…d0340xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.002100%coinbase31d ago0x18296b…787898
0x3983…edbe0xffa9…686fBaseBaseMinifetch Technical SEO APISeo$0.002100%coinbase31d ago0xd675f1…86c579

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.