Multi-Bridge Routes
Route aggregation and optimization using ARC API integration for complex cross-chain scenarios
Overview
Multi-Bridge Routes is the Agglayer SDK's Core module that provides access to ARC API. This powerful service aggregates routes from multiple bridge providers, enabling complex cross-chain operations that would otherwise require multiple separate integrations.
The ARC API combines routes from Agglayer Bridge and LiFi Bridge into a single interface, automatically finding the most cost-effective and fastest paths while providing risk assessment for each route.
Core Features
Route Discovery
Find optimal cross-chain routes with advanced filtering, optimization preferences, and risk assessment. Supports complex routing scenarios.
Learn more →
Chain & Token Metadata
Access comprehensive information about supported chains, tokens, and bridge capabilities. Perfect for building dynamic UIs and token selectors.
Learn more →
Transaction Building
Convert discovered routes into executable transactions with proper call data, gas estimates, and approval requirements.
Learn more →
Transaction History
Track and monitor cross-chain transactions across all bridge providers. Essential for building user dashboards and transaction status interfaces.
Learn more →
Understanding Gas Fees
Learn how gas fees and bridge costs vary by route provider. Real transaction examples show cost differences between Stargate, Across, and other bridges.
Learn more →
Complete Guides
Production Implementation Guide
Complete production implementation with service architecture, error handling, monitoring, and real-time transaction tracking for mainnet deployment.
Learn more →
What Multi-Bridge Routes Enables
Instead of integrating with multiple bridge APIs separately, Multi-Bridge Routes gives you access to all possibilities through a single interface:
graph TB
subgraph "Your Application"
UI[Bridge Interface]
Logic[Route Selection Logic]
end
subgraph "Agglayer SDK"
MBR[Multi-Bridge Routes<br/>Core Module]
end
subgraph "ARC API"
Aggregator[Route Aggregator]
end
subgraph "Bridge Providers"
AB[Agglayer Bridge<br/>L1 <-> L2 Direct]
LiFi[LiFi Bridge<br/>Multi-Chain Support]
end
UI --> Logic
Logic --> MBR
MBR --> Aggregator
Aggregator --> AB
Aggregator --> LiFi
style MBR fill:#e3f2fd
style Aggregator fill:#fff3e0When to Use Multi-Bridge Routes
Use Multi-Bridge Routes when you need route optimization across multiple bridge providers, cross-chain bridging from non-Agglayer chains, or want to build user-friendly interfaces with automatic route comparison. It's perfect for handling complex bridge scenarios automatically with production-ready routing and comprehensive metadata.
Quick Example
Here's how simple it is to discover and execute cross-chain routes:
import { AggLayerSDK } from '@agglayer/sdk';
// Initialize SDK
const sdk = new AggLayerSDK();
const core = sdk.getCore();
// Discover routes from Base to Katana
const routes = await core.getRoutes({
fromChainId: 8453, // Base
toChainId: 747474, // Katana
fromTokenAddress: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913', // USDC on Base
toTokenAddress: '0x203a662b0bd271a6ed5a60edfbd04bfce608fd36', // USDC on Katana
amount: '1000000000', // 1000 USDC
fromAddress: '0xYourAddress',
slippage: 0.5,
});
// Get best route and build transaction
const bestRoute = routes[0];
const transaction = await core.getUnsignedTransaction(bestRoute);
// Transaction ready for signing and execution
console.log('Bridge transaction built:', transaction.to);Last updated on