Claix is a B2B AI agent context infrastructure API that converts PDFs, Excel/CSV, Word/text documents and images into strictly typed JSON defined by your schema—also integrable in backend systems and automation. Official site: https://www.claix.dev/en

What file formats does the Claix API support?

Claix supports Excel (.xlsx) and CSV, JSON to Excel export, PDF (text or scanned), .docx/.txt/.md/.rtf documents, .jpeg/.jpg/.png/.webp/.heic/.heif images, and plain text/HTML/XML via a content field. Each format uses a dedicated endpoint and schema type.

How do I convert a PDF to JSON with Claix?

Create a pdf-json schema, obtain an API key, and send a multipart POST to https://www.claix.dev/api/pdf-json with file and schema_id fields and the x-api-key header. Documentation: https://www.claix.dev/en/documentation/pdf-to-json

What is Claix pricing?

Pay-as-you-go. The first 15 successful calls (HTTP 200) are free. Excel↔JSON is billed by variable volume (€0.25–€1.00). PDF→JSON €0.35, Doc→JSON €0.20, Img→JSON €0.10, and Txt/HTML/XML→JSON €0.10 per successful request. 4xx/5xx errors are not billed.

Does Claix offer an embeddable widget?

Yes. Claix provides a free unlimited iframe widget (https://www.claix.dev/widget/{id}), customizable and production-ready. JSON is delivered to the owner's HTTPS webhook; the API key is never exposed in the browser.

Where is the OpenAPI specification?

The OpenAPI 3 spec is at https://www.claix.dev/openapi.yaml. AI context summary: https://www.claix.dev/llms.txt and full knowledge base: https://www.claix.dev/llms-full.txt

Is Claix compatible with n8n and Make?

Yes. Use generic HTTP multipart or the n8n-nodes-claix community node. Guide: https://www.claix.dev/en/blog/integrar-claix-en-n8n

Is Claix GDPR compliant?

Claix offers EU-oriented processing, a public DPA at https://www.claix.dev/en/dpa, zero file retention for model training, and no training on customer documents.

Txt-to-JSON · Agent mode

Txt / HTML / XML to JSON with Agent mode

Endpoint

POSThttps://www.claix.dev/agent/txt-json

Agent mode active

This endpoint runs structured extraction from the main schema first, then a reasoning phase with agent_definition. The response includes data[] (extraction) and agent_data (typed inference). The schema must have is_agent_mode enabled.

This endpoint receives a content field with already processed plain text, HTML, or XML and returns a single JSON object matching a txt-json schema.

Unlike doc-json, no file is uploaded: the payload is the content itself in a multipart form. Auth, schema checks, usage logs, and optional context window behavior match the other child functions.

Public URLs (Claix domain): extraction at POST https://www.claix.dev/api/txt-json; Agent mode at POST https://www.claix.dev/agent/txt-json. Never expose the raw Supabase URL to end clients.

Designed for server-to-server integrations. Do not call it from an end-user browser: it 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>

If both are sent, x-api-key takes priority.

Before processing content, the system validates the API key and account status. Failures return 401.

2. Request format

HTTP method: POST · Content-Type: multipart/form-data (required)

Field	Type	Required	Description
content	Text	Yes	The text, HTML, or XML to transform. Not a file upload: the payload itself as a form text part.
schema_id	Text (UUID)	Yes	ID of a txt-json schema previously created on your account.

Field names must be exactly content and schema_id.

Schema requirement

schema_id must reference a txt-json schema. Other schema types return 400.

Supported content types in content

Type	Example use cases	Notes
Plain text	Raw emails, logs, pasted contracts, textual CSV, unrendered Markdown	Analyzed as-is; Markdown syntax is not interpreted.
HTML	Web pages, DOM fragments, HTML emails, rendered invoices	The model reads tags and visible text; JavaScript is not executed.
XML	RSS/Atom feeds, SOAP, e-invoices, legacy API responses	Node structure is used to locate fields.

Content requirements

Content cannot be empty (whitespace only).
Max 300,000 characters. Larger payloads return 413 before calling the model.
As a fallback, content may also be sent as a text File, but a string form field is the usual pattern.

3. Step-by-step request

Obtain your API key.
Create a txt-json schema and copy its schema_id.
POST to https://www.claix.dev/agent/txt-json.
Send auth via x-api-key or Authorization: Bearer.
Build multipart/form-data with content and schema_id.
Verify HTTP 200 before treating the call as successful.

4. Request examples

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

5. Successful response

200 OK · Content-Type: application/json

{
  "success": true,
  "schema_utilizado": "Contratos legales",
  "total_registros": 1,
  "data": [
    {
      "parte_a": "Inmobiliaria Norte S.L.",
      "parte_b": "Carlos Méndez",
      "fecha_firma": "2026-03-01"
    }
  ],
  "agent_data": {
    "clausula_penalizacion": true,
    "tipo_renovacion": "automatica",
    "resumen_contrato": "Arrendamiento con renovación automática y cláusula de penalización por impago."
  }
}

Field	Type	Description
success	boolean	Always true when HTTP is 200.
schema_utilizado	string	Name of the schema used for extraction.
total_registros	number	Number of records in data.
data	array	Objects extracted from the main schema (same as extraction mode).
agent_data	object	Typed Agent Mode answers per agent_definition (booleans, numbers, strings).

6. Error codes

{
  "error": "Descripción legible del problema.",
  "detalle": "Información técnica adicional (solo presente en algunos casos)."
}

400 — Missing content or schema_id, body is not multipart, empty content, or schema is not type txt-json.

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

404 — schema_id does not exist or does not belong to the account.

413 — Content exceeds 300,000 characters.

422 — No data matching the schema could be extracted.

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

7. Error code summary

Código	Categoría	¿Reintentar?
200	Éxito	—
400	Error del cliente (documento o datos mal formados)	No, corrige la petición primero
401	Error de autenticación	No, corrige las credenciales primero
404	Recurso no encontrado	No, corrige el schema_id primero
405	Método HTTP incorrecto	No, corrige el método primero
413	Archivo o texto extraído demasiado grande	No, reduce el tamaño primero
422	Sin datos extraíbles	No, revisa el documento/schema primero
500	Error interno del servidor	Sí, con precaución
502	Fallo del servicio de IA	Sí, recomendado con backoff