Last updated: 2026-06-06
Give the docs to AI tools
If you use ChatGPT, Claude, Cursor, Cline, Aider, Codex, or another AI coding tool, give it this documentation entry point:Copy this prompt
Paste this prompt into your AI tool:Common uses
| What you want the AI to do | Suggested wording |
|---|---|
| Generate integration code | “Read llms.txt, then write a Python/Node.js Crazyrouter API example.” |
| Use a specific model | “Read llms.txt and confirm which Crazyrouter API endpoint this model should use.” |
| Configure an IDE or agent | “Read llms.txt and show me how to configure Crazyrouter in Cursor / Cline / Claude Code.” |
| Debug an error | “Read llms.txt and the error-handling docs, then help me analyze this Crazyrouter API error.” |
| Generate video or images | “Read llms.txt and give me the Crazyrouter request example for video/image generation.” |
When to use llms-full.txt
llms.txt is a compact index. It helps the AI decide which docs to read first.
If your AI tool can read longer files, or you want to provide the full documentation context at once, also provide:
Where model and pricing data comes from
Models can change based on channels, permissions, and platform configuration. Documentation examples explain the request format; they are not the complete model catalog. For current public models, pricing, and billing details, use:cURL
Single-page Markdown
Many docs pages are also available as Markdown. Add.md to the page URL, for example:
llms.txt first, then provide the specific .md page links it needs.