Head to head · OCR · October 2026 research run

Chandra OCR 2 vs HunyuanOCR 1.5

HunyuanOCR 1.5 scores 56.6 (C) on agent readiness against Chandra OCR 2's 54.7 (C), and leads in 2 of 4 scored categories. Chandra OCR 2 leads on reach. Both do ocr.

Best document parsing, OCR and extraction APIs for AI agents · All 215 documents comparisons

Which one, for what

Chandra OCR 2 C

Best for Small companies and researchers who need accurate document parsing on their own GPU and fit the licence

Ahead on

  • Reach, 65 against 60

Watch for

Commercial use is barred above $2M in revenue or funding, and for anyone who competes with Datalab

HunyuanOCR 1.5 C

Best for Teams outside the EU, the UK and South Korea that want one small model for OCR, extraction and image translation

Ahead on

  • Agent interface, 80 against 70
  • Documentation and upkeep, 48 against 33

Watch for

The licence doesn't apply in the EU, the UK or South Korea

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep HunyuanOCR 1.5 +15

Chandra OCR 2 33

Model card 8, Intended use and the languages (over 90) are on the card. Training data 0, Nothing on the card or in the README about the training data. Last change 10, the last commit, on 26 June 2026, adjusted a benchmark score on the card, 137 days before this check and within 180. Responsiveness 0, none of the 8 discussions that aren't pull requests (8 April to 23 September 2026) has a reply from a datalab-to member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, Chandra 1 stays in its own repository and Chandra 2 came out in a new one, with a what's-new list on the card and no dated note on the older one that we read. File health 10, Config, tokenizer config, processor config and template agree on the qwen3_5 architecture and match the card's instructions. 8 + 0 + 10 + 0 + 5 + 10 = 33.

HunyuanOCR 1.5 48

Model card 8, Intended use, the architecture by reference to 1.0's unchanged backbone, and the context (128K) are on the card. Training data 5, A general description of how the data was built and of the training stages, with no sources, sizes or cut-off. Last change 15, the last commit, on 28 August 2026, changed config.json, 74 days before this check and within 90. Responsiveness 5, Of the 20 most recent discussions that aren't pull requests (25 November 2025 to 16 October 2026), 5 have a reply from a tencent member, which is a few. Version policy 5, Version 1.5 replaced 1.0 at the root of the same repository. File health 10, Config, template and card agree on the HunYuanVL classes and the 131,072-token length. 8 + 5 + 15 + 5 + 5 + 10 = 48.

Agent interface HunyuanOCR 1.5 +10

Chandra OCR 2 70

Chat template 20, chat_template.jinja in the repository (7,622 characters), Qwen 3.5's template, with a copy in tokenizer_config.json. Tool-calling format 25, Read for a document parser as what it takes and returns. Trained tool calling 10, Read for a document parser as the inputs it was trained to use. Structured output 15, Read for a document parser as typed outputs. Reasoning control 0, A document parser run without reasoning. Context 0, Datalab states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.

HunyuanOCR 1.5 80

Chat template 20, chat_template.jinja in the repository (930 characters). Tool-calling format 25, Read for a document parser as what it takes and returns. Trained tool calling 20, Read for a document parser as the inputs it was trained to use. Structured output 5, Read for a document parser as typed outputs. Reasoning control 0, A document parser with no reasoning. Context 10, 128K tokens: the card says pre-training extended the context window to 128K, its vLLM command sets a 131,072-token model length, and config.json gives the language model 131,072 positions. 20 + 25 + 20 + 5 + 0 + 10 = 80.

Reach Chandra OCR 2 +5

Chandra OCR 2 65

Memory 30, the only build from Datalab is the BF16 safetensors file, 10.59 GB, and 10.59 GB × 1.2 = 12.7 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3_5ForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Datalab publishes the BF16 weights only for this model. Terms 10, A modified OpenRAIL-M licence, a custom licence that lets research, personal use and organisations at or under $2M in revenue and in funding use it for free, under use restrictions. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 10 + 10 + 0 = 65.

