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

# Choose your product

> Match your use case to one of Eco's four products in 30 seconds.

Eco currently features four products. Pick the one that matches what you're building.

## The 30-second decision

| If you want to…                                                                                                         | Use                                                 | Live today |
| ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | ---------- |
| Move stablecoins between chains in one signed action                                                                    | [Routes](/routes/overview)                          | ✅          |
| Give a user a deterministic address with pre-programmed actions. Arriving funds auto-route to the right chain and token | [Programmable Addresses](/addresses/overview)       | ✅          |
| Embed decision logic into a single transaction (best-price selection, conditional execution)                            | [Programmable Transactions](/transactions/overview) | Beta       |
| Compose routing, liquidity, and compliance behind one API                                                               | [Orchestration](/transactions/orchestration)        | Beta       |

<Note>
  Beta products are available to **Eco partners for early access**. [Contact us](mailto:contact@eco.com) to integrate.
</Note>

## Detailed comparison

### Routes: Real-time transfers and swaps

The default product. An intent-based execution layer for stablecoin movement. Best execution comes from solver competition; failure modes are atomic refunds.

**Use Routes when** you need: cross-chain transfers, cross-stable swaps (RFQ), gasless deposits via Permit3, or destination calls that bridge-and-deposit in a single intent.

**Don't use Routes when** the user shouldn't have to interact with your app at the moment of funding. That's [Programmable Addresses](/addresses/overview).

→ [Routes overview](/routes/overview)

### Programmable Addresses: Custom deposit & withdrawal logic

Deterministic CREATE2 addresses with pre-programmed actions: when funds arrive, the actions execute automatically. Live today:

* [**Circle Gateway Deposits**](/addresses/gateway-fast-deposits), fast, gasless USDC deposits into Circle Gateway from Base/Optimism/Arbitrum, settled in 20–40 seconds

**Use Programmable Addresses when** the funding event needs to be a plain ERC-20 transfer, from any wallet, exchange, or partner, with no bridge UI and no signature.

→ [Programmable Addresses overview](/addresses/overview)

### Programmable Transactions: Advanced routing & execution <span style={{opacity: 0.6}}>(beta) Contact for access</span>

Make a single transaction smart enough to read state from multiple contracts, pick the optimal path, and execute atomically. No contract deployment required.

**Use Programmable Transactions when** the optimal path depends on live onchain state at execution time (best-price aggregation, MEV-resistant routing, agentic strategies).

→ [Programmable Transactions overview](/transactions/overview)

### Orchestration <span style={{opacity: 0.6}}>(beta) Contact for access</span>

Combines Routes, Programmable Transactions, Permit3, and compliance hooks behind a single API for teams who want one integration point.

**Use Orchestration when** you're building a regulated payment flow, an agentic system that needs all of the above, or a partner integration where you don't want to glue products together yourself.

→ [Orchestration overview](/transactions/orchestration)

## When to combine

Most non-trivial integrations use more than one product:

* A **payment platform** uses Programmable Addresses for funding and Routes for settlement.
* A **DeFi protocol** uses Routes for cross-chain deposits and Programmable Transactions for best-price internal routing.
* An AI agent uses Orchestration to chain a Programmable Address deposit, a Programmable Transactions swap, and a Routes destination call into one composable flow.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="play" href="/get-started/quickstart">
    Move your first USDC across chains in 5 minutes.
  </Card>

  <Card title="Solutions for you" icon="users" href="/solutions/wallets">
    Persona-shaped guides with the right product picked for you.
  </Card>
</CardGroup>