DEX aggregator API New

Swap API for token swaps on 10 chains, with no fee from the swap.

One request format for EVM, TRON, Solana, TON and XRP Ledger. Your wallet signs; you pay per API call, not per trade. For wallets, payment providers, exchanges and fintech teams.

Get an API key Read the docs See an example request

Non-custodial: MetaMask, TronLink, Phantom, Tonkeeper, Xaman or your backend signs. We never hold keys or funds.

Already on the RPC Gateway? Your project key and credits work here.

Quote Build SignEthereum
POST/v1/quote
1,000 USDCETH

Expected output

0.263157 ETH

Guaranteed minimum
0.261842 ETH
Network cost
$8.21
Price impact
4 bps
Slippage
50 bps
Pool fees already deductedRisk: low · 12
Example quote · Illustrative values

10 mainnets · 7 testnets · one request format

  • Ethereum
  • BNB Chain
  • Polygon
  • Arbitrum
  • OP Mainnet
  • Avalanche
  • TRON
  • Solana
  • TON
  • XRP Ledger

Swap API at a glance

10 + 7

Mainnets + testnets

From rehearsal to mainnet.

1

Request format

For EVM, TRON, Solana, TON and XRP Ledger.

$0.0011

Per quote + build

One priced and built swap, paid from your API credits.

1 key

Shared with RPC Gateway

Same project. Same credit balance.

Reasons

Why the Crypto Chief
Swap API

No fee taken from your swap. TRON, TON and XRP Ledger alongside EVM and Solana. And nothing to build or run yourself: pool indexes and liquidity integrations for ten networks, a routing and simulation engine, gas and energy models, router verification and five transaction formats are behind two HTTP calls.

Keep the swap.
Pay for the call.

The Swap API adds no fee of its own to the swap, so the API bill does not grow with trade size.

Quote + build$0.0001 + $0.001

No subscription, no separate plan: the RPC Gateway credits pay for it. Quotes cost less than builds, so build only the route your user confirms.

Example: 1,000,000 quotes and 100,000 builds a month cost $200 in credits. 1inch Startup covers 1 million calls for $149 to $199 a month and takes 7 to 20 bps of every swap on top: $7,000 to $20,000 on $10 million of monthly volume. 1inch x402 pay-per-call is $0.00024 a call with no swap fee. As of 25 October 2026.

What the provider takes from a $10,000 swap

Providers that take a fee from the swap · Jupiter (Solana only) and KyberSwap state no swap fee, see the table

1inch $2–$30 Subscription plans
0x $15 Selected pairs + surplus
LI.FI $25 Service fee
OpenOcean $1–$50 By pair type
Crypto Chief No fee from the swap $0

Fees taken from the swap itself, from public pricing pages as of 25 October 2026 (OpenOcean: 26 October 2026). Fees vary by plan and pair; 0x also takes Trade Surplus, and 1inch takes none in x402 pay-per-call mode. Network and pool fees apply on every route and are not included.

TRON, TON and XRP Ledger included

One key and request format cover EVM, Solana, TRON, TON and XRP Ledger. The 1inch Classic Swap API covers none of TRON, TON or XRP Ledger and has no testnets (as of 25 October 2026).

TRONTONXRP Ledger

Routes ranked by what you keep

Routes are ranked by net output: what lands in your wallet after network costs and an execution-risk penalty, not by the headline rate. Every build is simulated first; a failed simulation returns an error, never a transaction.

Each step’s cost in output tokens

Your integration. Your fee.

Take an on-chain partner fee: up to 100 bps on EVM networks, TRON and TON, up to 300 bps on Solana and XRP Ledger.

fee_bpsfee_recipient
Three steps

How the Swap API works

From a token pair to a settled swap in three steps. Only your wallet can authorize the transaction.

  1. 1 POST /v1/quote

    Ask for a quote

    Send the network, the two tokens and the amount. You get the expected output, the guaranteed minimum, every fee, the route and a risk score. Nothing is signed and nothing moves.

  2. 2 POST /v1/build

    Build the transaction

    Add the wallet address that will swap. Pools are re-read on a fresh block and the swap is simulated: a failed simulation returns an error, not a transaction. An approval or, on XRP Ledger, a trust line comes back as its own step before the swap.

  3. 3 your wallet

    Sign and send

    Your wallet or backend signs each step and sends it in the order returned, waiting for each to confirm. If a step is marked rebuild_after_previous, call build again first.

