> For the complete documentation index, see [llms.txt](https://docs.sail.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sail.money/for-ai-agents.md).

# For AI agents

Sail's docs are built to be read by machines as much as by people. Sailor is operated **through** coding agents, so pointing your assistant at these docs is a first-class workflow — not an afterthought.

## Ask your agent

Paste this into Claude Code, Cursor, Codex, ChatGPT, or any coding agent to get it up to speed and building:

```
Read https://docs.sail.money/llms-full.txt and explore the contents.
Then summarize what Sail is, how it works, and how a developer uses Sailor to
build and run a bounded, agent-managed account (SMA). When I confirm, install
Sailor (npm i @sail.money/sailor && npx sailor init) and walk me through
deploying an SMA and authoring a bounded mandate.
```

{% hint style="info" %}
This is a plain code block — use its built-in copy button. If your GitBook reader shows page-level **Copy as Markdown / Open in ChatGPT / Open in Claude** actions, those work too; nothing extra to install.
{% endhint %}

## Machine-readable context (llms.txt)

The docs publish structured static context at the site root, following the `llms.txt` convention:

* [**llms.txt**](https://docs.sail.money/llms.txt) — a structured index of every page, with links.
* [**llms-full.txt**](https://docs.sail.money/llms-full.txt) — the full expanded context, every page concatenated.

Point your agent at `llms.txt` for a map of the docs, or `llms-full.txt` to load everything at once.

## Understand vs. operate

The docs and the Sailor package do different jobs — you use them together:

* The **docs** (`llms.txt` / `llms-full.txt`) are how an agent **understands** Sail — it reads the documentation.
* The **Sailor package** (`npm i @sail.money/sailor`, or the [Docker image](/sailor/docker.md)) is how an agent **operates** Sail — deploying SMAs, signing mandates, and dispatching.

> **Point your agent at the docs so it understands Sail, then install** [**Sailor**](/sailor/getting-started.md) **(`npm i @sail.money/sailor`) so it can operate Sail.**

A typical first instruction:

> *"Read the Sail docs' llms-full.txt, then set up a Sail SMA on Base that only lets the agent swap USDC↔WETH on Uniswap V3 up to 500 USDC per trade."*

The assistant reads the relevant pages, installs Sailor, scaffolds the project, authors a bounded permission, simulates it, and runs.

New here? Start with the [Sailor overview](/sailor/sailor.md) and [Operate Sailor with a coding agent](/sailor/getting-started/coding-agent.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sail.money/for-ai-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.