Choose your starting point
Choose your developer tools
These are independent starting points. A standalone Sauce program does not require a Routes transfer. You can combine them when a transfer should also run a program at its destination. Deposit-address integrations use the service-specific APIs documented in Programmable Addresses.
Check supported chains and tokens for Routes coverage and Sauce chains for SDK support. Coverage and requirements differ.
Add contract execution to a transfer
Use destination calls for a known sequence of contract calls, such as approving delivered tokens and depositing them into your application. You include those calls in a custom Routes quote. Use the Sauce SDK when execution needs to read state, choose between actions or apply conditions during the transaction. Sauce in a route explains how a program participates in a Routes intent. Source-chain funding, destination-chain fulfillment and proof are separate transactions. An unhandled failure reverts the affected destination transaction’s changes. Your integration still tracks the cross-chain lifecycle and any refund separately.Explore related mechanisms
- Flash Intents use an intent’s own funds for same-chain fulfillment.
- Orchestration explains how your application coordinates funding, transfers and onchain execution.
- Solvers and market makers explains how to provide liquidity and fulfill intents.
Next steps
- Set up your integration for credentials and runtime requirements.
- Explore use cases for patterns by application type.
- Build with AI agents to connect your coding agent to documentation and development tools.