Roundhouse

Name: Roundhouse
Author: io.roundhouseai

MCP serverMCP

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

by io.roundhouseaihomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"roundhouse","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability (some checks stopped at authentication)34/34 checks ok

Some successful checks reached the service and some stopped at an authentication response; figures combine both.

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	19 ms	server roundhouse 0 · protocol 2025-06-18 · 17 tools
8 h ago	mcp initialize	ok	200	207 ms	server roundhouse 0 · protocol 2025-06-18 · 17 tools
15 h ago	mcp initialize	ok	401	1174 ms	auth required
22 h ago	mcp initialize	ok	401	23 ms	auth required
29 h ago	mcp initialize	ok	401	66 ms	auth required
2 d ago	mcp initialize	ok	401	49 ms	auth required
2 d ago	mcp initialize	ok	401	19 ms	auth required
2 d ago	mcp initialize	ok	401	24 ms	auth required
2 d ago	mcp initialize	ok	401	57 ms	auth required
3 d ago	mcp initialize	ok	401	48 ms	auth required

Tools observed via MCP handshake

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 b
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 AP
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 ke
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
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 thi
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
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
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-ke
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 drop
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: Be
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. Nul
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
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_
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 end
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
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 i
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

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.roundhouseai/roundhouse

first seen 9 d ago · fetched 3 d agoopen ↗

Field history (6 recent events)

9 d ago · declared · summary → "Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL."
9 d ago · declared · description → "Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL."
9 d ago · declared · publisherName → "io.roundhouseai"
9 d ago · declared · homepageUrl → "https://roundhouseai.io/docs/api/mcp?utm_source=mcp_registry&utm_medium=mcp_directory"
9 d ago · declared · version → "0.1.0"
9 d ago · declared · protocols → ["mcp"]

Roundhouse

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from