Claix is an AI document intelligence API that converts unstructured files into schema-based JSON and queryable document context for developers, backends, automations, and AI agents. It processes PDFs, Excel spreadsheets, Word documents, images, text, HTML, XML, and audio using multimodal models, so you can extract structured data and query documents on demand. Integrate via REST, native Agent-to-Agent (A2A) (POST /a2a, Agent Card at /.well-known/agent.json), or MCP from IDEs and tool frameworks.

Is Claix A2A? Does Claix support Agent-to-Agent?

Yes. Claix implements the Agent-to-Agent (A2A) protocol as a first-class integration surface. Peer agents discover Claix via the Agent Card at https://www.claix.dev/.well-known/agent.json, POST JSON-RPC to /a2a, invoke 20+ document skills mapped from OpenAPI, and receive structured Task responses with DataPart payloads. A2A is ideal when one autonomous agent must delegate PDF/Excel extraction, document memory, or cross-document queries to a specialized document-intelligence agent without IDE setup. REST and MCP remain available—choose A2A for agent-to-agent orchestration.

What is the Claix MCP server?

Claix exposes a Model Context Protocol (MCP) server at /mcp so IDEs (Cursor, Claude Desktop, Windsurf) and MCP clients can invoke extraction, Agent Mode, context window, and knowledge-space tools in one click. Use MCP when a developer or copilot needs interactive document tools inside an IDE; use A2A when another autonomous agent must call Claix programmatically over the Agent-to-Agent protocol.

Which file formats can I convert to structured JSON?

Claix natively supports PDF (.pdf), Excel workbooks (.xlsx, .xls), Word documents (.docx, .doc), images (.png, .jpg, .jpeg, .webp), and plain text files (.txt, .html, .md). Each format is processed with visual document understanding to return typed, validated JSON conforming to your custom schema.

How do I convert Excel spreadsheets to JSON with the API?

To convert an Excel file, send a POST request to /api/excel-json with your file and target JSON schema. Claix interprets multi-sheet workbooks, merged headers, and relational tables, returning clean JSON ready for ingestion.

Can I convert PDFs, Word documents, and images to JSON?

Yes. Claix provides dedicated endpoints for each format: /api/pdf-json for complex or scanned PDFs, /api/doc-json for Word files, /api/img-json for images and receipts, and /api/audio-json for spoken audio (MP3, WAV, M4A, OGG). Every endpoint outputs valid JSON according to your schema.

Who is Claix built for?

Claix is designed for software developers, AI agent builders, SaaS engineering teams, and automation specialists using platforms like n8n or Make. It eliminates the need to build custom OCR, chunking, and vector retrieval pipelines.

What is the Claix pricing model?

Claix offers two native modes. With Claix Managed AI you pay per successful document (from €0.10 for images to €0.20 for audio) plus €0.03 per follow-up question, with 100 free successful processing runs on new accounts and no mandatory monthly subscription for standard extraction. With Bring Your Own Key (BYOK) there is no additional Claix document-processing fee: you connect your own OpenAI, Gemini, Claude, or Grok key and pay only that provider’s token usage while Claix still handles schemas, structured JSON, document context, and automation-ready responses.

Is document processing free with Bring Your Own Key (BYOK)?

Yes. BYOK is a native Claix option: connect your own supported AI provider API key, choose a compatible model, and process PDFs, Excel, Word, images, and text through Claix with no additional Claix processing fee. You remain responsible for your provider’s token charges. Your Claix API key still authenticates the workspace. Managed AI remains available when you prefer Claix-managed rates and defaults.

What is Source Tracing in Claix?

Source Tracing is optional field-level citation: each extracted value can include a source anchored to the document. When that check fails, source is requires_human_revision so a person can review the field. It reduces AI hallucination risk; it does not claim to eliminate it.

Are failed requests charged to my account?

No. Claix only charges for successful HTTP 200 processing requests that return valid extracted data. Failed API calls due to invalid parameters or system errors do not consume your quota or balance.

What is Claix Agent Mode?

