Any documentinto clean datain one API call

Images (PNG, JPEG, WebP, GIF, HEIC), PDFs, DOCX, spreadsheets, CSV, and raw text. Vector formats such as SVG are rejected, so rasterize before sending. Each document source is capped at 20 MB, and a PDF at 200 pages. Output comes back as JSON, Markdown, or plaintext.

Yes. Tables, stamps, signatures and layout are all things you can ask for, not detail that a flattened text dump threw away. One PDF can carry up to 200 pages and 20 MB, answered as a single document rather than a page at a time.

Creating a job places a hold on your balance, sized from your input plus the average output of recent completed jobs. When the job finishes, the hold settles to the real token count and usage.cost on the job is what you paid. The final number is often lower than the hold, and a failed job is refunded in full.

A job always ends in completed or failed, with a stable error_code you can branch on. Transient failures retry automatically with backoff before the job is given up on, and a failed job refunds its hold in full, so a failure costs nothing. Two codes describe the document rather than a glitch: engine_content_blocked and engine_output_too_long. Retrying those with the same document unchanged will usually fail the same way.

The file you send is encrypted at rest and deleted from storage the moment the job reaches completed or failed. What remains is the job record: output, target, schema, engine, tokens and cost, so you can audit a run later. We do not train on your content and we never ask you to supply training examples.

Everything checkable is checked before you see it. Totals reconcile, IBANs and tax identifiers pass their checksum, QR codes and barcodes carry the exact payload of the symbol on the page, and the numeric constraints in your schema hold on the value you receive. A value that does not resolve comes back exactly as printed instead of being quietly corrected, and a field that is genuinely not on the page comes back null. Route those nulls to review rather than forcing a guess.

Describe each shape you accept as an anyOf branch with an enum field that identifies it, and every entry comes back as the shape it actually is. One job classifies and extracts, which replaces a separate classify then route step. Note that all sources in one job are read together as one document set, so keep unrelated documents in separate jobs.

No. You add funds first, from $5 or the local equivalent in euros and pounds, and each job draws from that balance. There are no subscriptions and no seats. Playground runs in the dashboard are real jobs and are billed the same way as API calls.

Price, and the kind of document each suits. vera-1.0-high is the default at $1.75 per million input tokens and $4.00 per million output, and it is the one for dense scans, complex layouts and strict schemas. vera-1.0-low runs at $0.50 and $2.00 for simpler documents and high volume batches. The API and the schema handling are identical, so set engine per job and switch whenever you want.

You get a string back and then own everything around it: a queue that survives a slow document, retries, webhooks, per job cost accounting, size and page limits, and the checks that keep a plausible wrong value out of your database. Veralens is that pipeline behind one POST, with typed output, a per job cost you can read, and no charge for a run that fails.