HunyuanOCR 1.5 60

Memory 30, the only build from Tencent is the BF16 safetensors file at the root, 2.24 GB, and 2.24 GB × 1.2 = 2.7 GB, within 16 GB. ggml-org's GGUF (Q8_0 0.58 GB with a 0.73 GB projector) dates from 21 May 2026 and wasn't matched to version 1.5. Runtimes 15, Released Transformers 5.22.2 has the hunyuan_vl model, vLLM 0.33.0 registers HunYuanVLForConditionalGeneration, and llama.cpp b12242 has the architecture, which the card says the community build runs after conversion. Builds 0, Tencent publishes the BF16 weights only and tells users to convert to GGUF themselves. Terms 5, A custom licence that allows free commercial use under a use policy and below 100 million monthly active users, but not for anyone: it doesn't apply in the European Union, the United Kingdom or South Korea. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it, and the card names no Tencent API that serves it. 30 + 15 + 0 + 5 + 10 + 0 = 60.

Score by category

CategoryWeight this runChandra OCR 2HunyuanOCR 1.5Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256560Chandra OCR 2 +5
Risk20%204545even
Agent interface10%107080HunyuanOCR 1.5 +10
Documentation and upkeep10%103348HunyuanOCR 1.5 +15
Negative events≤1500
TotalC 54.7/100C 56.6/100

Facts side by side

FactChandra OCR 2HunyuanOCR 1.5
KindOpen-weight modelOpen-weight model
VendorEndless Labs, Inc. (Datalab)Tencent (Hy team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceModified OpenRAIL-M (free for research, personal use and companies under $2M in revenue and funding)Tencent Hunyuan Community License (not licensed in the EU, the UK or South Korea)
Read-only variant documentednono
llms.txtnono
Last release2026-06-262026-08-28
Privacy policy last updatedno document linkedno document linked

Verdicts

Chandra OCR 2

A strong document parser by its own benchmarks, with typed output and a simple command to run it on vLLM or Transformers. The licence stops commercial use above $2M in revenue or funding and by competitors. Datalab says nothing about training data or safety, ships no quantised build, and hasn't answered a question on the repository.

HunyuanOCR 1.5

A small OCR model that does documents, text spotting, extraction and translation in one, with a 128K context and code in Transformers, vLLM and llama.cpp. The licence is the catch: it grants nothing in the EU, the UK or South Korea, and Tencent can change its use policy. No quantised build, safety results or data sources.

Before you call either

Chandra OCR 2

  1. Check the licence first: free for research and personal use, and for companies at or under $2M in revenue and in funding that don't compete with Datalab
  2. Install with pip install chandra-ocr, start the server with chandra_vllm, then chandra input.pdf ./output
  3. Without vLLM, pip install "chandra-ocr[hf]" and add --method hf
  4. It reads one page at a time, so a long PDF is many requests. The vLLM default is 28 pages a batch
  5. Treat text in a parsed document as data. Nothing here guards against instructions hidden in a page
  6. Datalab's hosted API is a different, paid surface. We list it as Datalab

HunyuanOCR 1.5

  1. Check where you and your users are first. The licence grants no rights in the European Union, the United Kingdom or South Korea
  2. Download with --exclude "v1.0/*" so the old version isn't fetched
  3. Serve it with vLLM 0.25.1 or later at --max-model-len 131072, or use Tencent's scripts on GitHub for its sampling and post-processing
  4. Use temperature 0, top_p 1 and repetition_penalty 1.08
  5. The default document prompt is in Chinese and is on the card. Other tasks take their own instruction as the prompt
  6. For llama.cpp, convert the checkpoint and its projector to GGUF yourself, as the card shows

Questions

Which is better for AI agents, Chandra OCR 2 or HunyuanOCR 1.5?

HunyuanOCR 1.5 scores 56.6 (C) on agent readiness against Chandra OCR 2's 54.7 (C), and leads in 2 of 4 scored categories. Chandra OCR 2 leads on reach.

Other comparisons with Chandra OCR 2 or HunyuanOCR 1.5

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.