Claix Agent Mode (/agent/*-json) is an extraction mode where an AI agent interprets ambiguous documents using natural language instructions instead of a rigid schema, allowing dynamic extraction based on context.

What is the difference between normal extraction and Agent Mode?

Normal extraction enforces strict, deterministic schema conformance for predictable pipelines. Agent Mode allows natural language reasoning over document contents, ideal for unstructured contracts and variable layouts.

How do I ask follow-up questions to a single document?

When you process a document with context enabled, Claix returns a document_id. You can send questions to POST /document-context/{document_id} to query that specific file without re-uploading or reprocessing.

What is the temporary context window?

The context window is a temporary retention layer that keeps a processed document queryable for follow-up questions without permanent storage, enabling multi-turn agent interactions before expiring automatically.

What are Knowledge Spaces, and how do I query multiple documents at once?

Knowledge Spaces allow you to group multiple persistent documents under a single space_id. By sending questions to POST /space-context/{space_id}, your backend, automation, or AI agent can query, compare, calculate totals, and cross-reference data across all active documents in that space simultaneously.

Can I white-label Claix or integrate it into automated workflows?

Yes. Claix is fully headless and integrates server-to-server via API keys, making it compatible with custom SaaS backends and automation platforms like n8n or Make.

Context Window

Query a persisted document

Endpoint

POSThttps://claix.dev/document-context/{document_id}

This endpoint answers questions about a document already extracted with window_context enabled. The document_id is in the URL (returned by the extraction call) and the questions go in a simple JSON body.

Public URL: POST https://claix.dev/document-context/{document_id}. Never expose the raw Supabase URL.

Designed for server-to-server integrations. Requires a secret API key.

1. Authentication

Every request must include your API key.

Option A — Dedicated header (recommended):

x-api-key: <YOUR_API_KEY>

Option B — Standard Authorization header:

Authorization: Bearer <YOUR_API_KEY>

The system checks that the key exists and is active, and that the account is not suspended. Failures return 401.

2. Request format

HTTP method: POST · Content-Type: application/json

document_id (UUID) is part of the path. The body has a single field:

Field	Type	Required	Description
questions	array of { question, format }	Yes	Typed questions answered from the persisted markdown only. Max 5. question: string ≤400 chars. format: string \| int \| boolean \| timestamp \| array.

{
  "questions": [
    { "question": "What is the exact penalty for early cancellation?", "format": "string" },
    { "question": "Which company is listed as the tenant, and what is its tax ID?", "format": "string" }
  ]
}

At least 1 question; at most 5.
Each item must include question (non-empty) and format as one of: string, int, boolean, timestamp, array.
Each ia_response item matches that type (or null if missing or not safely typed).
The document must belong to the API key account and must not have expired.

3. Step-by-step request

Extract a file with window_context: true and save the document_id from the response.
Obtain your API key.
POST to https://claix.dev/document-context/{document_id}.
Send { "questions": [{ "question": "...", "format": "string" }] } as JSON.
Check HTTP 200 and read ia_response.

4. Request examples

See the right-hand panel for cURL, JavaScript, Node.js, Python, PHP, and n8n examples.

5. Successful response

Status: 200 OK · Content-Type: application/json

{
  "user_ask": [
    { "question": "¿Cuál es la penalización exacta por cancelación anticipada?", "format": "string" },
    { "question": "¿Qué empresa figura como arrendataria y cuál es su CIF?", "format": "string" }
  ],
  "ia_response": [
    "El 15 % del importe restante del contrato.",
    "Inversiones Delta S.L., CIF B12345678"
  ],
  "log_id": "7c2e1a90-4b3d-4f8a-9e21-6d5c8b0a1f34"
}

Field	Type	Description
user_ask	array of { question, format }	The questions you sent (with their format), in the same order.
ia_response	typed array	Answers 1:1 with user_ask, typed by format (string, int, boolean, timestamp, array) or null. With source verification, each item is { value, source }.
log_id	string (UUID)	UUID of this call’s usage_logs row. Present on success and on most authenticated errors.

The response includes log_id when the usage_logs row could be stored.

If source verification is enabled on document queries, each ia_response item is { "value": ..., "source": "..." }. source quotes the phrases or snippets from the persisted plain-text content that support the answer. If there is no evidence, source is requires_human_revision.

Example with source verification enabled:

{
  "user_ask": [
    { "question": "¿Cuál es la penalización exacta por cancelación anticipada?", "format": "string" }
  ],
  "ia_response": [
    {
      "value": "El 15 % del importe restante del contrato.",
      "source": "penalización del 15 % del importe restante en caso de cancelación anticipada"
    }
  ],
  "log_id": "7c2e1a90-4b3d-4f8a-9e21-6d5c8b0a1f34"
}

6. Error codes

{
  "error": "Descripción legible del problema.",
  "detalle": "Información técnica adicional (solo presente en algunos casos).",
  "log_id": "7c2e1a90-4b3d-4f8a-9e21-6d5c8b0a1f34"
}

400 — Invalid document_id, malformed JSON, missing questions, empty array, more than 5 items, a question longer than 400 characters, or a missing/invalid format (string | int | boolean | timestamp | array).

401 — Missing, invalid, or inactive API key, or suspended account.

404 — Document does not exist, does not belong to the account, or has expired.

502 — AI service failure. 405 — Method other than POST. 500 — Unexpected server error.

7. Error code summary

Code	Category	Retry?
200	Success	—
400	Client error (malformed document or data)	No — fix the request first
401	Authentication error	No — fix credentials first
404	Resource not found	No — fix schema_id first
405	Incorrect HTTP method	No — fix the method first
413	File or extracted text too large	No — reduce size first
422	No extractable data	No — review document/schema first
500	Internal server error	Yes, with caution
502	AI service failure	Yes, recommended with backoff