Overview
Monday, 24 August

Good morning

Three APIs are live and metering. Sample data until you sign in.

Earned · 30d
$4,182.60
18.4% vs prior 30d
Spent · 30d
$142.18
128,431 calls billed
Wallet balance
$312.44
USDC · 4 agent wallets
Settle rate
99.4%
failed calls cost nothing

Revenue

Meteredon 2xx, instant
→
Netted$4.18 open
→
On chainevery 4h or $100
last batch 06:00 UTC · 0x9f2c…41ab

Revenue by API

last 30 days

Live calls

streaming
Next payout $100 increments
$842.60 of $900 · next release at the ninth increment
corporate wallet · 0x7a3f…c214

Nothing has been metered yet

The moment an agent makes its first call through Routavo, it lands here: what settled, what it earned, and every call in the order it happened.

your session · 0 calls · $0.0000 · open
earnings · usdc

Earnings

What agents paid for your calls, what Routavo took, what you are owed, and where it goes.

Reading the ledger…
Earned · net
$0.00
after Routavo's 1%
Payable now
$0.00
paid out by the operator
Paid out
$0.00
USDC, on chain
Held in disputes
$0.00
released when resolved

Payout address

not set
The operator pays out here and records the transaction. It appears under Payouts once the chain confirms it.

Payouts

none yet
WhenAmountTransaction
Nothing paid out yet.

Settlements

none yet
WhenWhatAPIGrossFeeNetRef
No paid call yet. Free-tier calls are metered here but move no money.
3 live · 1 staged

APIs

Connect what already runs. Reads go live first; anything that writes or deletes stays off until you turn it on.

Connected

3 live · 1 staged
geo.fastmaps
$2,104.20
38ms p50
atlasgrid.dev
$1,318.80
51ms p50
pinpoint.api
$759.60
44ms p50
acme-maps
staged from spec · not live
·
awaiting review

geo.fastmaps endpoints

8 live of 14
EndpointTypePrice / callCalls · 30dLive
Destructive endpoints stay off until you enable them one at a time.
You net
$0.002079after the fee
Autopilot is off for this API. On, it moves the price inside a band you set, one step a day, from your own numbers only.
Live on the next discover(). A quote an agent already holds is honoured for that call.

What Routavo takes

1% of what settles, at most a cent a call
No per-call fee, no monthly fee, nothing on the free tier. A failed call is never charged, so it costs neither side anything.

This is the record an agent reads before it calls you. Capability, schema, price, and terms in one response.

GET /discover?capability=geocode { "provider": "geo.fastmaps", "capability": "geocode", "price": { "amount": "0.0021", "asset": "USDC" }, "latency_p50_ms": 38, "metered": "on 2xx", "settlement": "netted, every 4h or $100", "contract": "geocode@1", "quote": "call({ capability: 'geocode', dry_run: true })" }

Catalog listing

verified
Capability contractgeocode@1
one shape every provider answers in
Terms and licensingdeclared
shown to every agent before it calls
Test callpassed 24 Aug
Routavo called it and got a contract-shaped answer
Signed receiptson
proof the caller can check without asking Routavo
Healthmeasured · no flags
settle rate and open disputes, published beside your price
Where agents find itgenerated from the live registry
discover("address to coordinates") · free text, ranked
/.well-known/mcp.json · one fetch says whether to connect
/.well-known/agent-card.json · A2A agents
/llms.txt · anything that reads pages
/api/catalog?format=openapi · spec tooling
/api/catalog?format=x402 · facilitator indexes
MCP Registry · com.routavo/routavo, one listing carries every provider

Unmet demand

nobody offers it yet
transcribe340 asks
agents asked in the last 30 days and got an empty catalogue
translate212 asks
agents asked in the last 30 days and got an empty catalogue
ocr96 asks
agents asked in the last 30 days and got an empty catalogue

Asked for under another name

1
geocoding asked 120 times · you offer geocode
alias it and you appear for both
2
weather-forecast asked 60 times · you offer forecast
alias it and you appear for both

No APIs connected

