> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flashnet.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with agents

> Skills and documentation access

Agents can read the same Orchestra guides and API contract as developers, with a reviewed skill for choosing and implementing a flow.

## Install the skill

```bash theme={null}
npx skills add https://docs.flashnet.xyz
```

The [Orchestra skill](https://docs.flashnet.xyz/skill.md) covers flow selection, funding, retries, and order tracking. It links to the current guides instead of copying the API reference.

## Connect documentation search

Add this HTTP MCP server to your agent's MCP configuration:

```text theme={null}
https://docs.flashnet.xyz/mcp
```

The server searches and retrieves documentation. It does not authorize Orchestra API requests or move funds. You can also connect through the page menu's **MCP** option.

## Read directly

* [Documentation index](https://docs.flashnet.xyz/llms.txt): find the relevant pages.
* [Quickstart as Markdown](https://docs.flashnet.xyz/orchestra/quickstart.md): read a guide without the site layout. Append `.md` to other page URLs for the same format.
* [Official OpenAPI](https://orchestration.flashnet.xyz/openapi.json): request and response schemas.
* [Full documentation](https://docs.flashnet.xyz/llms-full.txt): a bulk export when the task needs the entire site.

Start with the index and read only the pages the task needs. Fetch [routes and limits](/orchestra/routes-and-limits) for live availability; keep server keys out of prompts and client bundles.
