# Chandra OCR 2 vs Nemotron 3.5 Parse (slim)

> Nemotron 3.5 Parse scores 69 (B) to Chandra OCR 2's 54.7 (C) for ocr. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/chandra-ocr-2-vs-nemotron-3-5-parse.md (~3,450 tokens) · this version ~730 tokens · JSON https://www.anchorterminal.com/compare/chandra-ocr-2-vs-nemotron-3-5-parse.json · canonical https://www.anchorterminal.com/compare/chandra-ocr-2-vs-nemotron-3-5-parse
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Nemotron 3.5 Parse scores 69 (B) 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.

- Chandra OCR 2: C 54.7, rank #127 of 160 open-weight models · https://www.anchorterminal.com/tools/chandra-ocr-2.min.md
- Nemotron 3.5 Parse: B 69, rank #10 of 160 open-weight models · https://www.anchorterminal.com/tools/nemotron-3-5-parse.min.md
- Chandra OCR 2, good for Small companies and researchers who need accurate document parsing on their own GPU and fit the licence Ahead on Reach, 65 against 60.
- Nemotron 3.5 Parse, good for Agents and pipelines with an NVIDIA GPU that need fast local page parsing into Markdown, tables and boxed blocks for retrieval or extraction Ahead on Risk, 60 against 45; Documentation and upkeep, 59 against 33.

| Category | Chandra OCR 2 | Nemotron 3.5 Parse |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 65 | 60 |
| Risk (20%) | 45 | 60 |
| Agent interface (10%) | 70 | 70 |
| Documentation and upkeep (10%) | 33 | 59 |

| Fact (where they differ) | Chandra OCR 2 | Nemotron 3.5 Parse |
| --- | --- | --- |
| Vendor | Endless Labs, Inc. (Datalab) | NVIDIA |
| Licence | Modified OpenRAIL-M (free for research, personal use and companies under $2M in revenue and funding) | OpenMDW-1.1 |
| Last release | 2026-06-26 | 2026-10-28 |
| Terms last updated | not read yet | no document linked |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Documentation and upkeep, Nemotron 3.5 Parse +26: Chandra OCR 2 33 (Model card 8, Intended use and the languages (over 90) are on the card.); Nemotron 3.5 Parse 59 (The card with its subcards covers intended use, limitations, architecture, parameters and the evaluated languages, and misses a context length and a cut-off (14…)
- Risk, Nemotron 3.5 Parse +15: Chandra OCR 2 45 (File safety 25, one safetensors file, no .bin, .pt or .pth files and no Python in the model repository.); Nemotron 3.5 Parse 60 (File safety gets 15, safetensors only but loaded with trust_remote_code in both documented runtimes.)
- 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.); Nemotron 3.5 Parse 60 (Memory earns the full 30, since the only build is a 2.52 GB F32 file that needs about 3 GB with the fifth added.)
