Build with AI agents

Give your coding agent access to Eco’s documentation before asking it to build an integration. The documentation tools provide reference material; your application still needs service credentials and a wallet integration to submit transfers.

Prerequisites

A coding agent that can read URLs, install skills, or connect to an HTTP MCP server.
Node.js and npm if you use the skills installer.
The credentials and runtime from Setup before testing an API integration.

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-api-v1`	V1 quote requests, verification, funding, status, and errors
`eco-smart-deposit-addresses`	Circle Gateway and Solana deposit-address workflows
`eco-solver`	Solver quote endpoints and the fulfillment lifecycle
`eco-sauce`	Sauce compilation, execution, and Routes integration

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

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.
An MCP client cannot connect: confirm it 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

Agent integration for the transfer script and verification boundaries.
Eco for agents for application patterns.

Introduction

Who uses Eco

Build with AI agents

Prerequisites

Install documentation skills

Connect the docs MCP server

Use a starting prompt

Read documentation as Markdown

Troubleshooting

Next steps

​Prerequisites

​Install documentation skills

​Connect the docs MCP server

​Use a starting prompt

​Read documentation as Markdown

​Troubleshooting

​Next steps

Prerequisites

Install documentation skills

Connect the docs MCP server

Use a starting prompt

Read documentation as Markdown

Troubleshooting

Next steps