LlamaIndex 做的 Parse Gateway 能根据每页复杂度自动选解析模式，简单页免费处理，复杂页用高级版，省成本又不牺牲准确率。
LlamaIndex 发布 Parse Gateway，基于 LiteParse 的 is_complex 功能逐页判断文档复杂度。简单文本页面路由到免费、快速的文本解析器；复杂页面（含扫描、表格、图表等）路由到 LlamaParse 的 agentic 或 agentic plus 模式。该方案取代了传统的一刀切管道，在降低解析成本的同时保持高准确率。Parse Gateway 代码已开源，并集成到 MCP 服务器供智能体自主调用。
Introducing the Parse Gateway There's been an explosion of interest in model routing - you don't a...
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 llamaindex.ai/blog/parse-gat… YD LlamaParse cloud.llamaindex.ai z8 LlamaIndex 🦙 @llama_index 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 d llamaindex.ai/blog/parse-gat… ttps://t.co/K5 github.com/run-llama/pars… https://t.co/Gl0Dggv8qn 🔗 View Quoted Tweet 💬 2 🔄 0 ❤️ 2 👀 444 📊 2 ⚡