Orchestration is in beta and available to Eco partners for early access. It exists today as a composition pattern across Eco’s existing products; a unified Orchestration API is on the roadmap. Contact us to integrate.
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 | Deterministic-address funding |
| Programmable Transactions | Runtime decision logic, best-execution selection |
| Permit3 | Single-signature multi-chain authorization |
| Verified Liquidity | KYB’d solver network, KYC/AML/OFAC-screened users, per-transfer audit record |
Roadmap
| Item | Status |
|---|---|
| Composition pattern docs (recipes) | Available — see Recipes |
Unified /orchestration/* API | In design |
| Verified Liquidity, the permissioned fulfillment lane | Closed access, contact to integrate |
| Single-API “compose” surface for partners | Future |
Read next
Recipes
Composition patterns that already work today.
Contact us
Early-integrator access.