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

Ask across several documents

Endpoint

POSThttps://claix.dev/multi-document

Send up to 10 files in one call, together with the same typed questions used by Query space. Each file is converted to Markdown and the answers are built by crossing those texts. There is no schema_id and the files do not need to be stored beforehand.

The accepted formats are the same as Extraction → Markdown: PDF, Excel/CSV, Word and text, HTML/XML, images and audio.

Public URL: POST https://claix.dev/multi-document. Never expose the direct Supabase URL.

1. Authentication

Same API key check as Query document and Query space. The key must exist and be active, and the account must be active.

x-api-key: <TU_API_KEY>

Or:

Authorization: Bearer <TU_API_KEY>

2. Parameters

Method: POST · Content-Type: multipart/form-data

Field	Required	Description
file	Yes	Repeat the field from 1 to 10 times. files and documents are also accepted. Same formats and size limits as Extraction → Markdown.
questions	Yes	JSON array of { question, format }. Maximum 5 questions, 400 characters each. format: string \| int \| boolean \| timestamp \| array.
window_context	No	true keeps each converted document. Omit it or send false to only answer the questions.
window_time	Required if window_context is true	Minutes: 5, 10, 15, 30, 45, 60, 90, 120, 180, 240, 360, 480, 720, 1440, or infinity. infinity requires Persistent Mode on the account.
space_id	No	Knowledge space owned by the API key. Only when window_context is true. The kept documents are attached to that space.

3. Response

Same shape as Query space, plus documents_processed. Answers stay aligned with the questions and use the requested format, or null when the data is not in the files. If source verification is enabled for knowledge-space queries, each answer is { value, source }.

{
  "user_ask": [
    { "question": "¿Qué proveedor factura más en total?", "format": "string" }
  ],
  "ia_response": ["Suministros Omega S.A."],
  "documents_processed": 2,
  "log_id": "LOG_UUID"
}

log_id identifies the call in the logs panel.

4. Status codes

Code	When
200	Questions answered.
400	Missing questions or files, more than 10 files, unsupported format, invalid window_time, space_id without window_context, or infinity without Persistent Mode.
401	API key missing, invalid, inactive, or account not active.
404	space_id does not exist for this account.
405	Method other than POST.
413	A file is over the limit of its format.
422	A file could not be turned into readable Markdown.
502	The model call failed.