Zerodoc vs Mindee
Mindee is a capable, mature document-AI platform and the closest peer to Zerodoc — a developer-first API with an EU base. The differences that matter are structural: what happens to your documents, what privacy costs, and how billing works. Here is the factual comparison, with sources.
Figures verified July 2026 · sources linked below
What your money buys each month
Included pages per month on the free and entry plans. Mindee credits ≈ pages for standard extraction.
Mindee figures from mindee.com/pricing and docs.mindee.com as of July 2026: Starter is €44/mo on annual billing (monthly billing ~10% more) with a 6,000 credits/year minimum, shown here as its monthly equivalent. Per their credit-cost docs, 1 credit ≈ 1 page for standard extraction, but some models cost more (or less) per page. Their plan lineup changed recently — always verify against the current pricing page.
Pricing, line by line
| Zerodoc | Mindee (July 2026) | |
|---|---|---|
| Permanent free tier | 200 pages every month — no card, no expiry | None — 14-day / 200-credit trial, then a paid plan |
| Entry plan | £19/mo — 2,000 pages | €44/mo (annual billing) — 6,000 credits/year, ≈500/mo (Starter) |
| Mid tier | £89/mo — 10,000 pages (Pro) | €116/mo (annual billing) — Pro is a feature tier (EU localization, multi-user); credit volume is bought separately |
| High tier | £299/mo — 40,000 pages (Business) | Enterprise — custom pricing, 500,000+ credits/year minimum |
| Overage / extra pages | £0.025/page, flat on every plan | €0.044/credit, flat |
| Billing unit | Pages. One number, no multipliers | Credits — some models/options cost more (or less) than 1 credit/page |
What happens to a document after the response
The structural difference in one picture: their zero-retention is a policy you configure on higher tiers; ours is the absence of any storage path, on every plan.
Schematic — not to scale (seconds and hours can’t share an axis). Mindee retention behaviour per their data-processing documentation and DPA as of July 2026 — their docs state the original uploaded file is never written to disk, and a “delete when fetched” toggle can shorten the window. See how Zerodoc’s guarantee is enforced.
| Zerodoc | Mindee (July 2026) | |
|---|---|---|
| Document retention | None — processed in memory, buffer zeroed on response. No storage code path exists | Extracted data stored 12 hours by default (configurable 1–24h); their DPA permits up to 7 days for async jobs |
| Zero-retention as default | Yes — it is the only mode, on every plan | No — "delete when fetched" is an opt-in toggle, disabled by default |
| EU data residency | Every plan, including free | Localization is a Pro-tier (€116/mo) feature; the default zone is "No Preference" — EU or US |
| Third-party LLM in the pipeline | No — local OCR + deterministic rules only | Yes — LLM-based processing (docTI) is core to the product |
| Machine-readable proof | Every response carries retention: { stored: false } | Policy-based; no per-response retention attestation |
| Confidence scores | Every plan, every field, always on | All plans — but opt-in per model/call, null unless activated, and may cost extra credits |
| Your data & their R&D | Nothing is retained, so there is nothing to reuse | Shared models are not trained on your data; their DPA permits pseudonymized reuse for R&D by default |
The honest summary: choose Mindee if you need many document types, custom-trained models, or platform features like RAG today. Choose Zerodoc if your documents are sensitive enough that “stored for hours by default” is a problem, if you want processing that is EU-only on every plan rather than a Pro-tier setting, or if a €44/month floor for ~500 pages prices out your project. We do UK/EU invoices, excellently and privately — that focus is the product.
Migrating from Mindee
Both APIs take a document and return structured JSON, so a swap is mostly renaming fields. Send your file to /v1/extract:
# One endpoint, one header — no SDK required.
curl -X POST https://api.zerodoc.io/v1/extract \
-H "X-API-Key: zk_your_api_key" \
-F "file=@invoice.pdf;type=application/pdf"Then map the invoice fields (indicative — check both docs for your exact model version):
| Mindee invoice prediction | Zerodoc response |
|---|---|
| supplier_name | fields.supplier |
| invoice_number | fields.invoice_number |
| date | fields.invoice_date |
| due_date | fields.due_date |
| total_net | fields.net_amount |
| total_tax | fields.vat_amount |
| taxes[].rate | fields.vat_rate |
| total_amount | fields.total_amount |
| supplier_company_registrations (VAT) | fields.vat_number |
| supplier_payment_details.iban | fields.iban |
| locale.currency | fields.locale.currency |
Every Zerodoc field returns { value, confidence } — full response shape in the API reference.
Which one is right for you?
Choose Mindee if…
- You need many document types today — receipts, IDs, passports, custom models
- You want platform features: classification chaining, RAG, a large SDK surface
- Procurement requires SOC 2 Type II right now
Choose Zerodoc if…
- Extracted data being stored for hours by default is a problem for you
- You want guaranteed EU processing on every plan — not a Pro-tier setting with a "No Preference" default
- A €44/month floor for ~500 pages/month prices out your project
- You process UK/EU invoices and want depth, not breadth
Mindee is a trademark of its owner. Zerodoc is not affiliated with or endorsed by Mindee. Comparison compiled July 2026 from public materials; if anything here is out of date, tell us at support@zerodoc.io and we’ll correct it.
Try it on your own invoices
200 pages free every month — no card, no trial expiry. Nothing you upload is ever stored.
Start for free