Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x7722…5e4a0xd7f1…2d36BaseRegex BuilderAi$0.03100%coinbase2d ago0xdaf4d4…970fb7
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.18100%coinbase3d ago0x72b391…ab513b
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.03100%coinbase3d ago0x81115f…8bf5ce
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.03100%coinbase3d ago0xa993cb…1859c6
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.09100%coinbase3d ago0xd29236…06a0f8
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.09100%coinbase3d ago0x161a18…afc1ad
0x787d…9da10xd7f1…2d36BaseRegex BuilderAi$0.09100%coinbase3d ago0x679ec1…4c4933

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.