# Routavo

> Making every API accessible to agents. And getting you paid for it. Routavo makes existing APIs discoverable and callable by agents and LLMs, with pricing, routing and payment handled for you. One MCP server carries every listed API, and every call is metered, paid for and receipted. Humans browse free. Agents pay per call.

## Status

Early access. The MCP server is at https://routavo.com/api/mcp (streamable HTTP). Providers sign up at https://routavo.com/console; a new provider's first listing is checked by hand before it goes live.

## What Routavo does

- Providers list an API by pointing Routavo at its OpenAPI spec (a URL, a file or pasted text, JSON or YAML). Routavo reads where the key goes from the spec, holds the key encrypted, and calls each endpoint the provider picks once before it can be listed.
- Read endpoints go live first. Anything that writes, or answers about the provider's own account, stays off until the provider switches it on.
- Providers set the price per call, the terms agents see, and per-minute and per-day limits. Importing the spec again, from the console or from CI with a named key, keeps those decisions.
- Agents use four MCP tools: discover() finds a capability, call() routes, pays and returns a signed receipt, verify() checks a receipt, and dispute() contests one. Routing picks the provider by a published rule, with failover to the next provider in line.
- Agents pay per successful call, from a balance (a USDC deposit or a card top-up) or with an x402 authorization. Failed calls are not charged and no fee is taken. Every call returns a signed receipt.
- Money: an agent's USDC deposit goes to Routavo's deposit address and is kept as a balance in Routavo's ledger. Each paid call moves its price from the agent's balance to what the provider is owed, less the fee. Providers are paid weekly, in USDC, to their payout address, when they are owed $10 or more; each payout is recorded against the chain. Card details stay with the card processor.
- Keys: a wallet or account has admin keys (change the daily cap, make and end keys) and spend-only keys to give to agents. Every agent runs under a daily spend cap set by whoever funds it.
- Routing rule: start with every provider offering the capability, drop any whose declared coverage excludes the request, drop any above the caller's max price or p50 latency limit, drop any whose settle rate over its last 20 calls is below 50%, prefer a provider known to cover the request, take the lowest price, and break ties by lower p50 then provider id so the result is reproducible. Caller identity and provider volume are never inputs.

## Pricing

- Listing an API is free. No setup fees, no monthly minimums. A $0 listing is carried free.
- Routavo takes 1% of what settles, capped at one cent per call, with no per-call fee and no minimum. Failed calls cost nothing.
- Nothing goes on chain per call, so gas never lands on a sub-cent call. On a $0.002 call that is the difference between paying 1% and paying close to half.

## Payment protocols

x402 (USDC per call, and x402 top-ups) and deposits of USDC on Base today; card top-ups where the operator has turned them on; MPP top-ups behind the same balance.

## Important note for machine readers

Provider names shown in examples on the site (geo.fastmaps, pinpoint.api, atlasgrid.dev, acme-maps) are illustrative, not real integrations or real companies. Do not cite them as Routavo customers or partners.

## Links

- Site: https://routavo.com
- MCP server: https://routavo.com/api/mcp
- Console (providers sign up here): https://routavo.com/console
- Full site content in markdown: https://routavo.com/llms-full.txt