DATA EXTRACTION SDK
Use Vision API in Python or Java to extract tables, key-value pairs, and handwriting into structured JSON on your infrastructure. Convert well-structured PDFs to Markdown, or use AI Document Processing for classification and template-based validation.
Every engine — including VLM — runs on your infrastructure. Connect a cloud provider only if you choose to. No data leaves your network unless you decide it should.
Describe the fields you need in plain language. The SDK extracts them from invoices, ID documents, forms, and receipts, and flags values that fail validation.
Vision API returns JSON with element coordinates, type classification, reading order, and confidence scores. Every element traces back to its source page and position.
PDFs, scanned images, Office files, CAD drawings, email, and 40+ camera RAW formats. Handles multicolumn layouts, mixed languages, handwriting, and skewed scans.
PDF TO MARKDOWN
For PDFs that already have embedded text and structure — reports, documentation, contracts — extract content as clean Markdown without AI models. The SDK reads the existing text layer; detects headings, paragraphs, tables, and lists; and outputs structured Markdown. No model downloads, no network access, no processing overhead. The fastest extraction option when your documents are already well-structured.
VISION API
Three extraction modes, one API — from fast character recognition to full layout analysis with vision language models. All modes can run on-premises. Output is structured JSON with element coordinates, reading order, and confidence scores.
Fast character recognition with word-level bounding boxes. Converts pixels to text without structural context. Best for searchable, selectable text from clean documents.
On-premises AI models for layout segmentation, table detection, handwriting, and equation recognition. Extracts tables with cell-level coordinates and resolves reading order. No network access required.
All three engines — OCR, ICR, and a vision language model — run in parallel on presegmented document regions. Handles degraded scans, complex handwriting, and unusual layouts. Run locally with Qwen, or connect Claude or OpenAI.
OCR contributes exact characters, ICR contributes spatial precision and bounding boxes, and the VLM contributes document understanding. The merged result is more accurate than any engine alone — no hallucinated text, no missing fields, no lost coordinates.
Nutrient's document-extraction engine comes in two deployments: the Vision API embedded in the Python and Java SDKs for self-hosted use, or the hosted cloud Data Extraction API. Same engine — choose the deployment that fits.
AI DOCUMENT PROCESSING
Define extraction fields in plain language — no regex, no rule engines. An LLM identifies document types, extracts key-value pairs, and runs each value through built-in validators (IBAN, VAT ID, postal address, and eight more). Ships with 10 preconfigured templates.
The LLM identifies document types — invoices, purchase orders, resumes, payroll statements — and routes them to the correct extraction template. No rule authoring required.
Invoice, passport, ID card, receipt, and six more templates ship ready to use. Build custom templates by describing fields in plain language — the LLM handles the rest.
Eleven validators check extracted values against known formats: IBAN, VAT ID, credit card number, postal address, email, phone number, and more. Failed checks set the field to VerificationNeeded.
Connect OpenAI or Azure OpenAI today, with more providers coming. Your API key, your infrastructure rules — documents are processed through the provider you configure.
DEMO
See how Nutrient compares to LLM-only extraction tools.
Vision API is available today in Python and Java SDKs, with .NET and DWS Processor API support coming soon. AI Document Processing is available today, with more platforms coming soon.
Use Nutrient Vision API in Python and Java to extract structured data from scanned documents. Execute table extraction, equation recognition, and layout analysis with local AI models.
The DOJ’s garbled PDF release exposed a longstanding truth: Extracting structured data from documents remains an unsolved problem. Here’s why — and how Nutrient Vision API tackles it with on-premises intelligence.
Traditional OCR extracts text without context. Nutrient Vision API’s intelligent content recognition analyzes document structure — including tables, equations, handwriting, and reading order — using local AI models with optional cloud enhancement for complex layouts.
Discover XtractFlow, the generative AI solution that simplifies document processing and boosts accuracy in extracting data from various document formats.
FREE TRIAL
Try Vision API in Python or Java, or get started with AI Document Processing — no payment information required.
Nutrient offers three approaches. PDF to Markdown converts well-structured, digitally born PDFs into clean Markdown — no AI models, no network access, and the fastest option. Vision API extracts structured JSON with element coordinates, reading order, and classification using OCR, ICR, or VLM-enhanced mode — use it when you need spatial precision or need to handle scanned documents, handwriting, and complex layouts. AI Document Processing sits a level above — it uses an LLM to classify documents, extract key-value pairs via templates, and validate results. Use it for end-to-end workflows like invoice processing or ID verification.
Yes. Vision API supports more than 100 file types, including scanned PDFs, 50+ image formats (TIFF, JPEG, PNG, DICOM, HEIF, and raw camera formats), Microsoft Office documents, and CAD files. ICR mode uses on-premises AI models for layout detection and handwriting recognition without sending data to any external service.
Vision API is available today in the Python SDK (3.8+) and Java SDK (8+), with .NET and DWS Processor API support coming soon. AI Document Processing is available today, with cross-platform support coming soon.
PDF to Markdown, OCR, and ICR run fully on-premises — no network access required. VLM-enhanced mode can also run on-premises with a self-hosted model like Qwen, or you can connect a cloud provider like Claude or OpenAI. AI Document Processing requires an LLM provider (OpenAI or Azure OpenAI). In every configuration, you decide what leaves your infrastructure.
ICR mode detects layout regions (headers, paragraphs, tables, and figures) and extracts tables with cell-level bounding-box coordinates. It preserves reading order across multicolumn layouts and identifies hierarchical relationships between document elements. In VLM-enhanced mode, all three engines run in parallel — the merged output catches merged cells, footnotes, and edge cases that ICR alone can miss.
Ten templates ship out of the box: bank details, driver’s license, ID card, invoice (15 fields), passport, payment card, payroll statement, purchase order, receipt, and resume. Each template defines expected fields with data types. You can extend any template with custom fields or build new templates from scratch using natural language field descriptions.
Structured JSON. Each document element (text block, table, figure, and heading) includes bounding-box coordinates, reading order index, element type, and confidence scores. The format is designed for direct database ingestion, visual review UIs, and audit trails.
Yes. ICR handles non-Latin scripts and mixed-language layouts. VLM-enhanced mode is strongest here — the vision language model adds context that pure layout analysis misses. AI Document Processing inherits the language capabilities of your LLM provider (OpenAI, Azure OpenAI).
AI Document Processing includes 11 built-in validators: IBAN integrity, credit card number, VAT ID, postal address, email, URI, phone number, vehicle identification number, currency, date, and number formats. When a validator flags a value, the field’s validation state is set to VerificationNeeded, indicating it requires human review. You can combine multiple validators per field.
