Transactions
Every settlement, with the service it paid for and an x402-confidence score.
| Route | Txn hash | ||||||
|---|---|---|---|---|---|---|---|
Any chain | Any | Any | Any | Any route | |||
| 0xf08f…84010x6302…ad57 | Base | TripadvisorTravel | $0.01 | 100% | payAI | 104d ago | 0x4be88a…af7d82 |
| 0xf08f…84010x6302…ad57 | Base | TripadvisorTravel | $0.01 | 100% | payAI | 104d ago | 0x5c3fb6…9edc07 |
| 0xf08f…84010x6302…ad57 | Base | TripadvisorTravel | $0.01 | 100% | payAI | 104d ago | 0x041d43…a937ad |
| 0xf08f…84010x3c5f…3eea | Base | x402 service | $0.01 | 100% | candidates | 105d ago | 0x45dd53…a1fe30 |
| 0xf08f…84010x6d6e…9192 | Base | ExaSearch | $0.007 | 100% | coinbase | 105d ago | 0x5ccba1…77e9ed |
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
Show the promptHide 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.