Supported Routes

GET /v2/orchestration/routes lists every asset Orchestra can move and, for each asset, the destinations it can reach. 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 asset endpoints:

sourceChain:sourceAsset -> destinationChain:destinationAsset

Current examples include:

Use case	Source	Destination
Cross-chain stablecoin swap	`base:USDC`	`solana:USDT`
Stablecoin transfer	`ethereum:USDT`	`tron:USDT`
Bitcoin settlement	`lightning:BTC`	`spark:BTC`
Buy Bitcoin	`base:USDC`	`spark:BTC`

The live catalog changes as chains, assets, and provider capacity change. Query it at runtime instead of copying a static list into your application.

Response shape

The response is { assets: [...] } with one entry per supported asset. Each entry carries the asset’s identity, metadata, and a route object holding three destination sets:

{
  "assets": [
    {
      "id": "base:USDC",
      "chain": "base",
      "asset": "USDC",
      "assetDisplayName": "USDC",
      "assetDisplaySymbol": "USDC",
      "chainDisplayName": "Base",
      "chainIcon": "/chain-base.svg",
      "contractAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "decimals": 6,
      "chainId": "8453",
      "route": {
        "to": { "except": ["litecoin:LTC"] },
        "exactOutTo": ["lightning:BTC"],
        "fixedTo": ["bitcoin:BTC", "lightning:BTC", "spark:BTC", "spark:USDB"]
      }
    }
  ]
}

id is the asset’s canonical identity, <chain>:<asset> (for example ton:TON, hypercore:USDC). Every destination set contains these ids.

Field	Meaning
`to`	Destinations routable with `/estimate`, `/quote`, and `/submit`
`exactOutTo`	Subset of `to` that accepts `amountMode: "exact_out"`
`fixedTo`	Subset of `to` that can support `deliveryMode: "fixed"`, subject to partner configuration

Read capability from set membership, not from the asset symbol. Two assets with the same symbol on different chains can differ.

Destination set encodings

Each set is written in whichever of three forms is smallest:

"all": every other asset in the response. Never includes the asset itself.
["a:X", "b:Y", ...]: exactly those destinations. An empty array means none.
{ "except": [...] }: every other asset except the listed ids.

Expand any of them the same way:

type RouteSet = "all" | string[] | { except: string[] };

function expandRouteSet(set: RouteSet, assetIds: string[], selfId: string): string[] {
  const others = assetIds.filter((id) => id !== selfId);
  if (set === "all") return others;
  if (Array.isArray(set)) return set;
  return others.filter((id) => !set.except.includes(id));
}

To test whether base:USDC -> spark:BTC is supported:

const { assets } = await fetch("https://orchestration.flashnet.xyz/v2/orchestration/routes")
  .then((r) => r.json());
const ids = assets.map((a) => a.id);
const base = assets.find((a) => a.id === "base:USDC");
const supported = expandRouteSet(base.route.to, ids, base.id).includes("spark:BTC");

Asset detail fields

Field	Type	Notes
`chain`	`string`	Chain identifier
`asset`	`string`	Asset symbol
`assetDisplayName`	`string`	Human-readable asset name
`assetDisplaySymbol`	`string`	Display symbol
`chainDisplayName`	`string`	Human-readable chain name (e.g. `"Base"`, `"Spark"`)
`chainIcon`	`string \| null`	Chain icon path (e.g. `"/chain-base.svg"`), relative to the API host
`contractAddress`	`string \| null`	Token contract address (EVM, checksummed), mint address (Solana), or token ID (Spark USDB). `null` for native assets (BTC, ETH, SOL, etc.).
`decimals`	`number`	Smallest-unit decimals for the asset (e.g. 6 for USDC, 8 for BTC)
`chainId`	`string \| null`	Chain ID as a string. Numeric for EVM chains (e.g. `"8453"`), CAIP-2 for Solana (`"solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp"`). `null` for spark, bitcoin, and lightning.

Discover live pairs

No authentication is required:

curl -sS "https://orchestration.flashnet.xyz/v2/orchestration/routes"

This example lists the destinations currently available for Base USDC, expanding all three set encodings:

curl -sS "https://orchestration.flashnet.xyz/v2/orchestration/routes" | \
  jq -r '
    def expand($set; $ids; $self):
      if $set == "all" then $ids - [$self]
      elif ($set | type) == "array" then $set
      else $ids - [$self] - $set.except end;
    (.assets | map(.id)) as $ids
    | .assets[]
    | select(.id == "base:USDC")
    | expand(.route.to; $ids; "base:USDC")[]'

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 catalog alone. Generalized routes currently use exact-in, variable delivery unless the destination appears in the source asset’s exactOutTo or fixedTo set. 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.

Overview

Concepts

Guides

Reference

Security

What a route defines

Response shape

Destination set encodings

Asset detail fields

Discover live pairs

How Orchestra prices a route

Amount and delivery constraints

Bitcoin routes

Start building

​What a route defines

​Response shape

​Destination set encodings

​Asset detail fields

​Discover live pairs

​How Orchestra prices a route

​Amount and delivery constraints

​Bitcoin routes

​Start building

What a route defines

Response shape

Destination set encodings

Asset detail fields

Discover live pairs

How Orchestra prices a route

Amount and delivery constraints

Bitcoin routes

Start building