Integrate today,scale to millions

Document queries

Ask questions about your documentsClaix connects the data

Claix turns PDFs, Excel files, and images into document context for agents—accessible via REST, A2A (Agent-to-Agent), or MCP. Query a single file by document_id, or group them under a space_id to compare, sum, and connect information across multiple documents at once.

Invoice

1.Is there a late payment surcharge on this invoice and how much is it?
2.What is the total invoice amount and how is it composed?
3.What is the payment status and due date?

invoice_2026_0841.pdf

INVOICE

No. ····

ItemAmount
agent_data.jsonagent_data
Analyzing…
Data queriesCross-document or single-document queryPermanent, temporary, or no document storage. YOU CHOOSE

Capabilities

Invisible infrastructure. Structured outcomes.

Integration and Deployment

  • Invisible to end users

    Your customer sees your brand, logo, and product. Claix never appears in the UI. Behind the scenes, our intelligent AI mapping engine does the heavy lifting.

  • API-first by design

    REST for backends, A2A (Agent-to-Agent) for autonomous agent orchestration, and MCP for IDEs. No mandatory SDKs—integrate into your agent stack, CRM, ERP, or automation via HTTP, JSON-RPC, or MCP tools.

  • MCP server for agents and IDEs

    Connect Claix to Cursor, Claude Desktop, or Windsurf in one click. Let your AI agents process PDFs and spreadsheets automatically via our MCP protocol.

    View MCP documentation →MCP article →
  • A2A agent (Agent-to-Agent)

    Claix is a native A2A agent: other autonomous agents discover it via Agent Card, invoke 20+ extraction and document-query skills over JSON-RPC—without rewriting REST or tying you to an IDE.

    View A2A documentation →A2A article →

Infrastructure and Compliance

  • Secure infrastructure in Stockholm

    Data hosted in the EU, with encryption in transit and at rest, API Key authentication and multi-tenant isolation.

  • Zero maintenance for you

    We manage the AI engine, semantic mapping, and scaling. You focus on selling your product—not maintaining data pipelines.

  • Full privacy control. Zero AI training.

    You decide how much we remember. Neither Claix nor our providers use your confidential documents to train models. Keep absolute control over your data by choosing instant deletion (total destruction after processing), temporary mode (memory retained per session), or persistent mode (encrypted context exclusive to your organization).

  • Clean ID-based architecture

    Drop spaghetti code and unstable prompts. Create and manage extraction structures via API, all centralized under a unique identifier (schema_id). Your database and business logic stay clean.

    See schema management →

Flow architecture · Agent & REST Ready

From integration to production with agents in 5 steps

A frictionless pipeline designed for AI agents and backend systems. Ingest heterogeneous documents, delegate document context to Claix via REST or the A2A protocol, and operate with typed data and multi-file queries.

  1. Step 01 · Onboarding and instant API Key

    Frictionless onboarding

    Free signup with 100 successful processing calls included. Generate your server API key in seconds and start integrating—no credit card and no OCR or embeddings infrastructure to deploy.

  2. Step 02 · REST connection or A2A protocol

    REST integration and A2A protocol

    Inject HTTP endpoints into your microservices, n8n, or Make with standard headers (x-api-key). In multi-agent architectures, interact natively through the Agent-to-Agent (A2A) protocol with Agent Card discovery and task delegation.

  3. Step 03 · Deterministic extraction against schema

    Typed extraction against schema

    Claix processes scanned PDFs, Excel workbooks, Word files, or images with multimodal vision. Data is transformed deterministically into the requested JSON Schema, assigning programmatic null to fields without documentary evidence to eradicate hallucinations.

  4. Step 04 · Document memory and Knowledge Spaces

    Persistence and Knowledge Spaces

    Associate processed documents with a shared space_id. Your agent can query individual files by document_id or run cross-document queries across the whole space to compare, sum, and reconcile data across multiple files in a single call.

  5. Step 05 · Multi-agent scaling without tech debt

    Scaling and multi-tenant isolation

    Strict logical isolation by space and account to guarantee privacy and GDPR compliance. Cut prompt token consumption by more than 80%, drop fragile RAG pipeline maintenance, and ship agents to production faster.

Pricing

Pay-per-success. You only pay for what works.

200 OK → charged401 / 403 → free400 / 422 → free5xx → free

100 successful calls free — plenty of room to integrate Claix into your stack without spending a cent.

Free with your own AI key (BYOK): no additional Claix processing fee. You only pay your provider’s tokens.

Semantic normalization of spreadsheets and CSV into typed JSON schemas, with a flat per-document rate.

Free with your own AI key (BYOK): no additional Claix processing fee. You only pay your provider’s tokens.

Excel → JSON

Flat rate per successfully processed document (Claix Managed AI)

Tier€ / call
First 100 successful€0.00
From the 101th onward — any size or page count€0.15

Deploy now

Typed data for systems and AI agents.

FAQ

What is Claix?

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. Claix is also a native Agent-to-Agent (A2A) agent and MCP server: other AI agents can call it directly via the A2A protocol (POST /a2a, Agent Card at /.well-known/agent.json) or connect from IDEs and tool frameworks via MCP.

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, 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 offers two native modes. With Claix Managed AI you pay per successful document (from €0.10 for images to €0.15 for complex PDFs) 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.

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.