Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$0.03100%coinbase2d ago0x31d7c8…74bf4e
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$3.99100%coinbase2d ago0x0be643…a2c1ea
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$0.24100%coinbase2d ago0x17e368…612d74
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$0.03100%coinbase2d ago0x0ecc1b…a9e57e
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$0.01100%coinbase2d ago0xda7ca0…28f8b0
0xc683…0e680xa30f…dae9Basefalcon.sol compsSec$0.005100%coinbase2d ago0x0f03c3…55f384

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.