Point Routavo at an OpenAPI spec and we map every operation and stage it priced, or drop one line of middleware and keep your own hosting. Nothing goes live until you approve the list.

read endpoints go live first.
anything that writes or deletes stays off until you turn it on.
set it and forget it

Autopilot

Runs your price and your listing inside a band you set, from your own numbers only. One move a day at most, every one logged and reversible.

Nothing to run yet

Autopilot starts working the moment an API is connected. Connect one and it is a single switch from there.

price inside a band you set · names agents ask for · a health check
from your own numbers only, one move a day at most

Your APIs

0 of 3 on
APIPrice nowBandLast moveCheckedAutopilot
Click a row to see what it is doing and why. Checks run once a day; a price moves at most once a day, at most 10%, and never outside the band.

geo.fastmaps

off
Band starts at half to double the current price; change either end any time
What it does when on
Priceone bounded step at a time, from your own refusals and wins; rolled back if revenue falls
Naminganswers to names agents keep asking for that you already serve
Healthcalls your endpoint daily and keeps the verified date fresh; flags two failures in a row

Right now

checks once a day

Moves it has made

every one reversible

How it works

1Observeevery decision, and why each loss happened
2Proposethe smallest change that clears the rule you keep failing
3Applyinside your band, never past either end
4Measurerevenue after against before; undone if it fell
What it learns from
  • your own wins and losses
  • the reason recorded on each loss
  • published list prices, which agents read anyway
  • your own latency and settle rate
What it is never given
  • another provider's volume or revenue
  • another provider's conversion by price
  • who the calling agent is, when it prices
  • any ability to move outside your band
last 30 days

Routing

Every call you were considered for, and what decided it. Click a stage of the funnel to filter the list.

How to get used more

Each figure is a replay of decisions already logged, not a forecast. It answers one question: had this been true at the time, would the rule have picked you.

Where calls went

Left to right: hard rules drop a call before price is compared, so those were never winnable. Price only decides among the eligible.

Win rate over time

your price changes marked
Group by
Outcome

No routing decisions yet

Once an agent asks for a capability you offer, this is where you will see who used you, what got used instead when you lost, and the change that would have won the most calls back.

you will be judged on published price, measured latency,
and recent settle rate. never on your volume.
4 callers · sample

Connections

An agent connects once and reaches every API on the network. One wallet, one cap, one place to see it all.

Disputes

2 open · illustrative
09:14:020x7a3f…c21e · geocode · $0.0021 · "Coordinates were for the wrong Oslo."
Yesterday0x91bb…08d4 · forecast · $0.0034 · "Response was for the wrong day."

A caller holding a signed receipt can dispute the charge. You see the reason, the receipt and the amount, never their request or your response. The provider's share is held until you decide: refund returns the full price to the caller, uphold releases the hold.

Who has called

sample callers
CallerWalletUsesDaily capLast callStatus
0x91c2…7f4a
identified by wallet
 0x91c2…7f4a discover, call $5.00 / day12s ago active 1,204 calls
0x4d8b…20e1
identified by wallet
 0x4d8b…20e1 discover, call $5.00 / day3m ago active 618 calls
editor-agent
client name only
 · discover, call $0.25 / day1h ago active 41 calls
anon
anonymous
 · discover, call $0.25 / day6d ago active 3 calls

What the agent sees

4 tools
discover(capability)Providers that can do the thing, with live price, latency, terms, and the JSON schema for the call.
call(capability | provider, arguments, …)Routes to the cheapest healthy provider, fails over if it fails, meters on the 2xx, and returns a signed receipt. Options: dry_run for a quote, batch up to 50, plan for chained steps, recipe, quorum of two or three, budget, idempotency_key, fields. Every refusal carries a code, whether to retry, and what would fix it.
verify(receipt)Checks a receipt's signature. Anyone holding one can confirm the provider, price, fee and output hash without asking Routavo.
dispute(receipt, reason)Flags a charged call for the provider. Lands in that provider's queue below. Never carries the request or the response.

