Routes

A route is a pair of chains, from and to, with the speeds Xebra offers on it. The list below is read from GET /v1/routes and refreshed every five minutes. It is the same list the API checks every quote and transfer against.

Where the list comes fromCopy Anchor Link

Routes are not a configuration file. Each source has its own rule:

• From Stellar, the destinations are the ones Xebra's fee contract on Stellar has committed, read from the contract. A new destination takes a 48-hour public wait on the contract before it can be used, and appears here once that wait is over. Stellar offers Standard only.
• From EVM chains, the routes run through Arc: Arc sends to the EVM chains and Solana that Xebra has switched on, and other EVM chains can send into Arc where that direction is switched on. Fast appears where Circle offers Fast Transfer for burns on the source chain.
• From Sui, the one destination is Stellar, Standard only.

Destinations are where the USDC is minted: Stellar, Solana and the EVM chains. Solana is a destination only. Sui is a source only, because Circle's Forwarding Service does not deliver to it (see Forwarding).

Chain namesCopy Anchor Link

The API names chains in lower case: stellar, solana, sui, and the EVM chains arc, base, arbitrum, optimism, avalanche, polygon and others. The full set of names the API accepts is the ChainId type in @xebra/sdk and the ChainId schema in the API reference. A name that is valid is not necessarily a live route: ask /v1/routes.

import { createXebraClient } from "@xebra/sdk";

const xebra = createXebraClient();
const { routes, complete } = await xebra.routes();

const fromStellar = routes.filter((r) => r.from === "stellar").map((r) => r.to);
const fastRoutes = routes.filter((r) => r.speeds.includes("fast"));

completeCopy Anchor Link

The answer carries complete: true when every part of the list was read. If Xebra's contract on Stellar could not be read just then, complete is false and the list may be missing Stellar destinations. Ask again shortly rather than telling a user a route does not exist.

A route that goes awayCopy Anchor Link

A route can be switched off at any time, for example if Circle's Forwarding Service misbehaves on it. Quotes and transfers on a route that is not live are refused with route_unavailable. Transfers already burned are not affected: they can still be delivered or claimed. See Recovery.