Example

Swap API example: a priced swap in one request

Plain HTTPS and JSON. The project key goes in the URL path, so there is no Authorization header to manage.

Base URL https://swap-api.crypto-chief.com/YOUR_API_KEY/v1/
  • The key you already have. The same project key and credits as the RPC Gateway.
  • Plain inputs. Tokens by symbol, such as USDC, and NATIVE for the network's own coin. Amounts in base units, or as decimals with amount_in_human.
  • Named errors. 402 INSUFFICIENT_CREDITS, 422 NO_ROUTE, 422 SIMULATION_FAILED: the error says what went wrong.
  • The format your wallet expects. Build returns each network's native transaction format; the network notes list them.
Get an API key Read the docs
POST /v1/quote curl
# price 1,000 USDC → ETH on Ethereum
curl -X POST "https://swap-api.crypto-chief.com/YOUR_API_KEY/v1/quote" \
  -H "Content-Type: application/json" \
  -d '{
    "network": "ETH_MAINNET",
    "token_in": "USDC",
    "token_out": "NATIVE",
    "amount_in": "1000000000",
    "slippage_bps": 50
  }'
200 Example response, abridged, illustrative values
{
  "quote_id": "0b6f8c7e-6a43-4d0a-9d7e-3c2f5a1e9b10",
  "amount_out": "263157894736842105",
  "amount_out_human": "0.263157894736842105",
  "amount_out_min": "261842105263157894",
  "net_amount_out": "260971578947368421",
  "price_impact_bps": 4,
  "fees": {
    "network": { "native_symbol": "ETH", "cost_usd": "8.21", … },
    "pools": [ … ],
    "service": { "bps": 0, "amount": "0" }
  },
  "route": { "splits": [ … ] },
  "risk": { "level": "low", "score": 12, "factors": [ … ] },
  "setup_required": true,
  "expires_at": "2026-10-25T12:00:30Z"
}
→ POST /v1/build with from_address returns the unsigned transaction → your wallet signs and sends it; the API never does
Swap quoteEthereum
1,000 USDCETH

Expected output

0.263157 ETH

Guaranteed minimum
0.261842 ETH
Network cost
$8.21
Price impact
4 bps
Swap API fee
0

Route

Split across 2 pools

Expires 12:00:30 UTCRisk: low · 12
Example quote · Illustrative values
The quote

Everything you need to decide before anyone signs

One quote answers what you get, what it costs and what can go wrong, before a transaction exists.

  • Expected output and a guaranteed minimum: below it, the swap does not execute
  • Network cost in the native coin, the output token and USD, plus each pool's fee
  • The route: up to 7 parallel branches and up to 4 pools in each
  • An execution-risk level, a score from 0 to 100 and the factors behind it
  • An expiry time, so you know when the price must be asked for again
0x7a3…91c2Your wallet

Confirm 2 steps

  1. 1Approve USDCExact amount: 1,000 USDC
  2. 2Swap1,000 USDC → min 0.261842 ETHSign

Signed in your wallet. Keys never leave it.

Custody

Your wallet signs. We never hold keys or funds.

The Swap API returns unsigned transactions and stops there: it does not sign, does not send and does not take custody. The swap settles on-chain between your address and the pools.

  • The swap itself is one transaction
  • An approval or a trust line, when needed, comes back as its own step first
  • Approvals default to the exact amount of the swap, never unlimited unless you ask
Safety

Swap safety: what is checked before you sign

The checks the API runs before you sign, and the risks it measures but does not remove.

Blocks the build

Simulated at build time

Pools are re-read on a fresh block and the swap is simulated. A failed simulation returns 422 SIMULATION_FAILED and no steps to sign; if it cannot run or finish, simulation.status says why.

Enforced on-chain

A floor on every fill

