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.
Orchestration is a preview product. It exists today as a composition pattern across Eco’s existing products; a unified Orchestration API is on the roadmap. Talk to us if you want to be an early integrator.
Why this exists
Most non-trivial integrations span multiple Eco products:- 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 internal best-price routing
- An AI agent chains a Programmable Address deposit, a Sauce-based swap, and a Routes destination call into one composable flow
- A regulated payments app layers compliance (address screening, AML, region rules) over Routes via solver selection
What it composes
| Primitive | What it contributes |
|---|---|
| Routes | Cross-chain stable transfers + RFQ + destination calls |
| Programmable Addresses | Static-address funding |
| Programmable Transactions | Runtime decision logic, best-execution selection |
| Permit3 | Single-signature multi-chain authorization |
| Compliance hooks | Address screening, AML, region enforcement at solver-selection layer |
Roadmap
| Item | Status |
|---|---|
| Composition pattern docs (recipes) | Available — see Recipes |
Unified /orchestration/* API | In design |
| Compliance Engine for solver-selection rules | Preview, contact for access |
| Single-API “compose” surface for partners | Future |
Read next
- Recipes — composition patterns that already work today
- Contact us — early-integrator access