Skip to main content
Eco’s developer platform supports moving stablecoins and acting on them. You can build payments and swaps across chains, accept supported deposit flows, manage lending positions, or run a program that chooses actions based on current onchain state. The two main developer entry points are Routes API + CLI and Sauce SDK. Choose a transfer interface, program execution tools, or both, according to the workflow you are building.

​
Start with an outcome

These capability names describe outcomes. The linked guides explain the products, supported services and technical requirements behind each one.

​
Build onchain execution with the Sauce SDK

A program can make payments, compare swap pools, supply or borrow through lending protocols, and check your price, balance or health-factor limits. It reads state and chooses actions during execution. The SDK helps you compile the program, simulate it and prepare its transaction. This execution can be standalone. You do not need a Routes transfer to run a Sauce program. Your application or agent can submit programs as part of an automated workflow; it remains responsible for triggers, authorization and transaction submission. Start with Sauce SDK quickstarts for payment, swap, lending and conditional examples, or use the TypeScript library to integrate execution into your application.

​
Connect funding, execution and settlement

A workflow can use one or more of these stages:
  1. Funding: a wallet funds an intent, sends to a supported deposit address, or funds a program’s Pot.
  2. Execution: a solver delivers the transfer, destination calls invoke contracts, or a standalone transaction runs a program.
  3. Settlement and tracking: the application checks the relevant receipts and transfer status; a fulfilled intent’s proof enables reward settlement under the protocol’s conditions.
A program’s calls and checks execute within one transaction on one chain. Source funding, destination fulfillment and reward settlement have separate transaction boundaries. A failed destination transaction does not immediately return source funds; the applicable refund path must complete separately. Orchestration explains how to connect these stages without conflating their interfaces or completion states.

​
Choose where to go next

Routes API + CLI

Request quotes, fund transfers and track delivery.

Sauce SDK

Develop standalone or route-integrated onchain programs.

Choose an integration

Match a specific application requirement to a guide.

Explore use cases

Find patterns for payments, trading, wallets, agents and other applications.