Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xcf98…fe7e0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase17d ago0x0a3326…4be8fd
0xcf98…fe7e0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase17d ago0x6c65d0…dde51b
0xcf98…fe7e0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase17d ago0xfa924f…6cc8b5
0x0d4d…555c0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase17d ago0x35f291…4abd1b
0x0d4d…555c0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase17d ago0x29edf6…9389f8
0xdb00…1fac0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase18d ago0x85c3a7…bd326f

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.