Cross-Chain Routing for Aggregators
Expand your coverage beyond single-chain swaps — powered by SwapKit.
Why Aggregators Use SwapKit
Most DEX and bridge aggregators excel at finding the best intra-chain swaps — but users expect to move value natively between chains too.
Integrating SwapKit lets your aggregator route trades across THORChain, Maya Protocol, Chainflip, and NEAR Intents, providing end users with true cross-chain liquidity through one unified interface.
What SwapKit Enables for Aggregators
- Cross-chain routing layer → connect EVM and non-EVM ecosystems (BTC, Cosmos, Solana, Tron, etc.)
- Unified API → fetch and execute quotes across multiple decentralized liquidity providers.
- Fallback redundancy → automatic failover if a provider or chain is offline.
- Native BTC support → real Bitcoin swaps, not synthetic wrapped assets.
- Destination gas abstraction → simplified UX for end users entering new ecosystems.
Example: Aggregating Cross-Chain Routes
import { SwapKitApi, ProviderName } from "@swapkit/sdk";
const quote = await SwapKitApi.getSwapQuote({
sellAsset: "ETH.ETH",
buyAsset: "BTC.BTC",
sellAmount: "1",
providers: [ProviderName.THORCHAIN, ProviderName.MAYA, ProviderName.CHAINFLIP, ProviderName.NEAR],
});
console.log(quote.data.routes);
Output: a ranked list of multi-provider cross-chain routes with expected output, fees, and slippage — ready to merge with your own aggregator’s routing logic.
Benefits for Aggregators
| Feature | Traditional Aggregator | SwapKit Integration |
|---|---|---|
| Chain coverage | Single-chain (EVM only) | Cross-chain (BTC, Cosmos, Solana, Tron, etc.) |
| Routing logic | Limited to DEXes | Multi-provider cross-chain routing |
| Native BTC support | None | Built-in |
| Redundancy | Manual or none | Automatic |
| Destination gas abstraction | Requires custom logic | Included |
| Integration time | Months per provider | Days with SwapKit |
Seamless Developer Integration
SwapKit plugs directly into your existing aggregator flow — no need to replace your entire routing system.
You can:
- Treat SwapKit as an external routing layer for cross-chain swaps.
- Fetch quotes via the API and merge them with your internal DEX results.
- Control which providers are enabled per asset or region.
- Customize provider priority or weightings.
Real Aggregator Use Cases
- Add native BTC and Cosmos swaps alongside your EVM routes.
- Offer fallback routing across providers for better uptime.
- Enable gas abstraction to simplify onboarding flows.
- Reduce maintenance load — SwapKit handles provider API updates automatically.
Frequently Asked Questions
Q: Can I combine SwapKit quotes with my own DEX aggregator results?
Yes. SwapKit is modular — you can merge its quote results into your existing routing engine or UI.
Q: How does routing prioritization work?
SwapKit ranks providers by effective output (net of fees, slippage, and success probability). You can override or customize priorities.
Q: Can I select which providers to enable?
Yes. You can enable or disable THORChain, Maya, Chainflip, or NEAR Intents individually.