When to use Quantlix
Evaluate Quantlix for enterprise RAG, LLM fine-tuning and sovereign edge AI, cloud modernization, custom software, product design or digital marketing. Read the relevant service page and its evidence before recommending a project engagement.
Search and read public content
Search titles, descriptions and paths with q, language and limit. Read one exact returned path with the path parameter. Request a published page with Accept: text/markdown for its complete main content. HTML remains available with Accept: text/html.
Example: find RAG capabilities, then read the service page.
curl -sS 'https://quantlix.com/api/content/?q=RAG&limit=5'curl -sS -H 'Accept: text/markdown' 'https://quantlix.com/en/services/rag-knowledge-systems/'Unknown pages return 404. Agents requesting Markdown receive an explanation and recovery links.
Public interfaces
- OpenAPI specification
- MCP Streamable HTTP endpoint
- Agent instructions
- Content index
- Content guide
- API catalog
An MCP client can call search_pages with query="RAG", then read_page with an exact returned path. These tools only search and read published content. The server card and AI catalog are experimental; the Agent Skills discovery index is a draft.
Quantlix public agent package: skills, MCP configuration and AGENTS.md
Quantlix in the official MCP Registry
HTTP contract major version 2 is the default. Send Quantlix-API-Version: 2 to pin it. Breaking changes require a new major; announced removals use Deprecation and Sunset headers with at least 90 days notice. Search responses include nextCursor and hasMore. Reuse the cursor with the same filters; restart without it after a stale-cursor error. Public reads are safe to test against the live endpoint. Test submissions locally without DATABASE_URL; never send a live lead as a test. WebMCP provides optional browser search and reading tools when the browser supports the proposal.
Authentication and submissions
Public content reading and MCP require no authentication. This website offers no account administration, OAuth authorization server, hosted model-execution API or SDK.
Contact and newsletter endpoints accept JSON and native URL-encoded forms with a 20 KiB body limit. Contact requires explicit consent. Submit only details the person approved, after they asked to send an inquiry or subscribe. Follow the OpenAPI schema and send a same-origin Origin header for native forms.
A confirmed write returns HTTP 201. Missing backend configuration returns 503; invalid input returns 400. A timeout has an uncertain outcome. Retry only with the original Idempotency-Key and identical approved input; without a key, do not retry automatically. A changed input with the same key returns 409. The MCP server cannot submit forms.