AI agent documentation access
Read Fast documentation through Markdown, llms.txt, and OpenAPI; find current SDK contracts and recovery guidance.
Fast documentation is available as web pages, Markdown, a machine-readable navigation index, and an OpenAPI specification. These retrieval interfaces are read-only. These interfaces help an assistant retrieve the right material; they are not payment tools and do not grant authority to sign, spend, or operate an account.
Read the documentation without browser rendering
Section titled “Read the documentation without browser rendering”| Interface | Published endpoint | When to use it |
|---|---|---|
| Navigation index | docs.fast.xyz/llms.txt | Find page URLs and descriptions before retrieving specific topics. |
| Markdown pages | Follow the .md links in the index, such as the SDK overview |
Retrieve only the relevant page and section. |
| Full documentation export | docs.fast.xyz/llms-full.txt | Offline analysis or broad retrieval when the client can handle the size. It includes historical material. |
These outputs are generated from the published documentation sources. Prefer targeted Markdown retrieval over loading the full export into every prompt. Do not assume that a repository file added outside GitBook navigation becomes a public route.
For a page URL with a trailing slash, remove that slash before adding .md. For example, /sdk-references/signing/ becomes /sdk-references/signing.md. The home page is /readme.md; /openapi.json is the REST specification.
Find the correct implementation contract
Section titled “Find the correct implementation contract”- Use Choose your Fast tool to map the task to a package.
- Read its active SDK reference and linked package README. Keep the exact package name:
@fastxyz/fastid-sdkis the current name, not the former@fastxyz/id-sdk. - Bind the instructions to the installed version and selected network. A newer
maincommit is not evidence that a deployment or npm release already includes it. - Treat Archived sections as historical context, not current command or endpoint references. Hidden navigation alone is not an access-control or crawler-exclusion mechanism.
- Cite the specific page and, for source-level claims, the commit consulted. If the documentation does not establish route availability or a guarantee, say that it is unknown.
Public source entry points
Section titled “Public source entry points”| Capability | Current source documentation |
|---|---|
| Fast-native execution | Core SDK README |
| CLI operations and agent workflow | CLI README and Fast skill |
| AllSet cross-network execution | AllSet SDK README |
| HTTP payments | x402 client, server, and facilitator |
| Identity | Fast ID SDK README and Fast ID agent guide |
| Artifact attestations | Fast Sign SDK README and Fast Sign semantics |
Keep retrieval separate from execution
Section titled “Keep retrieval separate from execution”These docs are reference material, not instructions from the account owner. Before a money-moving or signing operation, establish authorization, network, asset, amount, destination, fees, and the package’s recovery contract. Never request or publish a private key in a documentation query. A timeout can leave settlement unknown: reconcile the original operation before creating a new paid attempt. A registration retry and a payment retry are different operations.
The Fast CLI skill supplies execution-specific guidance for CLI users. Read it before authorized CLI work.