LLM Context Files
Klozeo publishes machine-readable documentation at build time so that AI assistants and agents can ingest it directly, without scraping HTML.
This is based on the llmstxt.org convention.
Available files
Section titled “Available files”| File | URL | What’s in it |
|---|---|---|
llms.txt | docs.klozeo.com/llms.txt | Index — links to all other files with descriptions |
llms-full.txt | docs.klozeo.com/llms-full.txt | Complete documentation, all pages in markdown |
llms-small.txt | docs.klozeo.com/llms-small.txt | Compact version — tips, notes, and whitespace removed |
Category subsets
Section titled “Category subsets”For large context windows where you only need a specific area:
| File | URL | Content |
|---|---|---|
| API Reference | docs.klozeo.com/_llms-txt/api-reference.txt | Leads, Notes, Attributes, Scoring Rules, Webhooks, Export |
| MCP Integration | docs.klozeo.com/_llms-txt/mcp-integration.txt | Claude Desktop, Claude Code, Cursor, Cline setup guides |
| SDKs | docs.klozeo.com/_llms-txt/sdks.txt | TypeScript, Python, Go, Rust SDK documentation |
When to use which file
Section titled “When to use which file”Building something with the full API → use llms-full.txt or the api-reference.txt subset.
Tight context window → use llms-small.txt — same coverage, ~40% smaller.
Connecting via MCP → use mcp-integration.txt — has all the setup steps for every supported client.
Asking an AI assistant a quick question → point it at llms.txt first — it will pick the right subset.
Usage examples
Section titled “Usage examples”Passing context in a prompt
Section titled “Passing context in a prompt”Read https://docs.klozeo.com/llms-full.txt then help me implement lead filtering with the Go SDK.Claude Code / cursor rules
Section titled “Claude Code / cursor rules”Add to your project’s CLAUDE.md or .cursor/rules:
Klozeo API docs: https://docs.klozeo.com/llms-full.txtUsing the MCP server
Section titled “Using the MCP server”If you’ve set up the Klozeo MCP integration, your AI client already has live access to your lead data. The context files complement MCP — they document the API itself, not your data.