Head to head · Document extraction · October 2026 research run
Clairic vs Invofox
Clairic scores 66.3 (B) on agent readiness against Invofox's 46.8 (D), and leads in every scored category. Both do document extraction.
Best document parsing, OCR and extraction APIs for AI agents · All 142 documents comparisons
Which one, for what
Clairic B
Best for Typed fields, estimates and next-step forecasts from emails, invoices, receipts and other text or images inside Cloudflare, each with a null probability and confidence.
Ahead on
- Reliability, 51 against 30
- Schema & documentation, 85 against 70
- Agent ergonomics, 78 against 64
- Security & auth, 72 against 45
- Payments & pricing, 40 against 30
- Maintenance & community, 57 against 30
- Transparency & trust, 80 against 55
Watch for
Preview only. Cloudflare calls the endpoint an early checkpoint and expects to replace it under the unversioned ID @cf/cloudflare/clairic
Invofox D
Best for Teams that process a known set of business documents (invoices, payslips, bank statements, mortgage forms) at volume and can receive webhooks.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one
Score by category
| Category | Weight this run | Clairic | Invofox | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 51 | 30 | Clairic +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 70 | Clairic +15 |
| Agent ergonomics | 13%16.2 | 78 | 64 | Clairic +14 |
| Security & auth | 14%17.5 | 72 | 45 | Clairic +27 |
| Payments & pricing | 10%12.5 | 40 | 30 | Clairic +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 57 | 30 | Clairic +27 |
| Transparency & trust | 7%8.8 | 80 | 55 | Clairic +25 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 66.3/100 | D 46.8/100 |
Facts side by side
| Fact | Clairic | Invofox |
|---|---|---|
| Kind | Model API | HTTP API |
| Vendor | Cloudflare | Invofox, Inc. |
| Hosted endpoint | https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clairic | https://api.invofox.com |
| Transports | HTTP | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted preview under Cloudflare's Self-Serve Subscription Agreement and the model page's own terms. Cloudflare says open weights will follow soon, with no date or licence named | Proprietary hosted service. The n8n community node on GitHub is MIT |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-05 |
| Terms last updated | 2025-09-12 | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | 3.3/5 (4) | 3.3/5 (4) |
Verdicts
Clairic
Clairic's price is public at $0.10 per million input tokens with no output charge, and its docs publish JSON Schemas, limitations and when to use a decision model instead. It is a preview that Cloudflare calls an early checkpoint, served under an unversioned ID with no SLA, and its promised open weights have no date or licence.
Invofox
Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise.
Before you call either
Clairic
- Send
modelasclairicin the body as well as in the URL. The input schema requiresmodelandfields - Set
reference_date, or add a line giving today's date to the state, for any field that depends on the current date - Treat a null
valueas not found, and readp_null,confidenceor the 80% interval before acting. Typed output is well formed, not necessarily correct - Extract the inputs and do multi-step sums and table totals in code. Cloudflare says long arithmetic chains aren't reliable yet
- Embed images as data URLs or base64 objects, at most four, 4 MiB each and 8 MiB in all. Remote image URLs are refused
- Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
Invofox
- Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types
- Upload with POST /v1/ingest/uploads as multipart, with
infoas a JSON string. Send"useClassifier": truein place oftypeto have the type detected - Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded
- Handle the
file.rejectedwebhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely - Do not retry an upload blindly. There is no idempotency key, so send your own id in
clientDataand look it up withfilterfirst
Questions
Which is better for AI agents, Clairic or Invofox?
Clairic scores 66.3 (B) on agent readiness against Invofox's 46.8 (D), and leads in every scored category.
Do Clairic and Invofox need an API key?
Both need an API key.
Can an agent call Clairic and Invofox without installing anything?
Yes. Clairic has a hosted endpoint at https://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clairic and Invofox at https://api.invofox.com.
Other comparisons with Clairic or Invofox
- Adobe PDF Services / PDF Extract API vs Clairic
- Adobe PDF Services / PDF Extract API vs Invofox
- Amazon Textract vs Clairic
- Amazon Textract vs Invofox
- Azure Document Intelligence vs Clairic
- Azure Document Intelligence vs Invofox
- Clairic vs Extend API + MCP
- Clairic vs Google Cloud Document AI
- Clairic vs LandingAI Agentic Document Extraction
- Clairic vs LlamaParse API + MCP
- Clairic vs Mindee API
- Clairic vs Mistral OCR API
- Clairic vs Nanonets API + MCP
- Clairic vs Reducto API + MCP
- Clairic vs Unstructured API + MCP
- Clairic vs Veryfi API + MCP
- Extend API + MCP vs Invofox
- Google Cloud Document AI vs Invofox
- Invofox vs LandingAI Agentic Document Extraction
- Invofox vs LlamaParse API + MCP
- Invofox vs Mindee API
- Invofox vs Mistral OCR API
- Invofox vs Nanonets API + MCP
- Invofox vs Reducto API + MCP
- Invofox vs Unstructured API + MCP
- Invofox vs Veryfi API + MCP
- Invofox vs OpenDocRouter
Machine-readable
- This page as Markdown
/compare/cloudflare-clairic-vs-invofox.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-clairic.json·/api/v1/tools/invofox.json - From a terminal
anchor compare cloudflare-clairic invofox(the CLI) - Over MCP
compare_tools {"a": "cloudflare-clairic", "b": "invofox"}at/mcp, no key