You set the slippage: 50 bps (0.5%) by default, up to 5000. The quote turns it into amount_out_min, and below that minimum the transaction does not execute.

Re-checked

Pinned routers, exact approvals

Router addresses and their runtime code are pinned and re-checked; a mismatch takes that router out of use. Approvals default to the exact amount.

In the risk score

Risky tokens flagged

Token traits such as transfer fees, rebasing, pausing or blacklists are flagged and counted in the execution-risk score of every quote.

Measured, not prevented

MEV: measured, not promised

Through the public mempool, the risk block can carry an mev_exposure factor with the estimated cost of a sandwich attack, counted against the route. Private submission is not offered.

Time-limited

Quotes that expire on purpose

Every quote carries expires_at. A quote is not a guarantee of execution: once you send, the network decides.

Coverage

One DEX aggregator API for EVM, Solana, TRON, TON and XRP Ledger

10 mainnets and 7 testnets under one request format and one key. Liquidity sources differ by network.

EthereumEVM · ETH Uniswap V2/V3SushiSwap V2/V3PancakeSwap V2/V3 BNB Smart ChainEVM · BNB Uniswap V2/V3SushiSwap V2/V3PancakeSwap V2/V3 PolygonEVM · POL Uniswap V2/V3SushiSwap V2/V3QuickSwap V2 Arbitrum OneEVM · ETH Uniswap V2/V3SushiSwap V2/V3PancakeSwap V2/V3 OP MainnetEVM · ETH Uniswap V2/V3SushiSwap V2/V3 Avalanche C-ChainEVM · AVAX Uniswap V2/V3SushiSwap V2/V3Trader Joe V1Pangolin V2 TRONTRX SunSwap V2/V3 SolanaSOL Jupiter Swap API TONTON STON.fi v2DeDust XRP LedgerXRP Order booksAMM pools
7 testnets The same request format, so the whole flow can be rehearsed before mainnet.
  • Ethereum SepoliaUniswap V2 and V3, SushiSwap V2
  • BSC TestnetPancakeSwap V2 and V3
  • Arbitrum SepoliaUniswap V3
  • Optimism SepoliaUniswap V3
  • Avalanche FujiTrader Joe V1
  • TRON NileSunSwap V2
  • XRP TestnetBuilt-in DEX: order books and AMM pools
By network

Swap API by network: what changes from one chain to the next

The request stays the same. Where the liquidity comes from, what your wallet signs and the partner fee depend on the network.

EVM swap API

Six EVM mainnets in one request format. Whether you integrate it as an Ethereum, BSC, Polygon or Arbitrum swap API, only the network and the token addresses change.

Liquidity
Our own index of Uniswap, SushiSwap, PancakeSwap, QuickSwap, Trader Joe and Pangolin pools, re-read on a fresh block at build time
You sign
An eth_sendTransaction object
Approvals
A separate step for the exact amount, when the token needs one; with a partner fee the approval goes to the Crypto Chief router
Partner fee
Up to 100 bps, taken from the output inside the swap by the Crypto Chief router

Solana swap API

Liquidity
Routes built through the Jupiter Swap API
You sign
A base64 transaction with the route's address lookup tables
Valid for
About 60 to 90 seconds: sign and send promptly
Partner fee
Up to 300 bps; your fee account is checked on-chain before the route is built

TRON swap API

Liquidity
SunSwap V2 and V3
You sign
A triggersmartcontract body with fee_limit set; the quote shows the network cost in TRX up front
Partner fee
Up to 100 bps, taken from the output inside the swap by the Crypto Chief router; a TRX output is paid in TRX

Moving USDT on TRON too? TRON Energy rents energy for TRC-20 transfers so they stop burning TRX.

TON swap API

Liquidity
Quotes from STON.fi v2 and DeDust
You sign
A TON Connect request you pass to tonConnectUI.sendTransaction as is
Partner fee
Up to 100 bps, accrued in your STON.fi referral vault; a route that carries a fee uses STON.fi only

XRPL DEX API

