Introducing the Parse Gateway There's been an explosion of interest in model routing - you don't always need the best model for every task. …

Introducing the Parse Gateway There's been an explosion of interest in model routing - you don't always need the best model for every task. That is especially true for document parsing 📄🔀: - Some pages are text-heavy and relatively simple. These pages can be handled by cheap, fast text-based parsers - Other pages are more complex with a variety of dimensions: scans, dense tables, complex diagrams and charts, garbled binary text, and more. The trick is to use a good parse router that can optimize the parsing mode depending on page complexity! The Parse Gateway is based on the is_complex functionality we introduced within liteparse, which estimates the complexity of a page at the page level. Depending on the complexity, it routes the page to our various modes within LlamaParse: cost-effective, agentic, and agentic plus. The gateway code itself is open-source, but you can also directly find an implementation within our MCP server Check out the blog! https://www.llamaindex.ai/blog/parse-gateway-smart-page-level-document-parser-routing LlamaParse: https://cloud.llamaindex.ai/ Not every page in your PDF needs the same treatment. A scanned cover, a dense table, a clean text page, a figure-heavy diagram.... most parsing pipelines throw all of them at the same parser, forcing a tradeoff between cost, speed, and accuracy across the whole document. We built…

Related

• We've rolled out improvements to LlamaParse Cost Optimizer. Our intelligent tier routing now more reliably ensures you always strike the rig…
• This is a neat idea around doing model routing and sub-agent delegation while ensuring cache hits on accumulated context for all agents. It …
• Introducing: Granular job tracking and cost attribution in LlamaParse 🦙 Parsing thousands of pages a day is a lot to manage. Engineering te…

Source: Jerry Liu (X) | 2026-07-30