Skip to main content
Every pair returned by GET /v1/orchestration/routes is a valid Orchestra source and destination pair. Use it with /estimate and /quote, then submit the funded deposit for delivery. Bitcoin remains a central rail. Orchestra also routes stablecoins and other assets between supported networks without requiring BTC on either side of the transaction.

​
What a route defines

A route is an ordered pair of chain and asset endpoints:
Current examples include: The live table changes as chains, assets, and provider capacity change. Query it at runtime instead of copying a static list into your application.

​
Discover live pairs

No authentication is required:
Filter the response before displaying a route picker. This example lists destinations currently available for Base USDC:
Each entry includes contract or mint addresses, decimals, chain identifiers, display metadata, and two capability flags:
  • exactOutEligible means the recipient amount can be fixed with amountMode: "exact_out".
  • fixedEligible means the pair can support deliveryMode: "fixed", subject to partner configuration.
Read both flags from the selected pair. Asset symbols alone do not determine delivery support.

​
How Orchestra prices a route

Orchestra quotes compatible paths and providers in parallel when a route has more than one available option. It ranks viable plans by net destination output after route fees and estimated execution gas, then returns the strongest result received inside the pricing window. Not every route has several eligible paths. Market liquidity, provider availability, confirmation policy, and route controls can narrow the candidates for a given request. An Orchestra quote reports the best executable result available to Orchestra at that moment, not a comparison against every venue in the market. This matters most for stablecoin routing. The same source and destination pair may be served by a direct transfer, a bridge, an intermediate stablecoin, or a swap venue. Your integration sends one quote request and receives one deposit instruction.

​
Amount and delivery constraints

The same API serves user payments and large transfers. Every request remains subject to the selected pair’s live bounds and available liquidity. GET /v1/orchestration/limits reports typed bounds for canonical routes. Some generalized planner routes appear on /routes but not /limits today. Call /estimate while the user edits an amount, handle amount errors from /estimate or /quote, and avoid presenting a route as available based on the pair list alone. Generalized routes currently use exact-in, variable delivery unless their /routes entry says otherwise. Amounts covers amount modes and bounds. Pricing covers estimate, quote, and delivery semantics.

​
Bitcoin routes

Bitcoin L1, Lightning, and Spark routes use the same API and add Bitcoin-specific capabilities where they apply. These include Lightning invoices, ZeroConf processing for eligible Bitcoin L1 deposits, direct BTC delivery, and USDB settlement on Spark. Use the dedicated guides for Bitcoin flows: For routes without a BTC endpoint, use General Swaps.

​
Start building

Create an account in the Orchestra dashboard. Flashnet reviews new accounts before enabling API access. Once approved, continue with the Quickstart.