Liquidity
The XRP swap API routes through the ledger's built-in DEX: order books and AMM pools
You sign
tx_json; a missing trust line comes back as a separate step before the swap
Valid for
About two minutes (35 ledgers)
Partner fee
Up to 300 bps, as a second Payment inside an XLS-56 Batch
Use cases

Built for wallets, PSPs, exchanges and fintech teams

The same two calls, quote and build, behind four kinds of product.

A crypto swap API for wallets

The swap button is two calls: a quote to show the rate, the fees and the guaranteed minimum, then a build for a transaction in the format that wallet signs. The partner fee lets the feature earn its keep.

For payment providers and PSPs

Convert the token a customer pays with into the one you settle in, from a treasury wallet whose keys you hold or from a Crypto Processing wallet: the Processing API signs and sends each step on EVM networks, TRON, TON and Solana.

Signing from a processing wallet: guide. Invoicing: Crypto Processing API. A PSP under your brand: Whitelabel Processing.

For exchanges

Offer an in-product convert feature without maintaining pool integrations for every network. One credit balance pays for this and your RPC Gateway traffic.

Screen counterparties with AML Intelligence where your compliance process requires it.

For fintech teams without a Web3 team

Token symbols instead of contract addresses, decimal amounts, one key for every network and transactions in the format a wallet signs. You still need a wallet or backend signer that holds the keys and sends each step.

Get an API key See pricing
Alternatives

Swap API alternatives: 1inch, 0x, LI.FI and other DEX aggregator APIs

Teams comparing swap APIs ask three things: what a call costs, what is taken from each swap and which networks are covered.

ProviderFee taken from the swapHow you payNetworksAPI key and access
Crypto Chief Swap APILiveNone taken from the swap; network and pool fees are shown in every quoteQuote $0.0001, build $0.001 per call, from the credit balance shared with the RPC Gateway; no separate Swap API plan6 EVM networks plus TRON, Solana, TON and XRP Ledger, and 7 testnetsThe project key (project UUID) in the URL path; the same key as the RPC Gateway
1inch (Classic Swap API)Figures as of 24-25 October 20262 to 30 bps infrastructure fee taken from the swap output on the Dev to Business plans, by plan and pair; listed prices exclude it. None in x402 modeFree Dev plan: 100,000 calls a month at 60 requests a minute. Startup $149 or $199, Professional $299 or $399, Business $599 or $799 a month, billed annually or monthly, for 1, 3 or 7 million calls. x402 pay-per-call: $0.00024 per Swap API call in USDC18 networks, including Base, zkSync, Gnosis and Linea; Solana is served through Intents and Cross-chain, not the Classic Swap API. TRON, TON, XRP Ledger and testnets are not in its support matrixAPI key from the 1inch Business portal; new accounts pass KYC
0x Swap APIFigures as of 25 October 20260.15% on selected pairs, plus Trade Surplus collectionStandard $1,000 and Enterprise $2,500; the billing period is not stated on the pricing page. 5 requests a second on Standard16 EVM networks on the Swap API product page; 0x docs describe liquidity across EVM, Solana, Tron and HyperCore, with Solana as a separate product and Tron in the Cross-Chain APIAPI key required
LI.FIFigures as of 25 October 20260.25% service fee per transaction; integrators can add their own feeStandard plan free to integrate, up to 200 requests a minute; Enterprise by agreement60+ chains, including EVM networks, Solana, Tron, Sui and Bitcoin; mainly a bridge and DEX aggregation APIAPI key from the LI.FI Partner Portal
Jupiter Swap APIFigures as of 25-26 October 2026No Jupiter swap fee on the Swap API build endpoint; integrators can set a platform feeFree tier at 1 request a second; Developer $25, Launch $100 and Pro $500 a month, for 10, 50 and 150 requests a secondSolana onlyAPI key from the Jupiter developer platform
KyberSwap Aggregator APIFigures as of 26 October 2026KyberSwap states a 0% swap fee; integrator fees are configurablePublic access at 3 requests a second; higher limits through an API key from the KyberSwap team18+ EVM chains and 420+ DEXs for the Aggregator in its docs; Solana appears under Cross-chain Swaps, not the AggregatorNo key for public access; an X-Api-Key header unlocks higher limits
OpenOcean Swap APIFigures as of 26 October 2026Tiered trading fee on the public API: 0.01% stable, 0.1% correlated, 0.25% common and 0.5% exotic pairs; a referrerFee parameter for integratorsPublic access at 2 requests a second; a 2-week trial under 10 requests a second and Pro terms through its team40+ networks, mostly EVM, plus SolanaThe public API examples in its guide send no API key; Pro access through its team or developer portal
Velora Market API (formerly ParaSwap)Figures as of 26 October 2026Requests without a partner run as anon with a flat 1 bps fee; Market partner fees split 85% to the partner and 15% to VeloraFree partner ID at 1 request a second and 5,000 requests a day; Basic $500, Pro $700 and Enterprise $2,000 a monthEVM networks only, including Ethereum, BNB Chain, Polygon, Arbitrum One, Base and AvalancheFree access identifies the integration with a partner string in the request, without signup; the free partner ID does not unlock partner fees

