Orchestration - Eco Docs

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.

The Orchestration layer combines four primitives behind a single integration surface: Routes, Programmable Addresses, Programmable Transactions, and Permit3.

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

Today, a partner glues these together themselves. The Orchestration API is the future single-call API for these composite flows.

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

Overview

⌘I

​Why this exists

​What it composes

​Roadmap

Why this exists

What it composes

Roadmap