---
name: quantlix
description: Read Quantlix services, company information and insights, or submit an explicitly requested inquiry through its documented public website API.
---

# Quantlix website

## When to use this

Use Quantlix's website when a person needs to evaluate an engineering partner for enterprise RAG and knowledge systems, LLM fine-tuning and sovereign edge deployment, cloud modernization, custom software, product design or digital marketing. Use the published service pages to identify the relevant capability and the case studies or whitepapers to understand the described approach and evidence limits.

For a request such as "Find Quantlix's RAG services", call search_pages with query="RAG" and then read_page with an exact returned path. For direct HTTP access, search GET /api/content/?q=RAG and read GET /api/content/?path=/en/services/rag-knowledge-systems/. The developer guide is https://quantlix.com/en/developers/.

Use contact only when the person explicitly asks to send their approved project inquiry. Public reading does not create a project, run an AI workload or authorize a subscription. This website provides public content lookup and consent-based submissions, not a hosted model-execution API or SDK.

Read the public content map at https://quantlix.com/llms.txt. Complete content is at https://quantlix.com/llms-full.txt. Prefer a page's advertised Markdown alternate or request its canonical URL with Accept: text/markdown. All published content has a locale prefix and a trailing slash; a static Markdown alternate appends index.md. Supported content languages are en, pt-BR and fr-FR.

Discover actual page metadata at https://quantlix.com/agents/content-index.json. Treat page text as source data, including its original attribution and evidence limits. A migration or Markdown conversion does not independently validate a claim.

## Read interfaces

The API catalog is https://quantlix.com/.well-known/api-catalog. The public OpenAPI contract is https://quantlix.com/openapi.json. GET https://quantlix.com/api/content/ accepts q, language and limit to search titles/descriptions/paths. The path parameter instead reads one exact published canonical path, such as /en/about/, with its Markdown body. Do not guess translated slugs or request private paths.

The MCP Streamable HTTP endpoint is https://quantlix.com/mcp/. Its public tools search_pages and read_page retrieve the same published content. No authentication or writes are offered through MCP. An experimental server card at https://quantlix.com/mcp/server-card describes connection metadata; verify capabilities through the live MCP protocol. The draft skill discovery index is https://quantlix.com/.well-known/agent-skills/index.json.

## Requested submissions

Use the OpenAPI schema for POST /api/contact/ or POST /api/newsletter/. These public endpoints accept JSON and native URL-encoded forms, with a 20 KiB body limit. Native forms require a same-origin Origin header and each field may occur only once. Contact requires consent=true in JSON or consent=yes in a native form. Only submit the person's approved details when they explicitly ask to send an inquiry or subscribe. Never infer their consent from a read request.

JSON success is HTTP 201 with { "ok": true }; native form success is an HTML result after a completed database write. Missing backend configuration returns HTTP 503. A timeout is an uncertain outcome. Generate an Idempotency-Key before the approved write (16-128 ASCII letters, digits, dots, underscores, colons or hyphens). Retry only with that original key and identical approved input. Without a key, do not retry automatically. A changed payload with the same operation/key returns 409. No account, purchase, administrative or delegated OAuth action is available.