{"id":"io.roundhouseai/roundhouse","slug":"io-roundhouseai-roundhouse","title":"Roundhouse","description":"Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL.","version":"0.1.0","publisher":{"kind":"domain","id":"roundhouseai.io","label":"roundhouseai.io","url":"https://roundhouseai.io"},"website":"https://roundhouseai.io/docs/api/mcp?utm_source=mcp_registry&utm_medium=mcp_directory","repository":"","remotes":[{"type":"streamable-http","url":"https://api.roundhouseai.io/v0/mcp","headers":[{"description":"Optional Roundhouse API key (rh_live_…) from https://roundhouseai.io/dashboard/connections. Omit it to sign in with OAuth instead.","isSecret":true,"name":"x-api-key"}]}],"packages":[],"published":"2026-10-16","updated":"2026-10-16","status":"online","auth":"","latency_ms":965,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"get_account","title":"What this caller is entitled to, and what it would be charged","description":"Who the credential in front of this request resolves to, which of the two paid lanes it would take, what it has left to spend, and the price of every route on both lanes. Unmetered and answerable WITHOUT a key: checking your balance must never cost a unit and must never be the thing that fails. A caller with no key gets a real answer (`tier: anonymous`, `lane: x402`, the full price list), not a 40","read_only":true},{"name":"list_flows","title":"Live flow of funds","description":"The newest settlements across every indexed chain, payer to payee. This is the same feed the `/flows` page renders.\n\nWraps GET /v0/flows.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- flows: Settlement rows, newest first, decorated with resolved display names. Each row also carries `is_self_payment` (payer = payee, annotated rather than only excluded — a t","read_only":true},{"name":"list_transactions","title":"Global settlement feed","description":"Every indexed settlement, newest first, filterable by how confidently it is known to be an x402 payment.\n\nWraps GET /v0/transactions.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- transactions: Settlement rows, newest first. Each row also carries `is_self_payment` (payer = payee, annotated rather than only excluded — a third of the feed can be self-payment","read_only":true},{"name":"list_entity_settlements","title":"Settlements for one wallet","description":"Settlements where this wallet is either the payer or the payee, newest first. Walkable deeply in time order: `(payer, block_time desc)` and `(payee, block_time desc)` cover it, so page N costs what page 1 does and a wallet's whole history can be paged for velocity or trend.\n\nWraps GET /v0/entities/{wallet}/settlements.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nRe","read_only":true},{"name":"get_agent","title":"Per-agent stats and identity","description":"One wallet in its paying role: its resolved identity and its own settlement aggregates. Every figure is that wallet's own — there are no site-wide totals on this endpoint.\n\nWraps GET /v0/agents/{wallet}.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- wallet: The wallet queried, lowercased.\n- role: The role it was queried in: `agent` or `merchant`.\n- coverag","read_only":true},{"name":"get_merchant","title":"Per-merchant stats and identity","description":"The same shape as `/agents/{wallet}`, for a wallet in its receiving role.\n\nWraps GET /v0/merchants/{wallet}.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- wallet: The wallet queried, lowercased.\n- role: The role it was queried in: `agent` or `merchant`.\n- coverage: **Read this first.** `known` false means the index has never observed this address, so every","read_only":true},{"name":"list_agents","title":"Indexed ERC-8004 agents","description":"Agents read from the on-chain IdentityRegistry, with their registration card and payment wallet. `score` is the ERC-8004 reputation score derived from on-chain feedback — it is the REGISTRY's number, not a Roundhouse rating, and it is null for every agent no counterparty has left feedback for. Roundhouse publishes no trust score of its own.\n\nWraps GET /v0/agents.\nAccess: requires an API key (Autho","read_only":true},{"name":"list_wallets","title":"Every address the index has seen","description":"All settling wallets, filterable by the role they were seen in.\n\nWraps GET /v0/wallets.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- wallets: Wallet rows with role and last seen.\n- next_before: Cursor for the next page, or `null`.\n- meta: The chain served and `as_of`. On an EMPTY list it also carries `dataset_last_written_at`, `dataset_row_count` and any ","read_only":true},{"name":"get_leaderboard","title":"ERC-8004 agents by registry feedback score","description":"Agents ordered by the ERC-8004 reputation score, which is the on-chain registry's number and not a Roundhouse rating. Unscored agents sort last rather than dropping out, so a board where nothing has been scored still comes back looking ordered — check `meta.page_scored_agents`, which is how many rows on the page carry a score at all. Zero means the order is the `agent_id` tie-break and nothing mor","read_only":true},{"name":"list_agent_feedback","title":"ERC-8004 feedback for one agent","description":"Raw feedback entries from the ReputationRegistry for a single agent id.\n\nWraps GET /v0/agents/{agentId}/feedback.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- agent_id: The id queried.\n- chain: The chain the feedback was read from.\n- feedback: Feedback entries.\n- meta: The chain served and `as_of`. On an EMPTY list it also carries `dataset_last_written_at","read_only":true},{"name":"list_facilitators","title":"Relayers, per chain","description":"The facilitators seen relaying settlements, with their known relayer wallets. Paged: this used to return up to 200 rows unpaged, most of their columns null. Null-valued columns are omitted from each row.\n\nWraps GET /v0/facilitators.\nAccess: requires an API key (Authorization: Bearer rh_live_… or x-api-key).\n\nReturns:\n- chain: The chain served — this deployment's default when none was named.\n- faci","read_only":true},{"name":"get_graph","title":"Payment graph: nodes and payer→payee edges","description":"Entities as nodes and settlements aggregated into edges, over a bounded window. Two window forms, and exactly one may be sent: `window=N` is a row count running to the live tip (briefly cacheable); `days=N` covers **whole UTC days only**, excluding today, so an answer is stable for the day. Use `days` for anything an agent will cache. Self-payments are excluded from BOTH edges and node totals and ","read_only":true},{"name":"list_services","title":"Indexed x402 service directory","description":"The x402 service catalog. Without `q` it is ordered by the catalog's own reported 30-day call count (reported by the source, not indexed by Roundhouse); with `q` it is a relevance search grouped by service, so a mirror host or a listing repeated by several directories is one result. Each row carries the verified volume of the SERVICE it belongs to (settlements a known facilitator relayed, summed o","read_only":true},{"name":"list_capabilities","title":"The capability catalogue","description":"Every job the catalog is grouped by, with the canonical request and response each provider of that job is mapped onto — which is what lets an agent swap one endpoint for another without changing its code. Static: no market figures here, because each one costs its own catalog walk. Ask `/unified/{slug}` for a capability's offers and going rate. Send `fields=compact` when you are only choosing a cap","read_only":true},{"name":"get_capability","title":"One capability: who offers it, and what it costs","description":"Every indexed endpoint that does this job, with the market's going rate. `price.spot` is the call-WEIGHTED price, not the median — a median counts one wallet's forty near-identical listings as forty votes for its price. Check `price.spot_basis`: `median` means no offer reported any calls and the figure is a fallback, which does not mean the same thing as a market rate. `truncated: true` means the ","read_only":true},{"name":"recommend_capability_offers","title":"Shortlist endpoints for a capability","description":"A ranked shortlist of endpoints that do this job, under criteria you choose and the response echoes back. Every term is something the endpoint publishes about itself — its listed price against the going rate, and its own reported demand. Roundhouse does not endorse any provider, and there is no cross-capability ranking. Only confident matches are ever recommended.\n\nWraps GET /v0/unified/{slug}/rec","read_only":true},{"name":"run_sql","title":"Read-only SQL over the public dataset","description":"One `SELECT` (or `WITH`) over the public data-layer tables. Enforced in the database, not the worker: a read-only transaction as a role that can see only those tables, a statement timeout set by the TIER, and a hard 300-row cap. No semicolons, no comments, no multi-statement.\n\nPriced by the time it takes: one Query Unit per started 5 seconds, floor of 1 — so a query that answers quickly costs 1, w","read_only":true}],"server_info":{"name":"roundhouse","title":"Roundhouse x402 settlement index","version":"0"},"category":"agents","tags":["crypto","data","analytics"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":318546,"score":100,"indexable":true,"first_seen":"2026-10-16","stars":0,"badges":["official"],"sponsor":null,"page":"https://agentsindex.org/agents/io-roundhouseai-roundhouse/"}