Mindee
Mindee is a document parsing and intelligent document processing platform. Its REST API (api-v2.mindee.net) provides asynchronous inference across five model families — Extraction, Classification, Crop, OCR, and Split — plus a unified Jobs endpoint for polling. Mindee ships prebuilt models for invoices, receipts, passports, IDs, resumes, bank statements, and barcodes, along with customer-configurable extraction models with their own Data Schemas. Native SDKs cover Python, Node.js, Java, PHP, Ruby, and .NET, and front-end vision SDKs cover React and Vue. Mindee also stewards the open-source docTR OCR library.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Mindee the way a machine reads it — 61 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mindee scores 64.5/100 (strong), with a separate agent-readiness read of 62/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Mindee
Each block below is one kind of artifact we hold for Mindee. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Mindee Extraction API
Extract structured fields from invoices, receipts, IDs, passports, resumes, bank statements, and any other document type via Mindee's configurable extraction models. Enqueue a f...
Mindee Classification API
Classify documents into predefined categories so they can be routed to the appropriate downstream extraction model. Enqueue at POST /v2/products/classification/enqueue and retri...
Mindee Crop API
Detect, isolate, and crop the document area inside a larger scanned image. Useful for cleaning up phone-captured documents prior to classification or extraction. Async enqueue/r...
Mindee OCR API
Run full-page optical character recognition on a document and return the raw text plus bounding polygons. Enqueue at POST /v2/products/ocr/enqueue and retrieve the OCR payload f...
Mindee Split API
Split a multi-document PDF or image batch into individual documents that can each be classified and extracted independently. Async enqueue/results pattern at /v2/products/split/.
Mindee Jobs API
Poll the status of asynchronous Mindee inference jobs across every Mindee model family via GET /v2/jobs/{job_id}. Jobs return Waiting, Processing, Failed, or Success states and ...
Postman Collections 6
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Mindee Classification API
POSTMANMindee Crop API
POSTMANMindee Extraction API
POSTMANMindee Jobs API
POSTMANMindee OCR API
POSTMANMindee Split API
POSTMANOpen Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Mindee Classification API
OPEN COLLECTIONMindee Crop API
OPEN COLLECTIONMindee Extraction API
OPEN COLLECTIONMindee Jobs API
OPEN COLLECTIONMindee OCR API
OPEN COLLECTIONMindee Split API
OPEN COLLECTIONArazzo Workflows 14
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Mindee Bank Statement Extraction
Enqueue a bank statement with RAG and raw text enabled, poll until processed, then read the extracted transactions and balances.
ARAZZOMindee Classify Document Type
Enqueue a document for classification, poll until processed, then read the predicted document type.
ARAZZOMindee Classify Then Extract
Classify an unknown document, then run extraction on the same file once the type is known, reading the parsed fields.
ARAZZOMindee Crop Document
Enqueue a document for cropping, poll until processed, then read the detected objects and their crop coordinates.
ARAZZOMindee Custom Document Extraction
Enqueue an arbitrary document against a custom model with raw text capture, poll until processed, then read fields and full text.
ARAZZOMindee Extract From URL
Enqueue a publicly hosted document by URL for extraction, poll until processed, then read the extracted fields.
ARAZZOMindee Invoice Extraction
Enqueue an invoice for extraction, poll the job until processed, then read the extracted fields.
ARAZZOMindee OCR Full Text
Enqueue a document for full-page OCR, poll until processed, then read the per-page words and text content.
ARAZZOMindee OCR Then Extract
Run OCR over a document to capture its raw text, then extract structured fields from the same file, reading both outputs.
ARAZZOMindee Passport and ID Extraction
Enqueue a passport or identity document with polygon locations, poll until processed, then read the extracted holder fields.
ARAZZOMindee Poll Job With Failure Branch
Enqueue an extraction, poll the job, and branch explicitly on Processed, Processing, or Failed before reading the result.
ARAZZOMindee Receipt Extraction
Enqueue a receipt with confidence scoring, poll until processed, then read the extracted line items and totals.
ARAZZOMindee Split Multi-Document File
Enqueue a multi-document file for splitting, poll until processed, then read the identified document ranges.
ARAZZOMindee Split Then Extract
Split a multi-document file into ranges, then extract structured fields from the original file, reading splits and fields.
ARAZZOScroll within the panel for all 14 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Mindee Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Mindee Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Mindee Finops
FINOPSFeatures 15
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 15 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Mindee Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Mindee API Rules
SPECTRALMindee API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Mindee Inference
JSON SCHEMAMindee Job
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Mindee Extraction Structure
JSON STRUCTUREExamples 2
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Mindee — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 18
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 18 ·
Build 10
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 10 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/mindee · machine-readable index on apis.io