Keep swaps inside your wallet
- Your users stop leaving for an exchange when they want another coin.
- One integration gives them the best offer across the connected sources.
- If a source can't take the order, the next best one can take over.
Let your users swap wallet to wallet, your app never takes custody, and you earn on every completed order. Get the lowest rate each time. Exclude any provider you (don't) like.
Free to use · Self-serve key, no sales call · Rate limits published
+ the other sources, asked at the same time
Every source has its own sign-up, authentication, asset names, status codes and payout. Kotova X does that work for you, for centralized and decentralized sources alike. You integrate once.
And every new chain or asset means a change in each of them.
Every one of these products has users who hold one coin and need another. Here is what the API does for each.
Exchanges, neobanks, games, AI agents — if your users need another coin, the API fits. Tell us what you are building.
api [at] kotova.ioComparing, routing, failover and order problems are the hard parts of offering swaps. They are built in.
Ranked by what your user receives — or, for a reverse quote, by what they send. What Kotova earns never weighs in.
A source that fails or is busy is skipped. If the best one can't take the order, the next best one named in the quote can take over. A source can go away without a change on your side.
One list of currencies and networks with stable codes, whichever kind of source executes the swap. New sources and assets appear without new code.
Your user sends to a deposit address the source issued and receives at their own address. The funds never pass through Kotova either.
A short deposit, a late one, a missing refund address: where the source offers a choice, the order lists what your user can do — continue or refund — and you offer it in your own screens.
Every currency, token and network comes with an icon URL on cdn.kotova.io, mirrored on assets.kotova.io.
Send your key as a bearer token. The answer names the winning source, the next best ones that would take over, and the notices your user has to see.
llms-full.txtIdempotency-Key on orders: a retry never creates a second oneX-Request-Id on every response; the weight and remaining budget in the headers of every keyed callcurl https://api.kotova.io/x/v1/quote \ -H "Authorization: Bearer $KOTOVA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": {"currency": "BTC", "network": "btc"}, "to": {"currency": "USDT", "network": "trx"}, "amount": "0.05", "amount_type": "from", "rate_type": "variable", "end_user_ip": "93.184.216.34" }'
const res = await fetch('https://api.kotova.io/x/v1/quote', { method: 'POST', headers: { Authorization: `Bearer ${process.env.KOTOVA_API_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ from: { currency: 'BTC', network: 'btc' }, to: { currency: 'USDT', network: 'trx' }, amount: '0.05', amount_type: 'from', rate_type: 'variable', end_user_ip: userIp, // your user's public IP }), }); const quote = await res.json();
import os, requests quote = requests.post( "https://api.kotova.io/x/v1/quote", headers={"Authorization": f"Bearer {os.environ['KOTOVA_API_KEY']}"}, json={ "from": {"currency": "BTC", "network": "btc"}, "to": {"currency": "USDT", "network": "trx"}, "amount": "0.05", "amount_type": "from", "rate_type": "variable", "end_user_ip": user_ip, }, timeout=30, ).json()
{
"quote_id": "q_5mJc2Vq9XkT3nR8bYw1LdP",
"expires_at": "2026-11-10T10:17:03Z",
"to": { "currency": "USDT", "network": "trx", "amount": "3389.8" },
"provider": { "name": "Kotova X", "icon": { … } },
"source": {
"slug": "sideshift",
"notice": { "text": "The exchange service is provided by SideShift. …" }
},
"fallback_sources": [
{ "source": { "slug": "changenow", … }, "to": { "amount": "3376.2" } }
]
}
Kotova X is built on the partner APIs of the sources it connects. You could integrate them one by one. This is what that involves.
| Topic | Each source yourself | With Kotova X |
|---|---|---|
| Sign-up | A partner account and key per source | One self-serve key in your Kotova account |
| Authentication | Signed request bodies, nonce-and-timestamp signatures, a secret plus your user's IP | One bearer key in one header |
| Catalog | Each source names assets and networks its own way; you keep the mapping | One catalog with stable codes |
| Statuses | Each source has its own codes, numeric at some, text at others | One documented list of nine statuses |
| Order rules | Different quote lifetimes, minimums and refund-address rules | The quote says what the order needs |
| Problem orders | Each source's own hold, refund and support process | One list of actions on the order, offered in your app |
| Failover | Your own fallback when a source is down or limits you | Busy or failing sources are skipped; the next best can take the order |
| Icons | Find, host and update them yourself | Icon URLs on a CDN, with a mirror |
| Earnings | An affiliate program, dashboard and payout per source | One affiliate profile, one payout |
| New sources | Every new source is a new integration | They appear in the API without code changes |
Based on the sources' public API documentation.
Your API key belongs to your affiliate profile. Every order created with it earns you a share of Kotova's net revenue — the same as an order through your referral link. Orders that expire or are refunded earn nothing, and cost you nothing.
of Kotova's net revenue on each completed order, by default
Request a higher rate or a higher rate limit on your account page.
Paid out in USDC or USDT on BNB Chain, Solana, Arbitrum or Ethereum — USDT on Tron too.
API orders and referral-link orders add up in one place.
Sign in at app.kotova.io, turn on two-factor authentication, generate your referral code and create the key. It is shown once: keep it on your server.
Request a quote and show it with Kotova X as the provider. Before your user confirms, show the notices of the source and its fallback sources.
Create the order with your user's address, show the deposit address the source issued, and read the order until it is final.
Yes. The quoted rate already includes every service charge; network fees are separate.
No. You need one, for the key. Your users stay in your app.
Not your app and not Kotova. Your user sends to a deposit address the source issued for the order; a refund also comes from that source.
Kotova performs no identity checks itself. Connected centralized sources may do so case by case.
The API returns the best offer plus the next best ones as fallbacks. To let your users compare every offer, send them to app.kotova.io.
Yes. Send exclude_sources with the quote. The order then uses only the sources that quote names.
250 units a minute per account by default. Most calls weigh 1, an order weighs 50. Ask for more on your account page.
Kotova X as the provider, by name and icon, and — before they confirm — the notices of the quote's source and its fallback sources. Link the Kotova Terms of Service and Privacy Policy too. Display requirements
Create your key in a few minutes, or read the docs first.
Questions about an integration? api [at] kotova.io