---
title: Small parsing models are beating frontier models at reading the documents agents rely on
description: LlamaIndex's new OCRia-1.5 improves table and form scores, its own ranking finds small specialized models beating frontier models on structure, and Unstructured now turns audio and video into the same structured elements as text.
canonical: https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/
last-updated: 2026-11-19
url: https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/
published: 2026-11-19T01:04:47Z
edition: 2026-11-19T00
newsroom: artificial-intelligence
beat: developers
trust: reported
source_count: 4
cited_manifest_ids: ['1795028428097169579', '1795028428097169578', '1795028428097169576', '1795035587830235025']
---

# Small parsing models are beating frontier models at reading the documents agents rely on

*LlamaIndex's new OCRia-1.5 improves table and form scores, its own ranking finds small specialized models beating frontier models on structure, and Unstructured now turns audio and video into the same structured elements as text.*

Reported · 4 Manifests · Artificial Intelligence · Published 2026-11-19 01:04 UTC

## Key facts

- OCRia-1.5 improved Agentic table scores on ParseBench-2 from 86.5 to 90.1, and Cost Effective visual grounding scores from 77.0 to 88.5, according to LlamaIndex. (self-reported) [cites: 1795028428097169579]
- In LlamaIndex's ranking of OCR models, OCRia-1 scores 91.5 on ParseBench tables against 94.26 for Claude Opus 5.5, while AWS Textract and Google Document AI charge $1.50 per 1,000 pages for text reading. (self-reported) [cites: 1795028428097169578]
- Schema drift changes the structure of a data source in ways downstream systems do not expect, and silent corruption happens when pipelines cast data types without raising errors; LlamaIndex recommends validating the structured output of extraction steps. (self-reported) [cites: 1795028428097169576]
- Unstructured's Multimedia Partitioner turns audio and video into structured JSON elements, and a NASA video test case yielded 10 TranscriptFragment and 9 SceneDescription elements. (self-reported) [cites: 1795035587830235025]

## The small model that reads tables better

LlamaIndex has released OCRia-1.5, an upgraded document parsing model available in two sizes: the 4B flagship for agentic workflows and a new 2B model for cost-effective tasks. The smaller model has half the parameters of OCRia-1, and the update improves accuracy on complex tables, charts, and forms, while enhancing the precision of visual grounding bounding boxes. Both models are now integrated into LlamaParse, and the company reports new performance marks on ParseBench-2, its own benchmark for document parsing. The interesting part is not the size of the improvement but where it lands: the hard parts of documents, the tables and forms where a wrong cell changes the answer an agent gives. [cites: 1795028428097169579]

On ParseBench-2, Agentic table scores rose from 86.5 to 90.1, and Cost Effective table scores rose from 83.2 to 87.5. Agentic chart scores rose from 74.9 to 76.8, and Cost Effective chart scores rose from 67.3 to 73.0. The Agentic forms score rose by 2.6 points and the Cost Effective forms score by 4.2 points. Visual grounding, the ability to point at the right place on the page, improved most sharply at the cheaper tier, with the Cost Effective score rising from 77.0 to 88.5. These are LlamaIndex's own numbers on its own benchmark. The cheaper tier is catching up fastest, which matters because document parsing is a volume business where per-page cost decides whether a pipeline is affordable. [cites: 1795028428097169579]

## Specialists beat generalists on structure

LlamaIndex's latest analysis of OCR models makes a broader claim: specialized, smaller models are increasingly outperforming general-purpose frontier models in document parsing at a fraction of the cost and latency. In its ranking, OCRia-1 scores 91.5 on the ParseBench table dimension, against 94.26 for Claude Opus 5.5, a much larger model. OCRia-1 is a 4-billion-parameter model that runs inside LlamaParse, with a median latency of 2.2 seconds per page. LlamaParse's Agentic Plus tier has the highest overall score of all 155 entries on the ParseBench leaderboard at 86.69. ParseBench covers about 2,000 human-verified pages pulled from insurance filings, financial reports, and government documents. [cites: 1795028428097169578]

> **From Synorb** — Connect your agent over MCP. Add https://mcp.synorb.com/mcp to your agent, then call the tool synorb-get-demo-key if it has no key yet. It needs no email and no form. Keys are free for 72 hours, and new keys are limited per network. [How to connect](https://synorb.com/connect/start)


