Choose your product

Eco currently features four products. Pick the one that matches what you’re building.

​

The 30-second decision

​

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

Deterministic CREATE2 addresses with pre-programmed actions — when funds arrive, the actions execute automatically. Live today:

• Circle Gateway 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 (beta) Contact for access

Make a single transaction smart enough to read state from multiple contracts, pick the optimal path, and execute atomically. No contract deployment required. 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 (beta) Contact for access

Combines Routes, Programmable Transactions, Permit3, and compliance hooks behind a single API for teams 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 Programmable Transactions swap, and a Routes destination call into one composable flow.

​

Read next