AI Agents on RAVN: MCP Server, x402 Payments, and the Swap API
Your agent can swap across 17 chains on RAVN, native Bitcoin included. Pick a free MCP server, pay-per-call x402 or the plain REST API: same fields, same 0% fee.
Quick answer
Your agent can swap across 17 chains on RAVN, native Bitcoin included. The MCP server is free with no signup. x402 lets it pay per call in USDC. The REST API is free and needs no key. All three run the same logic, so fields, routes and the 0% swap fee never change.
Three ways in
| Method | Signup | Access cost | Best for |
|---|---|---|---|
| MCP Server | None | Free | Agents already running in Claude, Cursor or another MCP client |
| x402 Payments | None | 0.001 USDC a quote, 0.01 USDC an execute | Autonomous agents that pay as they go |
| REST API | None. A free key only raises the rate limit | Free | Existing bots and backends |
The swap fee is 0% on every route, native BTC included. We never hold your funds. Your agent always signs or sends from its own wallet.
MCP server, free
Our MCP server lives at https://app.ravn.exchange/api/mcp and speaks Streamable HTTP. It gives your agent ten tools:
- 1
ravn_quote: the best price across 17 chains, same-chain or cross-chain. Returns a quoteToken. - 2
ravn_execute: turns a quoteToken into something to sign or send: TRANSACTION, SIGNATURE or DEPOSIT. - 3
ravn_submit_signature: sends a signed SIGNATURE order so it gets placed. - 4
ravn_status: checks where a swap is, by quoteToken and reference. - 5
ravn_health: shows which venues are up right now. - 6
ravn_tokens: lists our curated tokens for a chain. - 7
ravn_tokens_resolve: looks up any token address, listed or not. - 8
ravn_btc_coverage: which tokens on a chain you can reach from native BTC. - 9
ravn_chains: every chain we list tokens for. - 10
ravn_btc_prepare_send: turns a DEPOSIT result into an unsigned Bitcoin PSBT, ready to sign.
The tools call the same free /v1/* endpoints as the REST API. No signup, no key.
{"mcpServers": {"ravn": {"url": "https://app.ravn.exchange/api/mcp"}}}
Paste that into claude_desktop_config.json or a Cursor .cursor/mcp.json and the tools show up. A plain GET from curl or a browser returns 405 Method Not Allowed. That is expected, since Streamable HTTP only answers POST.
x402, pay per call
With x402 your agent pays per call in USDC, on Base or Solana. Only quote and execute cost money. status and health have no /x402/ version and stay free.
- 0.001 USDC
POST /api/v1/x402/quote, same contract as the free quote endpoint - 0.01 USDC
POST /api/v1/x402/execute, same contract as the free execute endpoint
Your agent calls with no payment and gets a 402. The options sit in a payment-required header, and the body is just {}. It signs a USDC payment (EIP-3009 on Base, a USDC transfer on Solana) and retries. We settle it and return the normal response. Bodies match the free endpoints, and a quoteToken works with either execute call.
Why pay when free paths exist? Spend is fixed per call. Each payment is an on-chain record anyone can check. And agents that browse x402 catalogs, like Coinbase's x402 Bazaar and x402scan.com, can find RAVN there on their own.
REST API, no key needed
Inside a bot, backend or wallet? Call POST /quote, POST /execute and GET /status directly. Every endpoint works with no key at 30 requests a minute per IP. A free key only raises that limit. The cross-chain swap API guide and for integrators have the full endpoint map.
Receiving real Bitcoin
Your agent gets real BTC, not a wrapped copy. When a Bitcoin route comes back as a DEPOSIT, ravn_btc_prepare_send turns it into an unsigned PSBT. Your agent signs and broadcasts it, with no coin-selection code of its own. More on native BTC swaps without wrapping.
Who signs the transaction?
TRANSACTION and SIGNATURE results need a signature, and we never make one. You decide once how your agent signs. Keep a local key. Send the payload to a human or wallet app first. Or use a TEE or custody service (a CDP-managed wallet, Turnkey, Privy) that never shows the key to the agent. DEPOSIT results skip this, since they are a plain transfer. The docs have the full signing patterns.
Which one should I use?
- Already in Claude or Cursor: use the MCP server. Just add the URL.
- Fully autonomous, no stored secrets: use x402. Pay per call, nothing to rotate or leak.
- An existing bot or backend: call the REST API directly. No key needed.
Switching later changes how you connect, not what you built.
Build an agent on RAVN
Point an MCP client at the server, or read the full agent docs.
FAQ
How does an AI agent swap crypto on RAVN?
Three ways: the free MCP server, x402 paid per call in USDC, or the REST API with no key needed. All three share the same fields and the same 0% swap fee.
What is the RAVN MCP server?
A remote MCP server at app.ravn.exchange/api/mcp with ten tools, from ravn_quote and ravn_execute to ravn_btc_prepare_send. It is free and needs no signup.
How much do x402 payments cost?
0.001 USDC per quote and 0.01 USDC per execute, paid on Base or Solana. That is separate from the swap fee, which stays 0%.
Can agents swap native Bitcoin, not wrapped BTC?
Yes. ravn_btc_prepare_send turns a Bitcoin deposit into an unsigned PSBT your agent can sign. You get real BTC, not a wrapped copy.
Which access method should I use?
The MCP server inside Claude or Cursor. x402 for autonomous agents that should hold no secrets. The REST API for an existing bot or backend: it needs no key, and a free one only raises the rate limit.
