Agents Index

Roundhouse

OnlineOfficial

Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL.

Visit publisherConnectJSON

What it can do: 17 tools

  • get_account read-onlyWho 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
  • list_flows read-onlyThe 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). Retur
  • list_transactions read-onlyEvery 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:
  • list_entity_settlements read-onlySettlements 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 wall
  • get_agent read-onlyOne 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
  • get_merchant read-onlyThe 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 quer
  • list_agents read-onlyAgents 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 rat
  • list_wallets read-onlyAll 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
  • get_leaderboard read-onlyAgents 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 com
  • list_agent_feedback read-onlyRaw 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 q
  • list_facilitators read-onlyThe 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/f
  • get_graph read-onlyEntities 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 **whol
  • list_services read-onlyThe 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 h
  • list_capabilities read-onlyEvery 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 mark
  • get_capability read-onlyEvery 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.
  • recommend_capability_offers read-onlyA 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
  • run_sql read-onlyOne `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-

Connect it

Claude Code
claude mcp add --transport http roundhouse https://api.roundhouseai.io/v0/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.roundhouseai.io/v0/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "roundhouse": {
      "url": "https://api.roundhouseai.io/v0/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "roundhouse": {
      "type": "http",
      "url": "https://api.roundhouseai.io/v0/mcp"
    }
  }
}

Questions

What does Roundhouse do?

Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL. It exposes 17 tools to AI assistants.

What tools does Roundhouse provide?

17 tools, including get_account, list_flows, list_transactions, list_entity_settlements, get_agent, get_merchant, list_agents, list_wallets, get_leaderboard, list_agent_feedback, list_facilitators, get_graph….

How do I connect Roundhouse to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.roundhouseai.io/v0/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Roundhouse require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Roundhouse online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Roundhouse?

roundhouseai.io. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Agents & Orchestration