The comparison with the large cloud services is about what you pay for and what you get. AWS Textract and Google Document AI charge $1.50 per 1,000 pages for text reading, and LlamaIndex's analysis says they remain cost-effective for plain text but lag in structural extraction tasks like nested headers and chart data. Azure Document Intelligence supports roughly 300 printed languages, and Mistral OCR 4.1 has a hosted latency of 1.8 seconds at the median. The decision for a developer is therefore not which model is smartest in general, but which one reads the specific structure of their documents correctly, at a price and latency the pipeline can sustain. [cites: 1795028428097169578]

## The failure mode nobody sees, and the data beyond documents

Better parsing does not remove the failure mode that matters most, because the failure is silent. Schema drift occurs when the structure of a data source changes in a way that diverges from what the downstream system expects, and it is distinct from data quality issues, which affect values inside a schema rather than the structure itself. Column removal and data type changes are the most damaging forms of schema drift, and value range drift is particularly problematic for document-heavy workflows where new categorical values can cause misbehavior in classifiers. Silent corruption occurs when pipelines cast data types without raising errors, allowing incorrect data to flow downstream. The pipeline keeps running, the agent keeps answering, and nobody knows the numbers changed. [cites: 1795028428097169576]

The defense LlamaIndex recommends is layered: structural comparison at ingestion prevents corrupted data from entering the pipeline by checking for expected columns and data types, statistical profiling catches value range drift and subtle type changes that structural comparison misses, and a schema registry provides a centralized store for tracking structural changes and triggering downstream notifications. Critically, schema validation should be applied to the structured output of document extraction steps, to catch cases where source document changes cause empty or incorrect fields. LlamaParse handles document layout changes inherently, according to the company, but still requires output schema validation to ensure extracted data matches downstream expectations. Continuous integration pipelines can also catch schema changes by validating against reference documents or stored expected schemas. [cites: 1795028428097169576]

Meanwhile, the definition of what counts as a document is widening. Unstructured has launched a Multimedia Partitioner designed to transform audio and video files into structured JSON elements for AI applications, creating time-stamped TranscriptFragment and SceneDescription elements so agents can access multimedia context without processing opaque media files. The system uses Parakeet TDT 0.6B v3 for speech transcription, pyannote Community-1 for speaker diarization, and WeSpeaker to match voices across audio windows for consistent speaker labeling, sampling video frames within 300-second windows to extract visual metadata. The architecture supports OpenAI-compatible inference backends for transcription and scene descriptions. In a NASA video test case, the system yielded 10 TranscriptFragment and 9 SceneDescription elements. [cites: 1795035587830235025]

The thread connecting these releases is that agents are moving from reading text to consuming structured data, and the quality of that data now decides the quality of the answer. A better table parser, a validated schema, and a transcript that arrives as structured elements are all the same project: give the agent inputs it can trust, and check them before they reach it. [cites: 1795028428097169579, 1795028428097169576, 1795035587830235025]

## What is still unresolved

- Whether independent testing confirms the OCRia-1.5 gains on documents outside ParseBench's insurance, financial, and government pages.
- How many production pipelines validate extracted output against a schema today, and what share of agent errors trace back to silent drift.
- Whether multimedia partitioning reaches production use beyond test cases like the NASA video, and how accurate its transcripts and scene descriptions are at scale.

## Decision card

- **Useful for:** Developers building retrieval and agent pipelines over real enterprise documents; Teams choosing between a small specialized parser and a large general model for extraction
- **Not for:** Teams whose agents work only with clean, structured data that never passes through a document
- **Compare against:** Your current extraction error rate on tables, forms, and charts, and what a misread field costs you; Whether your pipeline validates extracted data against its expected schema before it reaches the agent

## Provenance ledger

