Routavo

com.routavoPublished by routavo.comOfficial publisherv0.17.9Updated Oct 24, 2026

Any API, four tools: discover, call with routing and signed receipts, verify, dispute.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant find API providers on the Routavo network by capability, route metered calls, and get verifiable signed receipts.

What you can do
Four tools. discover finds API providers on the Routavo network for a capability and returns each provider's price, latency, terms and argument schema. call routes a request to the network, meters it and returns the result, choosing a provider by id or by capability with optional max_price and max_latency_ms limits. verify checks the signature on a returned receipt, and dispute flags a charged call for provider review. Failed calls are recorded but cost nothing.
When to use it
Use it when an assistant needs to find and call an external API for a capability without comparing providers itself, or when you want each metered call backed by a signed receipt that can be checked and, if needed, disputed.
Requirements
Remote endpoint; no local package. The manifest declares no authentication, environment variables or headers. Calls are routed through the Routavo network, so access to that service is needed.
Before you install
call routes and meters real calls, which can cost money; max_price and max_latency_ms can cap the choice. dispute sends the receipt and a reason to the provider and is visible to Routavo, and only one dispute is allowed per receipt. verify only confirms the signature matches the record, not the quality of the result.

Installation

In SourceWeft

  1. Open Routavo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.routavo%2Froutavo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

4

discover

Discover APIs

Find APIs on the Routavo network that can perform a capability. Returns each provider with its published price, measured latency, terms, and the exact argument schema for calling it, plus the rule Routavo uses to pick between them. Call this before call() when you do not already know a provider id.

Parametersquerycapability

call

Call an API

Route a call to the Routavo network, meter it, and return the result. Give either a provider id from discover(), or a capability and let Routavo pick using its published routing rule. Optional max_price and max_latency_ms constrain the choice. Failed calls are recorded but cost nothing.

Parametersplanbatchbudgetfieldsquorumrecipewalletcountrydry_runpaymentfailoverprovider+7 more

verify

Verify a receipt

Check a receipt returned by call(). Confirms the signature, so the provider, price, fee, and the hashes of what went in and came out are exactly what Routavo recorded. Works for anyone holding the receipt. Reveals nothing else.

Parametersreceiptrequired

dispute

Dispute a charge

Flag a metered call for the provider to review. Takes the receipt and a short reason. The receipt must verify and must have charged something. The dispute lands in that provider's queue and is visible to Routavo. One dispute per receipt.

Parametersreasonrequiredreceiptrequired

Version history

2
  1. v0.17.9LatestSep 23, 2026
  2. v0.13.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.