Skip to main content

Documentation Index

Fetch the complete documentation index at: https://eco.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Eco ships four products at different layers of abstraction. Pick the one that matches the outcome you need — not the primitive underneath.

​
The 30-second decision

If you want to…UseLive today
Move stablecoins between chains in one signed actionRoutes✅
Give a user a single static address that auto-routes deposits to a chain or balanceProgrammable Addresses✅
Embed decision logic into a single transaction (best-price selection, conditional execution)Programmable TransactionsPreview
Compose routing + liquidity + compliance behind one orchestration APIOrchestrationPreview

​
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. → Routes overview

​
Programmable Addresses — Custom deposit & withdrawal logic

Persistent CREATE2 addresses that auto-execute a pre-programmed action when funds arrive. Two products today:
  • Solana deposit addresses — static EVM address on Base that auto-bridges USDC to a Solana wallet
  • 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

​
Programmable Transactions — Advanced routing & execution (preview)

Make a single transaction smart enough to read state from multiple contracts, pick the optimal path, and execute it — all atomically, without deploying a contract. Sauce is the protocol; supertransactions are the unit. 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

​
Orchestration (preview)

The composition layer. Wraps Routes + Programmable Transactions + Permit3 + compliance hooks behind a single API for partners 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

​
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 Sauce-based swap, and a Routes destination call into one composable flow.

Quickstart

Move your first USDC across chains in 5 minutes.

Solutions for you

Persona-shaped guides with the right product picked for you.