io.roundhouseai/roundhouse
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Roundhouse
Publisher-provided description
Read-only analytics on x402 agent payments and ERC-8004 agent identity, with SQL.
Summary by lookupd
Runs read-only SQL and analytics queries on x402 agent payments, ERC-8004 agent identity, and service catalogs.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http roundhouse https://api.roundhouseai.io/v0/mcp
Codex, remote (streamable-http)
codex mcp add roundhouse --url https://api.roundhouseai.io/v0/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"roundhouse": {
"url": "https://api.roundhouseai.io/v0/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (17 tools)
Publisher-provided text
get_accountWho 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 blist_flowsThe 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 APlist_transactionsEvery indexed settlement, newest first, filterable by how confidently it is known to be an x402 payment. Wraps GET /v0/transactions. Access: requires an API kelist_entity_settlementsSettlements where this wallet is either the payer or the payee, newest first. Walkable deeply in time order: `(payer, block_time desc)` and `(payee, block_timeget_agentOne 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 thiget_merchantThe same shape as `/agents/{wallet}`, for a wallet in its receiving role. Wraps GET /v0/merchants/{wallet}. Access: requires an API key (Authorization: Bearerlist_agentsAgents read from the on-chain IdentityRegistry, with their registration card and payment wallet. `score` is the ERC-8004 reputation score derived from on-chainlist_walletsAll 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-keget_leaderboardAgents 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 droplist_agent_feedbackRaw feedback entries from the ReputationRegistry for a single agent id. Wraps GET /v0/agents/{agentId}/feedback. Access: requires an API key (Authorization: Belist_facilitatorsThe facilitators seen relaying settlements, with their known relayer wallets. Paged: this used to return up to 200 rows unpaged, most of their columns null. Nulget_graphEntities 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 runninglist_servicesThe 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_capabilitiesEvery 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 endget_capabilityEvery 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'srecommend_capability_offersA 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 irun_sqlOne `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
Details
- Version: 0.1.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 244 ms
- First indexed:
- Last seen in registry:
- Website: https://roundhouseai.io/docs/api/mcp?utm_source=mcp_registry&utm_medium=mcp_directory
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.roundhouseai/roundhouse)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp