Model catalogue · Mistral AI
Mistral OCR
Mistral OCR reads documents - scanned pleadings, invoices, tables, handwritten notes - and returns structured text including layout; without this step no model can work on a file that exists only as an image. It is procured via Google Vertex AI, and there the chain is closed: the platform operator's signed confidentiality agreement under section 203 of the German Criminal Code is service-bound and expressly covers third-party models as well, with processing during the request committed to the EU and to the Netherlands. That weighs particularly heavily here, because an OCR pipeline passes through complete files rather than extracts.
Everything section 203 requires is settled, including the provider's confidentiality undertaking. You do not have to clarify anything further.
What it is good for
- Reading scans, receipts and tables with layout preserved - the preliminary step for all file work
- Processing committed to the EU and to the Netherlands, European model vendor
- Covered by the platform operator's service-bound section 203 agreement
Where it stops
- An OCR pipeline sends complete files through the service, not extracts - prior redaction is practically impossible here, which makes the contractual position all the more important
- The platform operator is a US group - CLOUD Act exposure remains despite the European model vendor
- The reach of the logging exception for third-party models cannot be evidenced from publicly available documents (as of 2026-08-17)
- Recognition errors on handwriting and poor scans remain - figures and deadlines from an OCR run have to be read back
- The platform's global endpoint gives no residency guarantee - the same models can be called there as well. Binding to the EU is therefore a configuration requirement: the global endpoint is blocked by organisational policy, otherwise the EU commitment is a settings question rather than a property.
Routes examined
The same model, procured differently, is a different legal position. What is examined per route is the contract chain, not the model.
| Route | Section 203 status | Version on this route |
|---|---|---|
| Google EU platform (Gemini Enterprise, formerly Vertex AI) | covered | - |
The conditions behind a conditional status - which piece is open on which route and who closes it - are set out in the full matrix in the German catalogue, and we go through them in the conversation. The German page for Mistral OCR carries the sources with their retrieval dates.
Is Mistral OCR the right fit?
We go through your tasks and the route that carries them - and say plainly where it does not.
Arrange a conversation