step 01
Read any document
gemma4 Parse PDFs, scans and forms, text, tables and layout, including images, with a vision-capable model. No OCR pipeline to maintain.
// use cases · document extraction
Read claims, invoices, contracts and forms, text, tables and scans, and return clean JSON. On EU infrastructure, fully auditable.
// how it works
Vision, extraction and classification from a single OpenAI-compatible endpoint, at volume, and only inside the EU.
step 01
gemma4 Parse PDFs, scans and forms, text, tables and layout, including images, with a vision-capable model. No OCR pipeline to maintain.
step 02
deepseek-v4-flash Pull fields straight into your own JSON schema with structured outputs, every value where you expect it, every time, ready to validate.
step 03
qwen3-embedding Classify the document type and route it to the right workflow, with embeddings you can audit, confident matches first, edge cases flagged.
// drop-in
Vision input and structured outputs work the OpenAI way. Change the base URL and key, point at gemma4, and get your schema back, privately.
read_the_docsfrom openai import OpenAI client = OpenAI( api_key="sk-...", base_url="https://api.helmcode.com/v1", # one line changes ) # vision in, structured JSON out — straight into your schema result = client.chat.completions.create( model="gemma4", messages=[{ "role": "user", "content": [ {"type": "text", "text": "Extract the invoice fields."}, {"type": "image_url", "image_url": {"url": invoice_png}}, ], }], response_format={"type": "json_schema", "json_schema": invoice_schema}, )
// why helmcode
The documents you process are full of PII and money. Closed APIs ask you to upload all of it, and log it.
The documents you extract, and the data inside them, are never stored, and never train a model.
Invoices, claims and contracts stay on EU infrastructure, not on US hyperscalers subject to the Cloud Act. GDPR and AI Act native.
Read a scan and return validated JSON from a single OpenAI-compatible endpoint, no separate OCR vendor, no glue code.
Process millions of documents a month. Limits are RPM and concurrency per key, never total tokens, so a busy month isn't a surprise bill.
DeepSeek V4-Flash, Qwen 3.6, Gemma 4. Your fields, your JSON, no proprietary extraction format to lock you in.
OpenAI-compatible structured outputs and vision. Change the base URL and key; your extraction code keeps working.
// extraction faq
What operations and engineering teams ask before automating document workflows.
Yes. gemma4 is vision-capable (and qwen3.6 is fully multimodal), so it reads scans, photos and forms, text, tables and layout, without a separate OCR pipeline.
Yes. Use OpenAI-compatible structured outputs (response_format json_schema) so fields land in your exact JSON shape, ready to validate and store.
No. Zero logs, documents and the data extracted from them are never persisted and never train a model. Extraction stops being a privacy liability.
Structured outputs constrain the response to your schema, so fields are always present and typed. Validate per field and flag low-confidence cases for review.
Yes. There are no token caps, limits are RPM and concurrency per API key, so you can process millions of documents a month on predictable, flat pricing.
Run on a dedicated GPU or fully on-premise inside your own datacenter, the same API and code, with documents that never leave your network.
// get started
Skip the AI infra work. Deploy your first private inference endpoint today.
Flat rate. EU data. OpenAI API compatible.
// cookies
We use strictly necessary cookies to run the site and, only with your consent, Google Analytics to understand usage. No advertising, ever — see our Cookie Policy.
// preferences