bots.st/roundhouse
Roundhouse
Read-only SQL analytics on agent payments and identities
2031 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 17
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://api.roundhouseai.io/v0/mcp
What it can do
| Tool | What it says it does |
|---|---|
get_account | 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… |
get_agent | 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. Wraps GET /v0/agents/{wallet}. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns… |
get_capability | 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… |
get_graph | 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… |
get_leaderboard | 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… |
get_merchant | The same shape as `/agents/{wallet}`, for a wallet in its receiving role. Wraps GET /v0/merchants/{wallet}. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns: - wallet: The wallet queried, lowercased. - role: The role it was queried in: `agent` or `merchant`… |
list_agent_feedback | Raw feedback entries from the ReputationRegistry for a single agent id. Wraps GET /v0/agents/{agentId}/feedback. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns: - agent_id: The id queried. - chain: The chain the feedback was read from. - feedback: Feedback… |
list_agents | 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… |
list_capabilities | 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… |
list_entity_settlements | 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. Wraps GET… |
list_facilitators | 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. Wraps GET /v0/facilitators. Access: requires an API key (Authorization: Bearer rh_live_… or… |
list_flows | The newest settlements across every indexed chain, payer to payee. This is the same feed the `/flows` page renders. Wraps GET /v0/flows. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns: - flows: Settlement rows, newest first, decorated with resolved display… |
list_services | The x402 service catalog, ordered by observed 30-day call volume. A listing is a claim; the observed columns are evidence — prefer `is_live` with non-zero `l30_unique_payers`. Note the path stays `/v0/endpoints` although the human page moved to `/services`; renaming it would break published… |
list_transactions | Every indexed settlement, newest first, filterable by how confidently it is known to be an x402 payment. Wraps GET /v0/transactions. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns: - transactions: Settlement rows, newest first. Each row also carries… |
list_wallets | All settling wallets, filterable by the role they were seen in. Wraps GET /v0/wallets. Access: requires an API key (Authorization: Bearer rh_live_… or x-api-key). Returns: - wallets: Wallet rows with role and last seen. - next_before: Cursor for the next page, or `null`. - meta: The chain served… |
recommend_capability_offers | 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… |
run_sql | 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. Priced by the time… |
In its maker's words
Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL.
- Website
- roundhouseai.io/docs/api/mcp?utm_source=mcp_registry&utm_medium=mcp_directory
- Publisher
- roundhouseai.io
- Listed from
- the official MCP Registry as
io.roundhouseai/roundhouse - Version
- 0.1.0, updated 16 Oct 2026
- Kinds of work
- Finance and markets, Crypto and web3, Data and databases
The domain it lives on
- roundhouseai.io
- registered 8 May 2026 (6 months ago), at GoDaddy.com, LLC, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2031 ms | |
| Answered | 2063 ms | |
| Answered | 971 ms |
Next door
- gblin-treasury-risk-regimeUSDC treasury risk and NAV actions
- Agent402.Tools: pay-per-call web toolsUS equity quotes and live news/search
- Financial Modeling Prep MCP ServerAccess financial data tools from an API
- TokenZeroVerifiable AI spend receipts and waste audits
- savvlyEligibility checks, projections, product comparisons
Is this your bot? Claim its address to add a verified badge and keep the listing current.