Build with AI agents

You can give a coding agent reference material for an Eco integration or Sauce SDK tools to develop onchain programs. These serve different purposes:

Your task	What to connect	What it provides
Build an application that uses Routes or deposit addresses	Eco documentation skills, the docs MCP server, or Markdown pages	API formats, integration guides, and reference examples
Write and test a Sauce program	The Sauce SDK’s MCP server and agent skills	Tools to compile, simulate, and build transactions, plus language guidance

MCP (Model Context Protocol) lets an agent access a tool server. The Eco docs MCP server searches documentation. The Sauce MCP server runs Sauce development tools. Connect either or both, depending on your project.

Prerequisites

A coding agent that can read URLs, install skills, or connect to an MCP server.
Node.js and npm for the documentation skills installer; Node.js 24 or later for the Sauce SDK.
The credentials and runtime from Set up your integration before testing a Routes API integration.

Add the Sauce MCP server

Follow Sauce for AI agents to install the command, configure your agent, and check that its tools are available. That guide also covers the Sauce skills and the workflow from a request to an unsigned transaction. The local Sauce server can expose wallet tools. Whether it can sign depends on its configuration and wallet permissions. Review agent and wallet access when choosing how your agent will use it.

Install documentation skills

npx skills add https://docs.eco.com

Select the skills and agent targets offered by the installer. The deployed site’s skills index lists the available skills. New skills appear after the corresponding documentation changes are deployed.

Skill	Scope
`eco-routes-api`	V1 quote requests, verification, funding, status, and errors; routes app and script requests to the tested boilerplates
`eco-smart-deposit-addresses`	Circle Gateway and Solana deposit-address workflows
`eco-solver`	Solver quote endpoints and the fulfillment lifecycle
`eco-sauce`	Points the agent to the Sauce MCP server, `sauce skills install` and the Sauce docs

For the API reference script, use Agent integration. Do not assume the skills installer also copies supporting scripts.

Connect the docs MCP server

The docs MCP server is available at https://docs.eco.com/mcp. Configure that URL in your MCP client. For Claude Code:

claude mcp add --transport http eco-docs https://docs.eco.com/mcp

The server provides documentation search. Its server card describes the exposed tools. It does not submit transfers or provide wallet credentials.

Use a starting prompt

Tell your agent the application you want to build and the integration you chose. For a browser application, point it to the wallet transfer app and quote verification module. For a server-side script, you can use this prompt:

Read https://docs.eco.com/llms.txt and the Routes API integration and quote-verification guides.
Write a TypeScript script that requests an exact-in quote for 1 USDC from Base (8453)
to OP Mainnet (10), using my recipient and funder addresses from environment variables.
Use ECO_API_KEY as x-api-key. Verify the quote signature and execution data against
the request. Handle HTTP errors and expired quotes. First show the funding transaction
without broadcasting it. Add a separate execution step and status tracking, including
unfulfilled and refunded outcomes. Keep credentials out of source code and logs.

Read documentation as Markdown

Resource	Purpose
llms.txt	Page index with summaries
llms-full.txt	Combined documentation text
Page URL with `.md` appended	Markdown version of an individual page
API reference	Request and response schemas, authentication, and errors

Troubleshooting

A skill is missing: check the deployed skills index; a change on a preview branch may not be published yet.
A desktop client cannot start sauce: confirm it can find both Node.js and the Sauce command. See Installation for client configuration and executable paths.
The docs MCP server cannot connect: confirm your client supports the server’s HTTP transport and can reach the docs host.
Generated code uses the wrong API format: supply the v1 integration guide explicitly. V1 and the legacy Open quoting service have different schemas.

Next steps

Sauce for AI agents for the Sauce MCP server and agent skills.
Agent integration for the transfer script and verification boundaries.
Eco for agents for application patterns.

Learn about Eco

Start building

Who uses Eco

Build with AI agents

Prerequisites

Add the Sauce MCP server

Install documentation skills

Connect the docs MCP server

Use a starting prompt

Read documentation as Markdown

Troubleshooting

Next steps

​Prerequisites

​Add the Sauce MCP server

​Install documentation skills

​Connect the docs MCP server

​Use a starting prompt

​Read documentation as Markdown

​Troubleshooting

​Next steps

Prerequisites

Add the Sauce MCP server

Install documentation skills

Connect the docs MCP server

Use a starting prompt

Read documentation as Markdown

Troubleshooting

Next steps