Skip to main content
Use the Routes API when your agent application needs to request a stablecoin transfer. Use the Sauce SDK when it needs to make payments, swap tokens, interact with lending protocols or choose actions based on onchain state. A program can run independently of a transfer. Your application defines which actions the agent may request and how transactions are approved and signed. If you want a coding agent to help you build the integration, start with Build with AI agents. That page explains the documentation and development tools available to your agent.

​
Build a transfer tool

The agent integration guide provides a reference transfer script and describes what it verifies. Your tool should validate the requested chain, token, recipient, and amount; verify the quote and funding transaction; and then track the funded intent. Return the intent hash and transaction identifiers so your application can follow up after a timeout. Keep approval and signing within your application’s wallet policy.

​
Develop programs with the Sauce SDK

A Sauce program can read blockchain state and choose which calls to make in one transaction. For example, it can check an available balance before sending a payment, choose between swap pools, or enforce a lending-position check. Your application or agent submits the transaction when the workflow should run; the program itself does not schedule future execution. The Sauce MCP server gives an agent tools to compile, simulate, and build transactions. It can also expose local wallet tools, depending on its configuration. Review the signing options and choose the wallet permissions that fit your application. Use Sauce SDK quickstarts for complete programs, then choose the TypeScript library or agent tools for your integration.

​
Define token permissions

If your integration uses delegated token permissions, review Permit3. Configure the permitted spender, amount, and expiration for the workflow you are authorizing.

​
Next steps