Niches · Document parsing & extraction

Pull named fields from invoices, receipts, forms and CVs

Four or more companies' docs show a full fit.

5companies, full fit
12companies, fit with a limit
36companies carry the tag
16share of the category's work
10first-hand accounts

What counts as done

JSON matching the given schema or the documented prebuilt field list, with line items as arrays, numbers as numbers, a confidence per field and nulls where a field is absent, from one call or one async job.

Measured, for our own tests: field-level accuracy on a fixed set of invoices and receipts. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: get the total, VAT and supplier from this invoice, extract line items from these receipts, fill this JSON schema from the document, parse this CV into fields

Does the job 5

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Azure Document Intelligence B
Microsoft Corporation
Prebuilt invoice, receipt, ID, contract and US tax models return documented fields with confidence; there is no JSON schema input, but the success criterion allows a prebuilt field list. acc-12 reports it working for a year after tuning. source
Extend API + MCP B
CrowdView Inc. dba Extend
Extract fills a JSON schema and returns output.value shaped like the schema with per-field ocrConfidence, logprobsConfidence and citations; sync or async runs. source
Google Cloud Document AI BB
Google LLC
Invoice, expense, identity, W2 and other prebuilt processors return typed entities with confidence, normalizedValue and properties for line items, and a Custom Extractor takes a schema (English only for generative extraction). source
LlamaParse API + MCP B
LlamaIndex, Inc.
Extract takes a JSON Schema or Pydantic model up to 3,200 fields, supports nullable fields and arrays, and returns confidence scores and citations when confidence_scores and cite_sources are set. source
Nanonets API + MCP E
Nano Net Technologies Inc.
json_options takes a JSON schema or field list, field specs type string, number, boolean, date or array, and metadata returns per-field confidence plus an overall score penalised for truncation. source

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Textract BB
Amazon Web Services, Inc.
AnalyzeExpense returns invoice and receipt fields and line items with Confidence, and AnalyzeID reads US identity documents, but there is no JSON schema input, AnalyzeExpense is English only, and IDs are US only. source
Clairic BB
Cloudflare, Inc.
Typed fields come back with numbers as numbers, confidence, p_null and null when absent, but list items can only be text, number or date, so line items as records are not possible; inputs are text or four images, and the model is a preview. source
Datalab B
Endless Labs, Inc.
page_schema takes a JSON schema with numbers and arrays, up to 750 fields, and returns per-field citations and verification status, but no numeric confidence per field is documented and there are no prebuilt models. source
Docling B
Docling Project (LF AI & Data Foundation)
Information extraction takes a string, dict or Pydantic template and fills it with a VLM, but there are no prebuilt models and no per-field confidence; confidence is graded per page. source
Invofox D
Invofox, Inc. (Delaware), with a registered branch in Spain
Typed JSON for invoices, receipts, payslips, ID documents and custom types, with per-field ERR_LOW_CONFIDENCE errors, but confidence is high, medium or low per document, types are set up in the web app rather than passed as a schema, and languages are Latin-script. source
LandingAI Agentic Document Extraction BB
LandingAI, Inc.
Extract fills a JSON schema, returns null for absent values and flags partial results with warnings, schema_violation_error and HTTP 206, but no per-field confidence is returned and there are no prebuilt models. source
Mindee API C
Mindee SAS (Mindee Inc. outside the Eurozone)
Templates for invoice, receipt, resume, payslip and IDs return typed fields with list fields and Certain, High, Medium or Low confidence, but every model must be created in the web platform first, and acc-46 saw new None values crash the Python client. source
Mistral OCR API B
Mistral AI (RCS Paris 952 418 325)
Document annotations fill a JSON schema at $5 per 1,000 pages, but acc-38 saw the model loop on number fields and truncate the JSON, and no per-field confidence is returned. source
Reducto API + MCP B
Reducto, Inc.
Extract fills a JSON schema with a documented list of guaranteed keywords and returns citations and usage, but per-field confidence is not shown in the extract response format read, and there are no prebuilt models. source
Unstructured API + MCP E
Unstructured Technologies, Inc.
Extract takes a JSON Schema and returns data in its shape, nulls included, with optional citation metadata, but no per-field confidence; the docs warn not to read missing evidence as confidence. source
Veryfi API + MCP C
Veryfi, Inc.
process_document returns receipt and invoice fields with line_items, and dedicated calls cover W-2, W-8, W-9 and cheques, but per-field confidence and supported countries could not be read, and acc-42 found the MCP server failing until token construction was fixed. source
Xiaomi-OCR-0 C
Xiaomi Corporation
Key information extraction takes a JSON schema and returns a JSON object, but the schema is a template of empty strings with no numeric types documented, and there is no confidence or null signal. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Adobe PDF Services / PDF Extract API C
Adobe Inc.
No schema parameter and no prebuilt invoice, receipt or CV model in the API; Extract returns layout elements only. source
Nemotron 3.5 Parse B
NVIDIA Corporation
A layout parser with no schema or field extraction mode. source
OpenDocRouter B
LlamaIndex, Inc.
Parse only; no schema or field extraction endpoint. source

6 listings in the category were added after this reading and aren't marked yet.

What stops agents finishing

  • strict schema output loops or truncates on number fields
  • client library breaks on a response change and stops the pipeline
  • prebuilt models only for US documents or English

Around it

Before: mailbox-access.find-and-read, file-storage.agent-upload. After: accounting.capture-bill, crm.upsert-contact, human-in-the-loop.review-output.

Where this comes from

Weight 16 of 100 in Document parsing & extraction: 10 of 46 accounts; invoice and receipt pipelines on Hacker News plus Mistral, Mindee, Veryfi and Docling issues

The same as data: /api/v1/use-cases/document-extraction.fields-from-business-docs.json, or the MCP tool get_use_case with id document-extraction.fields-from-business-docs. Other jobs in this category: /api/v1/niches?category=document-extraction.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.