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

> Routes is Eco's intent-based product for real-time stablecoin transfers and swaps across chains, with cryptographic execution guarantees and dual-mode fulfillment.

Routes is Eco's intent-based product for **real-time stablecoin sends and swaps across chains**, built for institutional scale and reliability. Users sign a desired outcome; solvers compete to fulfill it; the source-chain vault releases the reward only on cryptographic proof. The intent-based model delivers lightning-fast execution with predictable pricing, and Routes is live across all major stablecoin assets and chains.

## What Routes does

| Capability                                                  | What it does                                                                           |
| ----------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| [Stable 1:1 transfers](/routes/capabilities/stable-1-to-1)  | Move the same stablecoin (e.g. USDC) between chains at predictable pricing             |
| [Cross-stable RFQ](/routes/capabilities/stable-rfq)         | Swap one stablecoin for another (USDC↔USDT, USDC↔USDG) with competitive solver pricing |
| [Destination calls](/routes/capabilities/destination-calls) | Bridge AND interact with a destination contract atomically, one signature, one outcome |

Routes can also fulfill intents in two execution modes, solver settlement or orchestration, covered under [Settlement vs Orchestration](/routes/architecture/settlement-vs-orchestration) in the architecture section.

## How Routes works

```mermaid theme={null}
graph LR
    User[User]

    subgraph Source [Source chain]
        SrcPortal[Portal]
        Vault[Vault]
        SrcProver[Prover]
    end

    subgraph Dest [Destination chain]
        DestPortal[Portal]
        DestProver[Prover]
    end

    Solver[Solver]

    User -->|"1. publish and fund"| SrcPortal
    SrcPortal -->|"lock reward"| Vault
    Solver -->|"2. fulfill"| DestPortal
    DestPortal -->|"3. prove"| DestProver
    DestProver -.->|"4. dispatch"| SrcProver
    Solver -->|"5. withdraw"| SrcPortal
    SrcPortal -->|"verify and release"| Vault
    Vault -->|"reward"| Solver
```

1. **Publish and fund.** The user creates an intent and funds the source-chain vault.
2. **Fulfill.** A solver delivers the requested outcome on the destination chain.
3. **Prove.** A user-selected prover carries proof of fulfillment back to the source.
4. **Settle.** The Portal verifies the proof and releases the reward.

If no solver fulfills before the deadline, a permissionless refund service returns funds to the user.

## Integration paths

| Path                              | Best for                                 | Time to first transfer |
| --------------------------------- | ---------------------------------------- | ---------------------- |
| [CLI](/routes/integrate/cli)      | Manual operators, scripting, exploration | 5 min                  |
| [REST API](/routes/integrate/api) | Production server-to-server integration  | 15 min                 |

<Tip>
  For the underlying smart-contract surface, see [Architecture](/routes/architecture/overview). For the REST endpoints, see the [API Reference](/api-reference/introduction).
</Tip>

## Architecture at a glance

| Component                                        | Purpose                                                                                            |
| ------------------------------------------------ | -------------------------------------------------------------------------------------------------- |
| [Portal](/routes/architecture/portal)            | Non-upgradable factory contract, entry point for publish, fulfill, prove, withdraw                 |
| [Vault](/routes/architecture/vault)              | Per-intent CREATE2 escrow, non-custodial, deterministic, refund-on-expiry                          |
| [Executor](/routes/architecture/executor)        | Stateless call-execution contract, isolates user code from Portal storage                          |
| [Provers](/routes/architecture/provers/overview) | Modular settlement layer, six options (Chainlink CCIP, CCTP, Hyperlane, LayerZero, Polymer, Local) |
| [ERC-7683](/routes/architecture/erc-7683)        | Standardized cross-chain order interface                                                           |

## Primitives Routes uses

| Primitive                                             | Where                                                                      |
| ----------------------------------------------------- | -------------------------------------------------------------------------- |
| [Permit3](/routes/primitives/permit3/overview)        | Multi-chain token approvals via single signature                           |
| [Crowd Liquidity](/routes/primitives/crowd-liquidity) | Permissionless liquidity backstop, solvers flash-borrow for larger intents |

Routes also has a regulated counterpart, [Verified Liquidity](/verified/overview) <span style={{opacity: 0.6}}>(closed access)</span>: a permissioned fulfillment lane with a KYB'd solver network, OFAC screening built in, and a per-transfer audit record.