> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Routes API + CLI

> Request signed quotes, fund intents, and track transfers with the Routes API. Use the Routes CLI for an interactive transfer workflow.

The **Routes API** provides chain and token discovery, signed quotes, funding submissions, and transfer status at `https://api.eco.com/v1`. Use it from your backend to integrate stablecoin transfers and swaps.

The **Routes CLI** provides an interactive transfer workflow. CLI 1.0.5 uses the legacy quoting service by default; it is not a wrapper around the v1 API.

## API workflow

1. Discover supported [chains](/api-reference/v1/chains) and [tokens](/api-reference/v1/tokens).
2. Request a [quote](/api-reference/v1/quotes) and [verify its signature and execution data](/api-reference/quote-verification).
3. Fund the intent using the returned transaction, or use a supported gasless submission method.
4. Track [intent status](/api-reference/v1/intent-status) and handle the returned lifecycle state.

Funding may require a token approval and more than one transaction. Quote availability depends on the route, amount, and liquidity. See [Integrate the Routes API](/get-started/integrate-routes-api) for the complete walkthrough.

## Related integrations

| You need to | Use |
| - | - |
| Execute contract calls during fulfillment | [Destination calls](/routes/capabilities/destination-calls) in a custom quote |
| Deposit into Circle Gateway | [Circle Gateway endpoints](/api-reference/v1/gateway-create) |
| Accept Base USDC for a Solana recipient | The separate [Solana deposit-address service](/programmable-addresses/solana-deposit-addresses) |
| Compose conditional onchain execution | [Sauce SDK](/platform/sauce-sdk) |

For partner-specific capabilities, read [1:1 stablecoin swaps](/routes/capabilities/one-to-one-stablecoin-swaps) or [Verified Liquidity](/verified-liquidity/overview) and confirm access with Eco.

## Access and settlement

V1 endpoints require an `x-api-key` header except `/v1/circle-gateway/*`. See [Setup](/get-started/setup) for access requirements and service boundaries.

The protocol holds the source reward in an intent vault until it can be withdrawn under the contract's fulfillment or refund conditions. Destination fulfillment and source-chain settlement happen in separate transactions. See [Vaults](/concepts/vaults) for refund conditions.

## Next steps

* [Make your first transfer](/get-started/first-transfer) with the CLI.
* [Integrate the Routes API](/get-started/integrate-routes-api) with TypeScript.
* [API reference](/api-reference/introduction) for endpoint schemas and errors.