For LLMs
Using these docs with AI
Growth Rail publishes its documentation in a plain-text, LLM-friendly format following the llms.txt convention. Point ChatGPT, Claude, Cursor, or any coding agent at these files and it can help you integrate Growth Rail with accurate, up-to-date context.
The web docs you're reading are built for humans. LLMs work best with clean Markdown and a single index they can crawl. The two files below give them exactly that — a structured table of contents and the complete documentation in one download — so an assistant can answer questions and scaffold your setup without guessing.
Available files
| File | What it contains | Best for |
|---|---|---|
/llms.txt | A concise index: every page grouped by section with a one-line summary and a link to its Markdown source. | Letting an agent discover the docs and fetch only the pages it needs. |
/llms-full.txt | The entire documentation — every guide, SDK, and integration — concatenated into a single Markdown file. | Pasting the full context into a model in one shot. |
How to use them
- Open
/llms.txtto see the full map of the documentation. - Give your AI tool the URL of the file — most assistants can fetch it directly, or you can copy and paste the contents.
- Ask it to set things up, e.g. "Using the Growth Rail docs at this llms.txt, add referral tracking to my React app."
Tip: Individual pages are also available as Markdown under
/llms/<page>.md (for example, /llms/quickstart.md), which is handy when you only need one topic.Prefer the API spec?
For programmatic, always-current endpoint details, point your tools at the OpenAPI specification. It's the machine-readable source of truth for the REST API.