The pain you’re solving
- Agents writing contracts is risky and slow
- Multi-step cross-chain strategies break when chain state shifts mid-flow
- Per-chain wallet management explodes operational complexity
- “What just happened” is hard to reconstruct when an agent emits 12 transactions
What Eco gives you
| Capability | Product |
|---|---|
| Single-call multi-contract orchestration | Programmable Transactions |
| Cross-chain execution with atomic guarantees | Routes |
| One signature for multi-chain authorization | Permit3 |
| Deterministic deposit address per agent / per task | Programmable Addresses |
| Conditional and best-execution logic in one tx | Programmable Transactions |
Recommended product mix
| Use case | Use |
|---|---|
| Agent moves USDC across chains | Routes API |
| Agent picks best DEX route at execution time | Programmable Transactions |
| Agent has authority to spend across chains | Permit3 |
| Agent receives payments from anywhere | Programmable Addresses |
Patterns
Single-tx best-execution swap
Agent decides to swap. Instead of querying three DEXes and submitting four transactions, it emits one Programmable Transaction that quotes Uniswap, Aerodrome, and PancakeSwap atomically and executes on the winner. MEV-resistant, atomic, no contract deployment. → Programmable Transactions overviewCross-chain execution with bounded authority
User signs one Permit3 authorization granting an agent spending power across chains, with amount limit, expiration, scope. Agent operates within those bounds; revocation is one tx. → Permit3Auditable multi-step strategy
Agent emits one composite intent — bridge, swap, deposit — that succeeds or refunds atomically. Postmortem is one transaction trace, not 12.Get started
→ Programmable Transactions overview — the primary surface for agent-driven executionRead next
Programmable Transactions
Embed best-execution and conditional logic inline.
Permit3
Bound multichain authority with one signature.
Routes API
Programmatic cross-chain transfers and swaps.