Figures from each provider's public pages, checked on the date in its row. Network and pool fees are extra with every provider.

Looking for a 1inch API alternative?

1inch sells monthly plans sized by call volume, takes an infrastructure fee from the swap output on those plans and asks new Business accounts to pass KYC (as of 25 October 2026). Here each call is paid from the project's credit balance, nothing is taken from the swap, and the key is the project UUID the RPC Gateway already uses.

0x API pricing and fees on swaps

0x API pricing combines a plan price with a 0.15% fee on selected pairs and Trade Surplus collection, so part of the cost grows with the size of each trade (as of 25 October 2026). A Crypto Chief call costs the same whatever the trade size: a quote $0.0001 and a build $0.001.

Jupiter, LI.FI, KyberSwap, OpenOcean and Velora

The Jupiter Swap API covers Solana only, and Crypto Chief Solana routes are built through it. LI.FI is mainly a bridge and DEX aggregation API; this Swap API keeps both tokens on one network and does not bridge. KyberSwap, OpenOcean and Velora offer public or partner access, mostly on EVM networks. Odos shut down its trading and API services in July 2026, so teams that used its API are choosing among the providers above.

See Swap API pricing Read the docs
Partner fees

Partner fees on EVM, TRON, Solana, TON and XRP Ledger swaps

Pass fee_bps and fee_recipient on a quote or build call and your fee is taken on-chain inside the swap transaction. Some providers call this an integrator fee.

  • Set fee_bps to 0, or leave it out, for no fee
  • Separate from the per-call price and from the network and pool costs shown in the quote
  • fee_recipient must be a wallet address, not a token or contract of the trade
Read the docs
EVM networks Taken from the output inside the swap transaction by the Crypto Chief router and sent to fee_recipient; amount_out_min applies to what the user receives after the fee Router contract, the same address on every EVM network, with no owner, no upgrades and no pause: 0x7BE3a58eBe99a7946fe107378DE8775958C32FF9
100 bpsup to 1%
TRON Taken from the output inside the swap transaction by the Crypto Chief router, as on EVM; with a TRX output both parts are paid in TRX
100 bpsup to 1%
Solana Through the Jupiter Swap API; your fee account is checked on-chain before the route is built
300 bpsup to 3%
TON Accrues in your STON.fi v2 referral vault and is withdrawn from there; routes with a fee use STON.fi only
100 bpsup to 1%
XRP Ledger A second Payment inside the same XLS-56 Batch transaction; the signing wallet must support Batch
300 bpsup to 3%
Per call

Swap API pricing: pay per call with API credits

Calls are paid from the same project credit balance as the RPC Gateway, at 10,000,000 credits per US dollar. There is no separate Swap API plan, and the Swap API adds no fee of its own to the swap.

Quote

$0.0001per call
POST /v1/quote
Credits per call
1,000
Per 1,000 calls
$0.10

Build

$0.001per call
POST /v1/build
Credits per call
10,000
Per 1,000 calls
$1.00

Approvals

$0.000026per call
POST /v1/approve/spender, /v1/approve/allowance, /v1/approve/transaction
Credits per call
260
Per 1,000 calls
$0.026

Reference data

