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
662gvd…oNu128heAM…semGSolanaSolanax402 service$0.005100%payAI28d ago3NtP2psr…gBsgWo
662gvd…oNu19246Xr…6oisSolanaSolanax402 service$0.01100%payAI28d agow9GZKJaP…ji6KWP
662gvd…oNu1Solana token lookup (Jupiter)SolanaSolanaStock historical barsData$0.03100%coinbase28d ago3uLaSZcb…fG1vkc
662gvd…oNu19246Xr…6oisSolanaSolanax402 service$0.03100%payAI28d ago5fr7gZDx…ioxgvp
662gvd…oNu19246Xr…6oisSolanaSolanax402 service$0.06100%payAI28d ago2bt7WEGB…Y31Pz2
662gvd…oNu19246Xr…6oisSolanaSolanax402 service$0.06100%payAI28d ago2gSKCYBY…jou7dE

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.