> ## 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.

# Orchestration

> Combine Eco transfers, deposit addresses and transaction programs in your application.

You can combine Eco products to handle funding, transfers and destination execution in your application. Choose the integration path that matches how users provide funds and what needs to happen on the destination chain.

## Choose a starting point

| Your application needs to | Start with |
| - | - |
| Request a cross-chain transfer and submit its funding transaction | [Routes API](/platform/routes-api) |
| Receive funds at a deposit address | [Programmable Addresses](/programmable-addresses/overview) |
| Run a predefined sequence of calls after a transfer | [Destination calls](/routes/capabilities/destination-calls) |
| Read onchain state and choose execution logic within a transaction | [Programmable Transactions](/programmable-transactions/overview) |

## Design the flow

1. Choose the funding method and destination chain.
2. Decide whether the destination needs a token transfer, fixed contract calls or a Sauce program.
3. Follow the selected product's setup and submission guide.
4. Track each transfer and handle failures at the step where they occur.

A destination program runs atomically on its own chain. A flow spanning several chains uses separate transactions; a later failure does not reverse an earlier completed transaction. See [settlement and orchestration](/concepts/settlement-vs-orchestration) for the distinction.

## Next steps

* [Send USDC across chains](/cookbook/send-usdc-cross-chain).
* [Explore Programmable Addresses](/programmable-addresses/overview).
* [Build a Sauce program](/programmable-transactions/sauce/getting-started).