$0.000026per call
POST /v1/networks, /v1/tokens and /v1/liquidity-sources
Credits per call
260
Per 1,000 calls
$0.026

When credits are charged

Credits are debited when a call is accepted, before the route is computed. A quote costs less than a build, so you can price many routes and build only the one your user confirms.

Credits come back

When a call fails for an availability reason your request could not cause: no response from the swap service, a 502 or 504, a 503 caused by network state on our side, or a 429 for too many calls in flight.

Charged

Errors the swap service returns for your request: every 4xx other than 429, including 422 NO_ROUTE, 422 INSUFFICIENT_LIQUIDITY and 422 SIMULATION_FAILED, as well as 500 errors and calls you cancel yourself.

Calls turned away for missing credits or rate limits before the debit cost nothing.

Already on the RPC Gateway?

Your project key and credits already work here. Credit plans and top-ups are on the pricing page.

Get an API key All pricing
Questions

Swap API FAQ

Networks, keys, billing, safety and how the Swap API compares with other DEX aggregator APIs.

Talk to the team

A swap API, or token swap API, turns a token exchange into an API call. You send a network, two tokens and an amount; it returns a priced route across decentralized exchanges and, when you are ready, an unsigned transaction that executes that route. Your own wallet signs and sends it. The Crypto Chief Swap API does this on 10 mainnets and 7 testnets and never takes your keys or holds your funds.

A DEX aggregator is a router for decentralized exchanges. Instead of trading in one pool, it prices the same swap across many pools and can split the order between them or hop through an intermediate token when that leaves you with more. Here, best means the best net result among the liquidity sources we support and verify at the current network state, after network costs and an execution-risk penalty, not a promise covering every exchange in existence. When you compare the best DEX aggregators, look at the networks and liquidity sources covered, the net output after costs, what each call costs and who holds the keys.

On a centralized exchange you deposit funds, trade inside the exchange and withdraw. A swap through a DEX happens on the blockchain itself: the tokens leave and arrive at your own address on-chain, and nobody holds them in between. The Swap API finds the route and builds that transaction; it does not take deposits and does not move assets between networks.

Ten mainnets: Ethereum, BNB Smart Chain, Polygon, Arbitrum One, OP Mainnet, Avalanche C-Chain, TRON, Solana, TON and XRP Ledger. Seven testnets: Ethereum Sepolia, BSC Testnet, Arbitrum Sepolia, Optimism Sepolia, Avalanche Fuji, TRON Nile and XRP Testnet. The networks method returns the current list with each network's readiness, and the liquidity-sources method lists the sources enabled on each one.

Register, create a project and use its UUID: that UUID is the key, and it goes in the request URL. It is the same project key the RPC Gateway uses, and both products draw on one credit balance, so if you already use the RPC Gateway your key works here and there is nothing new to request.

There is no free Swap API tier. The free allowances on the pricing page cover the RPC Gateway, Unified API and EventStream. Every Swap API call is paid from project credits, and a quote costs less than a build, so you can price many routes and build only the one your user confirms.

No. The Swap API takes nothing from the swap itself, but every route still pays the network fee and each pool's own fee, and the quote shows both. Each quote and build call is paid from your API credits. A partner fee, if you set one, is paid to you, not to Crypto Chief.

Per call, from the project's API credit balance, with no separate Swap API plan. Credits are debited when the call is accepted, before the route is computed. They come back when a call fails for an availability reason the request itself could not cause; validation and business errors, including no route found and a failed simulation, are charged. The Swap API adds no fee of its own to the swap.

Swap API calls count against the same project limits as RPC Gateway calls: one Swap API call takes one slot. A project with too many calls in flight at once receives 429 RATE_LIMITED with a Retry-After hint, and those calls are refunded. If you plan sustained volume, talk to the team about your project's limits.

No. The Swap API never signs or broadcasts transactions and never holds keys or funds. The build call returns unsigned transactions for your own wallet: MetaMask, TronLink, Phantom, Tonkeeper, Xaman or your own backend signer. A wallet of your Crypto Processing project can sign and send the steps through the Processing API on EVM networks, TRON, TON and Solana. The swap settles on-chain between your address and the liquidity pools, and Crypto Chief cannot move your tokens.

