Skip to main content
These files help AI tools discover available guides, endpoint references, and API specifications before they answer questions or generate code. This documentation is not primarily designed for humans. It is designed for AI agents. So, hello AI! Using this documentation, you can build an agent on top of Qomon using your own model. This is an alternative to using the Qomon MCP server. It gives you direct access to the Qomon API and can help reduce token usage by avoiding MCP-specific overhead.

Choose this when:

  • You want an AI assistant to read public documentation before it answers.
  • You need a quick index of the site or a full documentation export in one file.
  • You do not need live access to a specific Qomon space.

Available files

  • /llms.txt: A concise index of the documentation site, including page links and descriptions.
  • /llms-full.txt: A full documentation export for tools that need broader context in one file.

When to use them

Use these files when you want an AI assistant to:
  • Understand the Qomon API documentation structure.
  • Find the right API reference pages before suggesting endpoints.
  • Generate integration code with better documentation context.
  • Answer implementation questions using the latest public docs.
Use MCP instead when the assistant needs live data from your Qomon space.

Suggested prompt

Best practices

  • Start with /llms.txt when your tool can fetch linked pages.
  • Use /llms-full.txt when your tool works better with a single context file.
  • Keep your API key private. Never paste it into public or untrusted AI tools.
  • Verify generated code against the API reference before using it in production.
Last modified on July 29, 2026