DocsPricing & Funds

Pricing & Funds

Usage-based pricing, how balance holds settle, and how to add and track funds.

Add $5, get an API key

You pay for the tokens each job uses, from $5.

vera-1.0-high

Invoice (2 pages)
≈ $0.0074
Bank statement
≈ $0.0110
Receipt
≈ $0.0039

$5 covers about 670 invoicesHow we measured

vera-1.0-low

Invoice (2 pages)
≈ $0.0032
Bank statement
≈ $0.0050
Receipt
≈ $0.0014

$5 covers about 1,570 invoicesHow we measured

Veralens is prepaid and usage-based. You add funds to a balance, and each job draws from it based on the tokens it uses and the engine you pick. There are no seats or monthly minimums. You pay for what you extract.

Engines and rates

Prices are per 1,000,000 tokens. Input tokens cover what you send: your sources, your schema, and any instructions. Output tokens cover the result you get back. They are counted on the result as we return it, indented JSON included.

EngineInput / 1MOutput / 1MBest for
Enginevera-1.0-highInput / 1M$1.75Output / 1M$4.00Best forFor dense scans, complex layouts and strict schemas. The default.
Enginevera-1.0-lowInput / 1M$0.50Output / 1M$2.00Best forFor simple documents and high volume.

No subscription, no minimum. Funds do not expire. A failed job is refunded in full.

Select the engine per job with the engine field on POST /jobs/create. If you omit it, jobs use vera-1.0-high.

What a job costs

Four sample documents, each run once on both engines. Per 1,000 is the cost of 1,000 documents like it. Open a sample to run it yourself in the playground.

DocumentEngineJob costPer 1,000Tokens
DocumentInvoice (PDF, 2 pages, JSON)Enginevera-1.0-highJob cost$0.0074Per 1,000$7.37Tokens1,368 in, 1,244 out
DocumentInvoice (PDF, 2 pages, JSON)Enginevera-1.0-lowJob cost$0.0032Per 1,000$3.18Tokens1,368 in, 1,247 out
DocumentBank statement (PDF, 2 pages, JSON)Enginevera-1.0-highJob cost$0.0110Per 1,000$10.96Tokens1,317 in, 2,163 out
DocumentBank statement (PDF, 2 pages, JSON)Enginevera-1.0-lowJob cost$0.0050Per 1,000$4.96Tokens1,317 in, 2,150 out
DocumentReceipt (Photo, 1 page, JSON)Enginevera-1.0-highJob cost$0.0039Per 1,000$3.93Tokens1,270 in, 427 out
DocumentReceipt (Photo, 1 page, JSON)Enginevera-1.0-lowJob cost$0.0014Per 1,000$1.45Tokens1,270 in, 406 out
DocumentContract (PDF, 1 page, Markdown)Enginevera-1.0-highJob cost$0.0027Per 1,000$2.70Tokens578 in, 421 out
DocumentContract (PDF, 1 page, Markdown)Enginevera-1.0-lowJob cost$0.0011Per 1,000$1.13Tokens578 in, 421 out

Measured on 18 October 2026 on real jobs. Your cost depends on your document and schema; each job shows its exact cost.

Comparing with a vendor you use today? See the same invoice priced against Mindee, Nanonets and Veryfi.

How a charge works

  1. Hold on create. When you create a job, Veralens estimates the cost from your input and places a hold on your balance. If the balance can't cover the hold, the request fails with insufficient_balance.
  2. Settle on completion. When the job finishes, the hold settles to the actual token cost. The job's usage.cost is the amount you were charged.
  3. Refund on failure. If a job fails, its hold is refunded in full. You are never charged for a failed extraction.

Because the hold is an estimate and settlement uses real usage, a completed job's final cost can be higher or lower than the amount held.

What you never pay for

  • Pages. You pay for tokens, not for how a page is counted.
  • A monthly minimum.
  • A subscription or seats.
  • Funds that expire. Your balance stays until you use it.
  • Failed jobs. Each one is refunded in full.

Adding funds

Open Usage in the dashboard to add funds via Stripe checkout. You can pay in US dollars, euros or pounds. Checkout picks the currency for your country. You can add from $5, €5 or £5, up to $1,000, €1,000 or £1,000 per top-up. Funds do not expire. There is no free balance, so add funds before your first job. Balance is credited as soon as the payment completes. You can top up at any time, and jobs draw from the balance until it runs out.

Tracking spend

  • Every job carries its own usage: cost (USD), inputTokens, and outputTokens.
  • Usage in the dashboard summarizes spend and remaining balance over time.
  • Use GET /jobs/list to pull per-job cost for your own reporting.

Controlling cost

  • Use vera-1.0-low for high-volume or simpler documents.
  • Keep sources tight. Send only the pages or text you need to extract from.
  • Request only the fields you need. A smaller schema means fewer output tokens.
Add $5, get an API key

You pay for the tokens each job uses, from $5.