routheus
Registry code: 32fffbd9326fb531
Free discovery tools for the Routheus multichain DEX router API. There is a FREE tier: single-input swap quotes and quote+calldata are free (rate-limited per IP, no payment or API key) — just call the endpoint with no X-PAYMENT header. Use routheus_catalog to see what's free and the prices for paid products (simulated quotes, arbitrage quoting, batches, token data), routheus_price_offer to price a specific call, then call the returned HTTP URL — free-tier for basic quotes, or with an x402 client to pay for full data. For higher limits or a custom plan, the catalog includes a contact email.
- endpoint
- https://routheus.xyz/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is routheus live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is routheus free to use?
- Not measured yet.
- What tools does routheus have?
- 3 tools: routheus_catalog, routheus_chains, routheus_price_offer.
- Is routheus safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- list dex router products and prices
- list supported chains
- price a swap quote call
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
routheus_catalog reads unknown never probed
Get the live Routheus product catalog: DEX endpoints, the FREE tier (single-input swap quotes and quote+calldata are free, rate-limited per IP — no payment or key), per-call USDC prices for paid products, supported EVM chains, x402 payment details, and a contact email for custom/higher-limit plans. Call this first to learn what's available, what's free, and what costs.
{ "type": "object", "properties": {} }arguments 4 linesroutheus_chains reads unknown never probed
List the DEX chains Routheus can quote on, with accepted path aliases (canonical slug, chain name, or EIP-155 id — e.g. eth = ethereum = 1).
{ "type": "object", "properties": {} }arguments 4 linesroutheus_price_offer reads unknown never probed
Get the price for a specific product, WITHOUT paying. For quote and quote_calldata it reports that a rate-limited FREE tier exists (call the returned URL with no X-PAYMENT header to use it); for all products it returns the exact x402 USDC offer and the ready-to-call HTTP URL. To get paid data, call that URL with an x402 client (x402-fetch / @x402/fetch / AgentKit).
{ "type": "object", "required": [ "chain", "product" ], "properties": { "chain": { "type": "string", "description": "Chain slug/name/id, e.g. base, ethereum, 1" }, "product": { "enum": [ "quote", "quote_calldata", "quote_sim", "quote_arb", "token_metadata", "token_search" ], "type": "string", "description": "Which product to price" } } }arguments 25 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id32fffbd9326fb531.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/32fffbd9326fb531/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/32fffbd9326fb531?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.