Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0xc0c3…78a80x09ae…ec64Base—$100.9870%0x07ae…0e673d ago0xc7d3cb…66d2e0
0xc0c3…78a80x09ae…ec64Base—$101.2970%0x07ae…0e673d ago0x63c547…374de0
0xc0c3…78a80x09ae…ec64Base—$101.6070%0x07ae…0e673d ago0xbde786…e5bf19
0xc0c3…78a80x09ae…ec64Base—$60.7070%0x3943…d1bd3d ago0x69dded…da8137
0xc0c3…78a80x09ae…ec64Base—$61.3870%0x07ae…0e673d ago0x454b15…0c34cc
0xc0c3…78a80x09ae…ec64Base—$278.0870%0x07ae…0e674d ago0xb83e09…40d6cc

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.