Four tools, fixed. Quotes, plans and quorum are parameters of call, so the hundredth API adds nothing to an agent's context window.

Server

healthy
{ "mcpServers": { "routavo": { "url": "https://mcp.routavo.com" } } }
Transportstateless HTTP
Spec2026-07-28
Client identityCIMD
Catalog cachettl 60s

Capability contracts

geocode@1
in { query, limit?, language? } out { results: [ { name, lat, lng, country, region, timezone } ] }
forecast@1
in { lat, lng, days? } out { current: { temp_c, wind_kph }, days: [ { date, max_c, min_c, precipitation_mm } ] }

Recipes

weather_for_place~$0.0055
geocode the place, then forecast at the top match · inputs: query, days? · call({ recipe: "weather_for_place", arguments: { query: "Denver" } })

One shape per capability. An agent that learned geocode on one provider does not relearn it on the next, which is what makes providers substitutable and routing mean anything.

No agents connected

Give an agent this one URL and it reaches everything on the network through it. There is no key to issue and no account for it to create: it brings a wallet, and that is the account.

mcp.routavo.com
four tools, fixed. it stays four as the network grows.
org · routavo-demo

Settings

Safe defaults are on. Change one and it lands in the audit log with who changed it.

Safety

enforced by the server
Pause all endpoints every call is refused with a reason agents can act on; discover() keeps answering; nothing is charged
Bench a listing under 50% settled over its last calls; it comes back on its own when calls settle againalways
Spend caps refused on the spot, never queued$5.00 a day per proven wallet · $0.25 anonymous
Set on the server: DAILY_SPEND_CAP_USD and ANON_DAILY_SPEND_CAP_USD. A wallet can lower its own cap, never raise it above yours.
Signed receipts every call comes back with proof the caller can check without asking Routavoon
Request and response bodiesnever logged
Not a setting. Routavo keeps metadata only: who, what, when, price, outcome. A logged body is a privacy problem and an injection surface, so there is no switch for it.
Alerts benched or back, Autopilot moves, disputes, payouts, deposits, signupsthe bellemailwebhook
Email goes to the operator address; a webhook (Slack, Discord, PagerDuty) is ALERT_WEBHOOK on the server.

Enterprise controls

defaults pre-set · designed
Set the way a security review would want them. Single sign-on and directory provisioning wait for your identity provider; everything else is on. Turn off what your policy does not need.

Access and identity

Single sign-on SAML or OIDC
Directory provisioning SCIM
Users and roles come from your directory, and leave when they leave it.
Roles4 defined
ownereverything, including this screen
financeledger, payouts, exports
engineerAPIs, endpoints, pricing, connections
auditorread everything, change nothing
Counterparty allowlist serve only wallets you have verified
Off by default so an open network can find you. On the server today: WALLET_ALLOWLIST and WALLET_DENYLIST.
Sanctions screening of wallets
Every counterparty wallet is checked against OFAC and equivalent lists before a settlement touches it, by a specialist provider.

Change control

Second approver to enable a destructive endpoint
Second approver to raise a cap above
Second approver for price changes outside the Autopilot band
Change freeze window

The person who can be talked into a change by a tool result must not be the only person who can approve its consequence. Autopilot moves stay inside their band and are exempt; anything that widens a band is not.

Treasury security

Payout address allowlist 24 hour hold on any new address
Second signature above
Daily payout limit
Bring your own key management
Signing keys live in your HSM or cloud KMS. Routavo holds no private key either way: payouts are sent from your wallet and recorded against the chain.

Monitoring

p95 latency above
Settle rate below
Spend or volume anomaly an hour more than three standard deviations off its usual, either way
Trace propagation OpenTelemetry: your request id travels to the upstream and back
Public status page

Data

Data residency
Logs, decisions and audit records stay in the region you pick.
Retention

Audit log

immutable · every change on this screen and every other
What is recorded
  • who made the change, and the role they used
  • what changed, before and after
  • when, and from which address
  • which approver signed off, when one was required
What is never recorded
  • request or response bodies
  • agent prompts or tool results
  • another provider's volume
  • anything you did not change