Give your agent tools it can pay for.

Routavo's MCP server is live. Paste one URL where your agent takes a connector, and it can find a tool by what it does, call it, pay per call with no signup, and get a signed receipt back.

https://routavo.com/api/mcp

No account, no key, no card. The free tier meters every call and charges nothing.

What your agent can call today

Routavo's own tools, built on public data sources. As API companies join, their tools arrive here too, described so agents can choose them and priced per call.

Every one is listed with its price, source and licence in the catalogue at /api/catalog.

In an app

These take a URL and nothing else. Everything on this list was checked in September 2026; if a menu has moved, the setting is usually called Connectors, Integrations or MCP. Two URLs exist: routavo.com/mcp is the free tier and never asks for anything; routavo.com/mcp/paid asks the app to sign you in once, so calls come out of your Routavo balance and the app never sees your key or your card.

Grok and Grok Bot

xAI

  1. Go to grok.com/connectors, choose New Connector → Custom
  2. Paste https://routavo.com/mcp for the free tier, or https://routavo.com/mcp/paid to pay from a balance
  3. With /mcp/paid, Grok opens Routavo's sign-in: paste your key and approve, and Grok gets a token for your balance, never the key
  4. Team admins add it once in the cloud console for everyone
  5. In the API, a key from /topup goes in authorization (see In code)

Muse

Meta

  1. Tell it: Build a custom integration to Routavo. Its MCP server URL is https://routavo.com/mcp and it takes a bearer token.
  2. It writes the client itself with the official MCP SDK, over streamable HTTP, and tests every tool
  3. For the free tier, tell it there is no credential
  4. To pay, give it a key from /topup through its credential prompt, never in the chat

Instinct

Spear Street, private access

  1. It runs on a cloud computer with a browser and your stored credentials, and has no connector menu
  2. Message it: Use the Routavo API for weather, geocoding, earthquakes and elevation. Read https://routavo.com/api/wellknown?file=llms.txt first.
  3. To pay, have it open /topup and keep the key it gets

Perplexity

Perplexity AI

  1. Open Settings → Connectors
  2. Choose + Custom connector
  3. Paste the URL, leave authentication set to None
  4. Org admins can turn it on for everyone in one step

Gemini

Google, consumer app

  1. Go to gemini.google.com/apps
  2. Scroll to the bottom and add a custom app link
  3. Paste the URL

Gemini Enterprise

Google Cloud

  1. Agents → Connectors → Custom MCP server
  2. Paste the URL. Transport is streamable HTTP
  3. Leave authentication empty for the free tier

Claude

Anthropic

  1. Settings → Connectors → Add custom connector
  2. Paste the URL and save; use /mcp/paid instead to sign in and pay
  3. Available on the web and desktop apps

Anything else with MCP

Cursor, VS Code, Zed, Windsurf, Cline

  1. Open the editor's MCP settings file
  2. Add the block from In code below
  3. Reload the window
What is verified and what is not. Grok, Perplexity, Gemini and Claude have a connector setting, checked against their own documentation in September 2026. Grok's custom connectors need a paid Grok plan. Routavo is tested with the official MCP client over streamable HTTP, including the sign-in a connector dialog runs, which is the client Muse writes for itself. Muse's directory opened to developers on 18 September at muse.ai/platform, with every connector reviewed by Meta before it is listed; until Routavo is listed there, the custom integration above is the way in. Instinct is still in private access with no developer surface, so its path is the one that works for anything with a browser. This page changes when they do.

In code

Every framework below takes an arbitrary MCP URL. Nothing here needs an account; a key from /topup is the one optional line, and it is the same line everywhere.

{
  "mcpServers": {
    "routavo": {
      "type": "http",
      "url": "https://routavo.com/api/mcp"
    }
  }
}

In mcp.json, .cursor/mcp.json or your client's equivalent. To pay from a balance, add "headers": {"Authorization": "Bearer rw_..."} beside "url", with your Routavo key.

Paying for calls

Calls cost fractions of a cent, so per-call payment settles on chain. A card charge costs 2.9% plus 30c to take, and a call here costs a fifth of a cent, so cards and everything like them top up a balance instead, and calls meter off the balance.

How you payWhat it costsGood for
Nothing
free tier
No charge at all. Every call is metered and receipted. Trying it, and everything up to the daily free-tier cap.
USDC on Base
deposit
Gas only. Nothing added on top. The cheapest way to fund an agent. Prove a wallet, deposit, call.
x402
per call
The price of the call. One signed authorization pays for one call. Agents that hold a wallet and want no balance at all.
An x402 wallet
routavo.com/topup/x402
Face value. One USDC transfer on Base per top-up. Coinbase for Agents, Circle agent wallets, anything on the x402 SDKs: pay the link, get a key for the paying wallet. $1 by default; ?usd=5 asks for more, up to what the wallet allows.
Sign in from the app
routavo.com/mcp/paid
Nothing extra. The app asks you to sign in once; you pay with a card if you have no balance. Grok, Claude and any connector dialog that runs OAuth. The app gets a token for your balance, never a key or a card.
Card or Link, on a page
routavo.com/topup
Face value plus a stated fee, shown before you pay. Anyone with a card and no wallet: pay once, get a key, paste it into the agent. An agent with a browser can do it for you.
Card, Link, Klarna, Affirm
MPP top-up
The same fee, no page: a 402 challenge the agent pays in one round trip. Agents holding a Stripe payment token. Opens an account and returns its key if there is none.
Stablecoin through Stripe
MPP top-up
Face value. Cheaper than the card rail and priced that way. Agents on Tempo or Solana.
Whichever way the money arrives, it lands on the same kind of balance and the same kind of key: Authorization: Bearer rw_... on every request. An agent that runs out mid-task does not fail silently. The refusal names the balance, the price, and every rail that can add funds, so the agent can top up and carry on without a human. Ask for a quote first with dry_run: true and nothing moves.

What an agent can read before it connects

All of this is public, needs no key, and is meant to be fetched by machines.

DocumentWhat is in it
/.well-known/mcp/server-cards.jsonIdentity, endpoint, transports and protocol versions, before any connection is made.
/.well-known/mcp.jsonThe whole server: tools, capabilities, prices, trust tiers, fees, routing rule.
/api/catalogEvery listing as JSON. Add ?format=openapi for a spec with prices and payment offers annotated on it, or ?format=x402 for facilitator catalogues.
/.well-known/agent-card.jsonThe A2A agent card.
/api/wellknown?file=llms.txtThe same thing in prose, live, for a model reading it directly: every capability, price, contract and way to pay.
/llms.txtWhat Routavo is, for companies and for agents, in a page of prose.
/.well-known/oauth-protected-resourceWhere an app signs a person in to pay (OAuth 2.1, PKCE, Client ID Metadata Documents, dynamic registration).
What Routavo keeps. Every call is metered and gets a signed receipt you can check at /api/receipt. Request and response bodies are never logged.