Skip to main content
The router quotes swaps over the Solana venues that GET /venues marks buildable and servable (more than 15) and builds the transaction that executes them through the on-chain swap program. Under /evm it does the same on Ethereum, BNB Chain, Base and Robinhood Chain over Uniswap and PancakeSwap: see EVM swaps. It never signs and never sends: you get a quote, then instructions or unsigned transactions, and your backend signs and broadcasts them.

Quote and swap

The two calls of every swap

Transactions

v1 transactions, compute budget, priority fee, tips

Platform fee

Charge your own fee on a swap

EVM swaps

Ethereum, BNB Chain, Base and Robinhood Chain: approvals and swap, simulated

Public router

https://router.raze.bot is Raze’s router. It takes your Raze API key. Its Solana routes have no path prefix (/quote, /swap-instructions, …); the EVM routes are under /evm (/evm/quote, /evm/swap, …) and speak the same API. On Solana it builds for Raze’s deploy of the swap program, DADMMjfNnY6z8H9h9RfHZ9tfarBySsj4Yb65qLyKJDAD: that is the programId of every swap instruction it returns. Launch, the unsigned token-deploy builder, is part of it too, under /launch.

One router, one program deploy

A router can also run for a client’s own deploy of the swap program: its address, its upgrade authority, the admin of its config. Every router builds for the program address it is configured with (ROUTER_SWAP_PROGRAM_ID), so the programId of every swap instruction you receive is that deploy. It reads that deploy’s on-chain config at boot and keeps it current:
  • a venue the config has no live row for is never quoted;
  • while the config is paused, every build answers 503;
  • per-venue limits the deploy’s admin sets (for example a slippage cap) apply on chain, inside the slippage you ask for.

Authentication

https://router.raze.bot takes the same key as the market-data API, sent the same ways: x-api-key, Authorization: Bearer or ?apiKey= (see Authentication). Only /health, /ready, /evm/health and /evm/ready are open. The router shares your account’s rate a second with the API, and every request it lets in spends credits (see Rate limits and credits). A missing or unknown key answers 401, a request over the limit 429, with the API’s body: { "error": { "code": "unauthorized", "message": "…" } }. A router run for a client’s own deploy has no keys, no accounts and no rate limit, and listens on loopback by default: keep it behind your own gateway, which is the place for keys and limits.

Routes

Conventions

These are the Solana routes’. The EVM routes follow them too, with 0x addresses, uint256 amounts, a required chain, exact-in only and transactions instead of instructions: see What differs from the Solana routes.
  • Amounts are integers in the token’s base units (lamports for SOL, the mint’s smallest unit otherwise). In quotes and builds the large amounts are decimal strings (inAmount, outAmount, otherAmountThreshold, platformFee.amount, every lamport field of costs); minReturn, maxAmountIn, computeUnits, contextSlot and lastValidBlockHeight are JSON numbers.
  • Mints and wallets are base58 addresses. Wrapped SOL is So11111111111111111111111111111111111111112.
  • Venue labels (label, dexes, excludeDexes) are the dex names of GET /venues, matched ignoring case and punctuation.
  • Unknown parameters and body fields are ignored, not refused. A known path with the wrong method is 405 with an empty body.
  • Every transaction is v1 (SIMD-0385): see Transactions.

Close to Jupiter, not the same

Quote parameters and response fields follow Jupiter’s quote API (inputMint, outputMint, amount, swapMode, slippageBps, routePlan, otherAmountThreshold, …), and the build answers with the same instruction buckets. A Jupiter client ports with a few changes: