MCP server
Ten tools over the Model Context Protocol. Point Claude, Cursor or any MCP client at one URL and it can quote, execute, check status and build a signable Bitcoin transaction.
An agent cannot sign up
No inbox for a key. No card to put on file. No way to accept terms. Most routing APIs start with a signup form. We do not have one.
17Chains15 EVM + BTC + SOL17Routing venuesRaced in parallel16/17Healthy nowDegraded venue0Fees for usersPermanently
Why this is a real problem
Most routing APIs make an agent behave like a person.
Get a key by email. Accept terms in a browser. Add a card, get invoiced, reconcile it later. Every one of those steps assumes a human with an account.
The usual workaround is a developer provisioning a key and handing it over. Now the agent spends someone else's credentials, with no per-call accounting and no way to revoke one task without killing them all.
What makes this pleasant for a human developer is what makes it usable at all by software. No key. Calls from anywhere. An endpoint that quotes its own price and takes payment for the request you just made.
Three ways in
Same routing engine, same venues, same prices. Pick the one that fits how your agent is built.
x402
The endpoint answers 402 Payment Required and names its own price. The agent pays in USDC and retries. No account, no invoice, no shared credential.
REST API
The same quote, execute and status contract our own app uses. Anonymous calls work. A free self-serve key only raises the rate limit.
Your agent can hold Bitcoin
Normally it cannot. Bitcoin has no balance and no contract to call. Spending means picking unspent outputs and signing each one, which is not the model any EVM wallet in an agent framework was built for.
ravn_btc_prepare_send closes the gap. It builds the Bitcoin payment for the agent, so the agent only has to sign it. That is what puts native BTC in reach of software never designed for Bitcoin.
What an agent gets
No account
Not on MCP, not on x402, not on REST. Nothing to provision, share or revoke.
Per-call cost
With x402 the agent pays for the request it made, at the price in the response. No invoice, no monthly bill to attribute.
Every venue
The same parallel race a human gets, ranked on net output after gas. Agents are not routed to a worse tier.
Native assets
Real Bitcoin and real Solana, settled canonically. A wrapped receipt is a liability an agent cannot reason about.
Machine-readable
A public OpenAPI 3.1 spec, an llms.txt (a plain-text summary written for models), and structured error codes on every failure.
Sandbox
Run the whole flow with no real funds while you are still finding out what the agent decides to do.