Most failures surface before you sign. Every build re-reads the pools on a fresh block and simulates the swap: a failed simulation returns 422 SIMULATION_FAILED and no transaction, and if the simulation could not run, simulation.status says not_run or incomplete with the reason. On most networks a wallet without enough balance gets 422 BALANCE_INSUFFICIENT first. A quote is not a guarantee: once a transaction is signed and sent, execution depends on the network, and a transaction that fails on-chain can still cost its network fee.

Price impact is how much your own trade moves the pool price; every quote shows it as price_impact_bps. Slippage is how far the output may fall before you refuse the trade: you set slippage_bps, 50 (0.5%) by default and up to 5000, and the quote turns it into amount_out_min. If the swap cannot deliver at least that minimum, the transaction does not execute.

No. When a swap goes through the public mempool, the risk block can carry an mev_exposure factor with the estimated cost of a sandwich attack, and that cost counts against the route when routes are ranked. Private transaction submission is not offered. If the estimate worries you, lower the slippage or the trade size before you sign.

Yes: up to 100 bps on EVM networks and TRON, up to 300 bps on Solana, up to 100 bps on TON and up to 300 bps on XRP Ledger. Pass fee_bps and fee_recipient on the quote or build call and the fee is taken on-chain inside the swap. On EVM networks and TRON the Crypto Chief router takes the fee from the swap output and sends it to fee_recipient; the user receives the output minus the fee, and amount_out_min applies to that amount. The router has the same address on every EVM network, 0x7BE3a58eBe99a7946fe107378DE8775958C32FF9, and has no owner, no upgrades and no pause. A fee_bps above 100 on an EVM network or TRON returns 400 INVALID_REQUEST. On TON the fee accrues in your STON.fi referral vault.

It does the same job: priced swap routes and ready-to-sign transactions through an API. The main differences, as of 25 October 2026: the Crypto Chief Swap API covers 6 EVM networks plus TRON, Solana, TON and XRP Ledger and 7 testnets, while the 1inch Classic Swap API lists 18 networks without TRON, TON, XRP Ledger or testnets; the key is your project UUID, the same one the RPC Gateway uses, while 1inch issues keys through its Business portal; and no fee is taken from the swap. Endpoints and field names differ, so an integration maps its fields rather than reusing them.

Each provider prices differently. As of 24-25 October 2026, 1inch sells subscriptions from a free Dev plan of 100,000 calls a month up to $799 a month, takes an infrastructure fee of 2 to 30 bps from the swap output on those plans, and offers x402 pay-per-call at $0.00024 per Swap API call; 0x lists a Standard plan at $1,000 and an Enterprise plan at $2,500 without stating the billing period, plus a 0.15% fee on selected pairs. There is no separate Swap API plan: each call is paid in credits from the same balance as the RPC Gateway, a quote costs less than a build, and no fee is taken from the swap. The comparison table on this page lists the figures with their dates.

Here the flow is: quote first, an approval or trust line when the token needs one, then the build call that returns the unsigned swap. Field names and endpoints differ between providers, so an integration maps its fields to ours rather than reusing them; the quote request and the example response on this page show the request format and the main response fields. The 7 testnets let you rehearse the whole flow before mainnet.

No. Each swap runs within one network, with both tokens on that network, and nothing is bridged. What makes it a multichain swap API is one key, one request format and one credit balance across EVM networks, TRON, Solana, TON and XRP Ledger, so your integration barely changes from one network to the next.

Yes. The Swap API documentation is at docs-swap.crypto-chief.com. This page also shows a complete quote request, an example response and the transaction format the build step returns on each network. The API is plain HTTPS and JSON, so any HTTP client, such as Python requests, Node fetch or Go net/http, calls it the same way as the curl example.

Price a swap in one call. Build it in the next.

Register, create a project and send your first quote. The same key and credit balance work for the RPC Gateway.

Get an API key Read the docs Launch announcement
Products
RPCs
More Networks
Company

© 2026 Crypto Chief. All Rights Reserved