Claix is an AI document intelligence API that converts unstructured files into schema-based JSON and provides queryable document context for AI agents. It processes PDFs, Excel spreadsheets, Word documents, images, and text using multimodal vision models, allowing developers to extract structured data and query documents on demand.

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, and /api/img-json for images and receipts. Every endpoint uses visual intelligence to interpret layout structures and output valid JSON.

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 operates on a pay-per-use model per processed document (from 0.10 € for images to 0.15 € for complex PDFs) and 0.03 € per follow-up question. There are no mandatory monthly subscriptions for standard extraction, and new accounts include 100 free successful processing runs.

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 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 · Delete space

Delete a knowledge space

Endpoint

DELETEhttps://claix.dev/delete-space/{space_id}

Deletes a knowledge space by space_id. It accepts no body and no query parameters — the identifier is only in the URL path.

The delete only affects a space owned by the same account as the API key. If the UUID does not exist or belongs to someone else, the API returns 404 with the same generic message (the exact reason is not exposed).

Public URL: DELETE https://claix.dev/delete-space/{space_id}

The operation is irreversible. This call is free: it is not billed and does not consume extraction or context-window quota.

1. Authentication

Every request must include your API key. It is a personal server-side credential, different from any user session token.

Option A — Dedicated header (recommended):

x-api-key: <YOUR_API_KEY>

Option B — Standard Authorization header:

Authorization: Bearer <YOUR_API_KEY>

Either one is enough. If you send both, x-api-key wins.

Claix checks that the key exists and is active, and that the account is not suspended. Otherwise it returns 401.

2. Request format

Method: DELETE · Body: not required · Query params: none

Parameter	Location	Required	Description
space_id	URL path	Yes	UUID of the space returned by POST /create-space.

Expected URL format: /delete-space/{space_id}

3. Building the call

Get the space_id from the original create call or from your own store.
Replace {space_id} in the URL with that UUID.
Send DELETE with your API key in x-api-key (no body).

4. Request examples

Use the code panel on the right to copy examples in cURL, JavaScript, Python, and more.

5. Success response format

HTTP 200 — The space was deleted. The response only includes the deleted space_id; there is no success field. If the delete was not possible, the request ends in 404 before a success response is built.

{
  "space_id": "5b9e2c14-7d3a-4f8b-9e1c-6a0d4b8f2e7c"
}

6. Error codes

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

400 — Missing space_id in the URL, or it is not a valid UUID.

401 — Authentication failed: key missing, unknown, disabled, or account not active.

404 — The space does not exist, belongs to another account, or was already deleted. Same generic message for security.

404 example:

{
  "error": "No existe ningún espacio de conocimiento con id '5b9e2c14-7d3a-4f8b-9e1c-6a0d4b8f2e7c'."
}

405 — Method other than DELETE. · 500 — Internal error.

7. Code summary

Code	Category	Retry?
200	Success — space deleted	—
400	Client error (space_id missing or malformed)	No — fix the request first
401	Authentication error	No — fix credentials first
404	Space not found, foreign, or already deleted	No — fix the space_id first
405	Incorrect HTTP method	No — use DELETE
500	Internal server error	Yes, with caution

8. Best practices

Always use the public claix.dev domain, not the direct Supabase URL.
Delete the space when the case or client no longer needs cross-document queries. Documents that were grouped still exist on their own: this endpoint does not delete them.
After deletion, POST /space-context/{space_id} will return 404.
Never ship your API key in frontend code or public repositories.