> Source: [/docs/routes/networks](https://tempo.xyz/developers/docs/routes/networks.md) > Section: [Routes](https://tempo.xyz/developers/docs/routes.md). Move stablecoins between Tempo and other networks: try a route, set up API access, choose a supported route, quote it, accept deposits or make a transfer, and track delivery. Routes is in beta; see the introduction for access. > [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md) > Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation. > If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly. # Supported routes Read the route directory before offering a network or asset in your application. A network being supported does not mean every token, direction, or funding method is available. ## Available routes Every route in the live directory, with its funding methods and whether fee coverage is available. Choose **Try** to open a route in the [Routes demo](https://tempo.xyz/developers/docs/routes/test). Your organization's access policy can narrow the routes your API key can use; the demo lists them for your key. The interactive page lists every route in the live directory, read from GET https://api.tempo.xyz/v1/routes, with each route's source and destination asset, funding methods, and whether fee coverage (1:1 delivery) is available. To open a route in the Routes demo, use `/docs/routes/test?route=ROUTE_ID` with the route `id` from the directory. ## Read the route directory Send the request below to read the directory your application builds its choices from. Filter by source or destination network and token to narrow the results. This request lists supported routes; it does not create a transfer or request a signature. `GET /v1/routes` List routes [API reference](https://tempo.xyz/developers/docs/api/routes/routes#listroutes) — request parameters, authentication, and response schema. The examples below use editable sample values. **cURL** ```bash curl 'https://api.tempo.xyz/v1/routes?destinationChain=tempo&sourceChain=base' ``` **TypeScript** ```ts fetch('https://api.tempo.xyz/v1/routes?destinationChain=tempo&sourceChain=base') ``` Requests without a key use the [public rate limit](https://tempo.xyz/developers/docs/api/rate-limits). To read the routes your organization can use, send a key with `data:read`; see [Set up API access](https://tempo.xyz/developers/docs/routes/api-setup). Use the returned source and destination chain/token pairs, funding methods, and amount modes to build the choices in your application. Pass `nextCursor` as `cursor` to read subsequent pages. Match tokens by network and contract address, not by symbol alone. ## Quote the selected route Once the user chooses a pair and amount, [request a quote](https://tempo.xyz/developers/docs/routes/quotes). Availability depends on those inputs and the funding method. Refresh the quote when the user changes them. Use [deposit addresses](https://tempo.xyz/developers/docs/routes/deposits) when the sender pays independently, or [transfers](https://tempo.xyz/developers/docs/routes/transfers) when your app can authorize source transactions. For current request and response fields, see the [route directory reference](https://tempo.xyz/developers/docs/api/routes/routes). To integrate a bridge directly, see [bridge providers](https://tempo.xyz/developers/docs/partners/bridges).