Transactions

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

RouteTxn hash
Any chain
Any
Any
Any
Any route
0x905c…0b2c0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase15d ago0x1d29db…87d910
0x80f5…60a50x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase15d ago0x1b760c…8821eb
0x80f5…60a50x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase15d ago0xbea819…7136e5
0x0d4d…555c0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase15d ago0xa152db…bbbc84
0x0d4d…555c0x02c2…3043BaseSocialFetchTikTok$0.01100%coinbase15d ago0xbb9ed4…9f71bd
0x9705…8ee60x02c2…3043BaseSocialFetchTikTok$0.03100%coinbase16d ago0xbca83c…3d1525

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.