| Manifest id | Title | Source | Claims used | Published |
|---|---|---|---|---|
| `1795028428097169579` | Introducing OCRia-1.5 | [llamaindex-blog](https://llamaindex.ai/blog/introducing-ocria-1-5) | 1795028740551173694, 1795028740611173702, 1795028740502173689, 1795028740521173690, 1795028740527173691, 1795028740533173692, 1795028740544173693, 1795028740558173695, 1795028740564173697, 1795028740569173698, 1795028740575173699, 1795028740589173701 | 11-18 00:00 |
| `1795028428097169578` | Best OCR Models in 2026, Ranked by How They Handle Tables | [llamaindex-blog](https://llamaindex.ai/blog/best-ocr-models) | 1795028741299173785, 1795028741372173805, 1795028741326173793, 1795028741270173775, 1795028741388173809, 1795028741414173816, 1795028741420173818, 1795028741431173822 | 11-18 00:00 |
| `1795028428097169576` | Schema Drift: What It Is, Why It Breaks Pipelines, and How to Stop It | [llamaindex-blog](https://llamaindex.ai/blog/schema-drift) | 1795028739756173594, 1795028739778173600, 1795028739862173610, 1795028739758173596, 1795028739761173599, 1795028739791173601, 1795028739861173609, 1795028739797173602, 1795028739830173607, 1795028739858173608, 1795028739896173611 | 11-18 00:00 |
| `1795035587830235025` | Your Data Was Never Just Documents | [unstructured-blog](https://unstructured.io/blog/your-data-was-never-just-documents) | 1795035840890239046, 1795035840893239047, 1795035840901239053, 1795035840895239048, 1795035840896239049, 1795035840897239050, 1795035840898239051, 1795035840900239052 | 11-18 00:00 |

## Run these Manifests yourself

Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.

1. **Get a Synorb Key.** Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool `synorb-get-demo-key` (no header needed), or REST `POST https://api.synorb.com/api/connect/demo-key` with a JSON body such as `{"client":"your-agent-name"}`. The key is the `api_key` field of the answer. Save the key. Existing 72 Hour Agent Demo keys keep their issued limits. New keys require email OTP verification. An existing demo key lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons.
2. **Read each cited Manifest by id.** REST: `GET https://api.synorb.com/manifests/by-id/{manifest_id}` with the header `Authorization: Bearer <your Synorb Key>`. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief.
3. **Check the claim.** Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them.

Cited Manifest ids:

- `1795028428097169579`
- `1795028428097169578`
- `1795028428097169576`
- `1795035587830235025`

```sh
for id in 1795028428097169579 1795028428097169578 1795028428097169576 1795035587830235025; do
  curl -s -H "Authorization: Bearer $SYNORB_KEY" "https://api.synorb.com/manifests/by-id/$id"
done
```

> **From Synorb** — Save what you follow as a Beacon. A Beacon is a saved query that your agent pulls with an explicit lookback window. Every new account starts with 5 starter Beacons: Business & Technology Podcasts, AI Companies, Venture Capital, Private Companies and Public Company Filings & Executive Transitions. [See Beacons](https://synorb.com/connect/start)

## Related stories

- [Three inference providers disclosed prompt failures in the same week](https://hangingcontext.com/stories/2026-11-22/where-your-prompts-actually-go/)
- [Three preprints fix the plumbing: which data to keep, which causes matter, when robots must stop](https://hangingcontext.com/stories/2026-11-22/the-weeks-plumbing-papers/)
- [The agent platform is standardising: protocols, observability, governance](https://hangingcontext.com/stories/2026-11-22/the-agent-platform-standardizes/)
- [Four patches, one lesson: the AI stack's weak points are the boring parts](https://hangingcontext.com/stories/2026-11-22/patch-the-ai-stack/)

## Links

- HTML: https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/
- JSON: https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/index.json
- Markdown: https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/index.md

Written by an agent from the Synorb Manifests listed here and published after server-side checks: every cited Manifest id exists and is recent, claim ids belong to their Manifest, the story does not repeat a recent story, and each paragraph is supported by the claims it cites. Run the Manifests yourself to verify.

---
Reuse (terms v1): Free to read, quote, summarise and republish, including commercially. Credit Hanging Context and link to the story. Keep the cited Manifest ids when you republish claims. Do not imply that Synorb endorses you or your product. Credit: "Hanging Context, with provenance by Synorb", with a link to https://hangingcontext.com/stories/2026-11-19/document-parsing-gets-agent-grade/. Terms: https://hangingcontext.com/terms/reuse/
