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 pars…

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 𝗣𝗮𝗿𝘀𝗲 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 to fix that. It uses LiteParse's 𝘪𝘴_𝘤𝘰𝘮𝘱𝘭𝘦𝘹 functionality to estimate complexity page-by-page and routes each page to the right tier based on why it's complex (scanned, sparse text, garbled encoding, vector text, embedded images) and how severely. Simple pages get parsed for free, in-process. Genuinely hard pages get routed to more capable LlamaParse tiers. No manual heuristics, no flat one-size-fits-all pipeline. And it's also available as an MCP server, so your agents can estimate complexity and choose a parsing tier themselves! The result: you stop paying premium prices for pages that never needed it, without sacrificing accuracy on the ones that do. 📚️ Full writeup: https://www.llamaindex.ai/blog/parse-gateway-smart-page-level-document-parser-routing 👩‍💻 Try it: https://github.com/run-llama/parse-gateway

Related

• LiteParse, our OSS document parser, is really good at parsing complex PDF layouts, text, and tables into a clean spatial grid. The best part…
• LiteParse is the best open-source, model-free document parser for AI agents. Run it over over 50+ document types, and it will parse dense pa…
• Fully solving document parsing includes covering every point on the Pareto curve of accuracy, cost, and latency: 1️⃣ High-accuracy parsing -…
• Parsing complex tables in PDFs is extremely challenging. Existing metrics for measuring table accuracy, like TEDS (tree edit distance simila…

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