Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

We've spent years building LlamaParse into the most accurate document parser for production AI. Along the way, we learned a lot about what fast, lightweight parsing actually looks like under the hood. Today, we're open-sourcing a light-weight core of that tech as LiteParse 🦙 It's a CLI + TS-native...

llama_index's profile picture

LlamaIndex 🦙

119,096 subscribers

581,748 Aufrufe • vor 6 Monaten •via X (Twitter)

BildungGesundheit & WellnessWissenschaft & Technologie
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

LiteParse Samples 📄🧑‍🏫 LiteParse is our free and fast document parser that can parse text with bounding boxes from any document. I’ve created a new repository that contains some demos on how you can make use of its outputs! ✅ Comparison against PyPDF and PyMuPDF ✅ Visual Citations: search for any keyword and see joined bounding boxes pop up in the source images It should be a default tool to help AI agents OCR any document type (supports PDF, Word, Powerpoint + dozens of other formats), before heavier-weight VLM-based document parsing solutions (like our own LlamaParse). LiteParse Samples repo: LiteParse:
0:33

LiteParse Samples 📄🧑‍🏫 LiteParse is our free and fast document parser that can parse text with bounding boxes from any document. I’ve created a new repository that contains some demos on how you can make use of its outputs! ✅ Comparison against PyPDF and PyMuPDF ✅ Visual Citations: search for any keyword and see joined bounding boxes pop up in the source images It should be a default tool to help AI agents OCR any document type (supports PDF, Word, Powerpoint + dozens of other formats), before heavier-weight VLM-based document parsing solutions (like our own LlamaParse). LiteParse Samples repo: LiteParse:

Jerry Liu

13,196 Aufrufe • vor 5 Monaten

Our OSS engineer Clelia Bertelli (🦀/acc) recently built 𝗹𝗶𝘁𝗲𝘀𝗲𝗮𝗿𝗰𝗵, a fully local document ingestion and retrieval CLI/TUI application powered by LiteParse ⚡ litesearch demonstrates how developers can assemble a high-performance, local-first retrieval pipeline using open tools from across the ecosystem: • Parsing: LiteParse, the fast and accurate document parser we recently open sourced • Chunking: @ChonkieAI • Embeddings: A local Nomic model via Hugging Face transformers.js • Vector storage: A local Qdrant edge shard (custom-built in Rust and compiled as a native add-on) • Retrieval: Query stored files with optional path-based filtering and configurable relevance thresholds • Runtime: Bun for speed and versatility 💻 Check out the repository and try it yourself: 📚 LiteParse docs:
0:32

Our OSS engineer Clelia Bertelli (🦀/acc) recently built 𝗹𝗶𝘁𝗲𝘀𝗲𝗮𝗿𝗰𝗵, a fully local document ingestion and retrieval CLI/TUI application powered by LiteParse ⚡ litesearch demonstrates how developers can assemble a high-performance, local-first retrieval pipeline using open tools from across the ecosystem: • Parsing: LiteParse, the fast and accurate document parser we recently open sourced • Chunking: @ChonkieAI • Embeddings: A local Nomic model via Hugging Face transformers.js • Vector storage: A local Qdrant edge shard (custom-built in Rust and compiled as a native add-on) • Retrieval: Query stored files with optional path-based filtering and configurable relevance thresholds • Runtime: Bun for speed and versatility 💻 Check out the repository and try it yourself: 📚 LiteParse docs:

LlamaIndex 🦙

14,900 Aufrufe • vor 5 Monaten

Over 1 billion PDFs are created every day, but your agents still can’t read them reliably. Today we’re releasing Parse 2.0, the most accurate document parsing API in the world. Extend already processes millions of pages daily for leading AI teams like Brex, Mercury, Opendoor, Flatiron Health, and hundreds of others. Now, its even better. Parse 2.0 is SOTA quality on RealDoc-Bench, our open source benchmark that measures agent success rate on real world docs that agents actually encounter in production. We trained Parse 2.0 on 1M+ pages of the hardest documents seen in production. Here’s how it stacks up: - #1 in healthcare, real estate, logistics, and financial services - 95.7% agent Q&A accuracy on 581 docs (next best: 92%) - 0.847 F1 on layout (next best: 0.759) Give it a try today and build production-ready document agents with Extend.
1:32

Over 1 billion PDFs are created every day, but your agents still can’t read them reliably. Today we’re releasing Parse 2.0, the most accurate document parsing API in the world. Extend already processes millions of pages daily for leading AI teams like Brex, Mercury, Opendoor, Flatiron Health, and hundreds of others. Now, its even better. Parse 2.0 is SOTA quality on RealDoc-Bench, our open source benchmark that measures agent success rate on real world docs that agents actually encounter in production. We trained Parse 2.0 on 1M+ pages of the hardest documents seen in production. Here’s how it stacks up: - #1 in healthcare, real estate, logistics, and financial services - 95.7% agent Q&A accuracy on 581 docs (next best: 92%) - 0.847 F1 on layout (next best: 0.759) Give it a try today and build production-ready document agents with Extend.

Kushal Byatnal

588,683 Aufrufe • vor 4 Monaten

We’re excited to officially launch LlamaParse, the first genAI-native document parsing solution. Not only is it better at parsing out images/tables/charts 📊📈 than virtually every other parser, it is now steerable through natural language instructions - output the document in whatever format you desire! It is also the only parsing solution that seamlessly allows you to build accurate RAG over complex documents, free of hallucinations 🔥 We launched it in private preview a few weeks ago and hit 2k users, 1M total PDF pages parsed. And now it’s better than ever. LlamaParse contains the following killer features: ✅ SOTA table/chart extraction ✅ Seamless integration with LlamaIndex 🦙 advanced RAG/agents ✅✨ Natural language Parsing Instructions ✅✨JSON mode and image extraction ✅✨Support for ~10 document types (.pdf, .pptx, .docx, .xml) and more Our pricing is simple: 1k free per day, and additional pages at 0.3c a page, or $3 for 1k pages. If you want advanced document RAG and/or private deployments, come get in touch with us to chat about LlamaCloud. Check out our full blog post here: LlamaParse client repo: Signup at 🦙☁️: Come talk to us:
5:07

We’re excited to officially launch LlamaParse, the first genAI-native document parsing solution. Not only is it better at parsing out images/tables/charts 📊📈 than virtually every other parser, it is now steerable through natural language instructions - output the document in whatever format you desire! It is also the only parsing solution that seamlessly allows you to build accurate RAG over complex documents, free of hallucinations 🔥 We launched it in private preview a few weeks ago and hit 2k users, 1M total PDF pages parsed. And now it’s better than ever. LlamaParse contains the following killer features: ✅ SOTA table/chart extraction ✅ Seamless integration with LlamaIndex 🦙 advanced RAG/agents ✅✨ Natural language Parsing Instructions ✅✨JSON mode and image extraction ✅✨Support for ~10 document types (.pdf, .pptx, .docx, .xml) and more Our pricing is simple: 1k free per day, and additional pages at 0.3c a page, or $3 for 1k pages. If you want advanced document RAG and/or private deployments, come get in touch with us to chat about LlamaCloud. Check out our full blog post here: LlamaParse client repo: Signup at 🦙☁️: Come talk to us:

LlamaIndex 🦙

143,189 Aufrufe • vor 2 Jahren

Astra is awesome, but if you're using it specifically to parse and extract a massive volume of documents, you will break the bank (10c+ per page on parsing and extraction!) We've added a native LlamaParse connector to ChatGPT that gives the model access to high-quality document OCR and extraction at the pareto frontier of accuracy and cost. It contains native access to our parse and extract endpoints. Upload your most complex documents, and you can do the following: * digitalize it into extremely accurate context for any QA task * perform large-scale extraction from a set of documents with accurate grounding and citations Offload the higher-level reasoning to Astra, leave specialized doc parsing and extraction to us. ChatGPT plugin: Come sign up here:
0:31

Astra is awesome, but if you're using it specifically to parse and extract a massive volume of documents, you will break the bank (10c+ per page on parsing and extraction!) We've added a native LlamaParse connector to ChatGPT that gives the model access to high-quality document OCR and extraction at the pareto frontier of accuracy and cost. It contains native access to our parse and extract endpoints. Upload your most complex documents, and you can do the following: * digitalize it into extremely accurate context for any QA task * perform large-scale extraction from a set of documents with accurate grounding and citations Offload the higher-level reasoning to Astra, leave specialized doc parsing and extraction to us. ChatGPT plugin: Come sign up here:

Jerry Liu

11,083 Aufrufe • vor 15 Tagen

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:
1:24

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

Jerry Liu

22,763 Aufrufe • vor 1 Monat

Baidu Inc. just dropped PaddleOCR-VL-1.5, and it’s not just another OCR model. This is a fully open-source OCR model with just 0.9B parameters, built specifically for production-grade document understanding. And the results speak loudly 👇 On OmniDocBench V1.5, the most authoritative global document parsing benchmark, PaddleOCR-VL-1.5 ranks #1 overall, hitting 94.5% overall accuracy, outperforming models like DeepSeek-OCR2. As the first OCR model natively supporting irregular document layout positioning, it perfectly solves OCR pain points in production for complex structured business documents such as financial reports and insurance forms. While a lot of the industry is racing toward bigger models, PaddleOCR is betting on something smarter: small parameters + high performance + open source + real usability. That combination is exactly what scalable document intelligence needs right now. Demo / API → Open source → Model → Curious to see how teams start building on top of this.
0:29

Baidu Inc. just dropped PaddleOCR-VL-1.5, and it’s not just another OCR model. This is a fully open-source OCR model with just 0.9B parameters, built specifically for production-grade document understanding. And the results speak loudly 👇 On OmniDocBench V1.5, the most authoritative global document parsing benchmark, PaddleOCR-VL-1.5 ranks #1 overall, hitting 94.5% overall accuracy, outperforming models like DeepSeek-OCR2. As the first OCR model natively supporting irregular document layout positioning, it perfectly solves OCR pain points in production for complex structured business documents such as financial reports and insurance forms. While a lot of the industry is racing toward bigger models, PaddleOCR is betting on something smarter: small parameters + high performance + open source + real usability. That combination is exactly what scalable document intelligence needs right now. Demo / API → Open source → Model → Curious to see how teams start building on top of this.

Bishal Nandi

35,318 Aufrufe • vor 7 Monaten

An underrated issue with document parsing for RAG / agent use cases is dealing with multi-page tables - sometimes a big table spills over into multiple pages. This breaks chunking algorithms that generally operate at the page-level or smaller, and causes LLMs to lose the full view of the data. With LlamaParse Continuous Mode (in beta), you can now parse a document with multi-page tables and join them into a single table! This means you can now: 💡 Do contiguous chunking for RAG use cases OR 💡 Parse the table for text-to-SQL Check out our blog post highlighting this feature. Huge shoutout to Pierre-Loic Doulcet and Sacha Bron : Signup here: It's in beta, let us know your feedback!
2:22

An underrated issue with document parsing for RAG / agent use cases is dealing with multi-page tables - sometimes a big table spills over into multiple pages. This breaks chunking algorithms that generally operate at the page-level or smaller, and causes LLMs to lose the full view of the data. With LlamaParse Continuous Mode (in beta), you can now parse a document with multi-page tables and join them into a single table! This means you can now: 💡 Do contiguous chunking for RAG use cases OR 💡 Parse the table for text-to-SQL Check out our blog post highlighting this feature. Huge shoutout to Pierre-Loic Doulcet and Sacha Bron : Signup here: It's in beta, let us know your feedback!

Jerry Liu

24,245 Aufrufe • vor 1 Jahr

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks
1:46

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks

Adit

16,957 Aufrufe • vor 9 Monaten

PDF parsing is still painful because LLMs reorder text in complex layouts, break tables across pages, and fail on graphs or images. 💡Testing the new open-source OCRFlux model, and here the results are really good for a change. So OCRFlux is a multimodal, LLM based toolkit for converting PDFs and images into clean, readable, plain Markdown text. Because the underlying VLM is only 3B param, it runs even on a 3090 GPU. The model is available on Hugging Face . The engine that powers the OCRFlux, teaches the model to rebuild every page and then stitch fragments across pages into one clean Markdown file. It bundles one vision language model with 3B parameters that was fine-tuned from Qwen 2.5-VL-3B-Instruct for both page parsing and cross-page merging. OCRFlux reads raw page images and, guided by task prompts, outputs Markdown for each page and merges split elements across pages. The evaluation shows Edit Distance Similarity (EDS) 0.967 and cross‑page table Tree Edit Distance 0.950, so the parser is both accurate and layout aware. How it works while parsing each page - Convert into text with a natural reading order, even in the presence of multi-column layouts, figures, and insets - Support for complicated tables and equations - Automatically removes headers and footers Cross-page table/paragraph merging - Cross-page table merging - Cross-page paragraph merging A compact vision‑language models can beat bigger models once cross‑page context is added. 🧵 1/n Read on 👇
0:44

PDF parsing is still painful because LLMs reorder text in complex layouts, break tables across pages, and fail on graphs or images. 💡Testing the new open-source OCRFlux model, and here the results are really good for a change. So OCRFlux is a multimodal, LLM based toolkit for converting PDFs and images into clean, readable, plain Markdown text. Because the underlying VLM is only 3B param, it runs even on a 3090 GPU. The model is available on Hugging Face . The engine that powers the OCRFlux, teaches the model to rebuild every page and then stitch fragments across pages into one clean Markdown file. It bundles one vision language model with 3B parameters that was fine-tuned from Qwen 2.5-VL-3B-Instruct for both page parsing and cross-page merging. OCRFlux reads raw page images and, guided by task prompts, outputs Markdown for each page and merges split elements across pages. The evaluation shows Edit Distance Similarity (EDS) 0.967 and cross‑page table Tree Edit Distance 0.950, so the parser is both accurate and layout aware. How it works while parsing each page - Convert into text with a natural reading order, even in the presence of multi-column layouts, figures, and insets - Support for complicated tables and equations - Automatically removes headers and footers Cross-page table/paragraph merging - Cross-page table merging - Cross-page paragraph merging A compact vision‑language models can beat bigger models once cross‑page context is added. 🧵 1/n Read on 👇

Rohan Paul

149,423 Aufrufe • vor 1 Jahr

i'm flattered by the shoutout, but there's no free lunch for document parsing Cohere parse starts at $1.50 / 1k pages, which is indeed on the cheaper end of doc OCR solutions, but it scores ~50% when averaged across all 5 ParseBench dimensions: * It lacks high-quality visual grounding, doing coarse segmentation for tables and images, but lacking finer-grained bboxes at the word/cell/line-level. this is quite important for any sensitive AI application that requires precise citations back to the source. * It lacks general visual / chart parsing capabilities, which are prevalent across finance, manufacturing, healthcare, and more * to its credit, it does a decent job over tables (87%) compared to other comparable solutions at the price point our cost-effective mode in LlamaParse starts at 0.375c / page and is more consistently strong across all dimensions. also there's various ways to bring it down with volume discounts if you're interested in learning more about various document parsing modes and comparing tradeoffs in price/accuracy, come talk to us! LlamaParse:
0:26

i'm flattered by the shoutout, but there's no free lunch for document parsing Cohere parse starts at $1.50 / 1k pages, which is indeed on the cheaper end of doc OCR solutions, but it scores ~50% when averaged across all 5 ParseBench dimensions: * It lacks high-quality visual grounding, doing coarse segmentation for tables and images, but lacking finer-grained bboxes at the word/cell/line-level. this is quite important for any sensitive AI application that requires precise citations back to the source. * It lacks general visual / chart parsing capabilities, which are prevalent across finance, manufacturing, healthcare, and more * to its credit, it does a decent job over tables (87%) compared to other comparable solutions at the price point our cost-effective mode in LlamaParse starts at 0.375c / page and is more consistently strong across all dimensions. also there's various ways to bring it down with volume discounts if you're interested in learning more about various document parsing modes and comparing tradeoffs in price/accuracy, come talk to us! LlamaParse:

Jerry Liu

25,524 Aufrufe • vor 10 Tagen

Parsing documents with AI agents just got a lot more seamless🚀 We've rebuilt the LlamaParse MCP server to handle your document processing workflows, and you can connect it today to any MCP-compatible client at 🌐 Once connected, you'll be able to: 📁 Parse documents into clean markdown 🔍 Classify files against your own categories ✂️ Split long documents into labelled sections ⬆️ Upload files via URL or a browser-based upload flow Building a production MCP server surfaced some non-obvious challenges: getting auth to align with an existing platform identity system using WorkOS, working around MCP's lack of built-in file upload support, and making deployments, rate limiting and observability feel native with Vercel and . We wrote up all of it, from the OAuth flow, to the token-based upload design, to the tradeoffs we hit along the way📝 📚 Read the full blog: 👩‍💻 GitHub repository:
1:01

Parsing documents with AI agents just got a lot more seamless🚀 We've rebuilt the LlamaParse MCP server to handle your document processing workflows, and you can connect it today to any MCP-compatible client at 🌐 Once connected, you'll be able to: 📁 Parse documents into clean markdown 🔍 Classify files against your own categories ✂️ Split long documents into labelled sections ⬆️ Upload files via URL or a browser-based upload flow Building a production MCP server surfaced some non-obvious challenges: getting auth to align with an existing platform identity system using WorkOS, working around MCP's lack of built-in file upload support, and making deployments, rate limiting and observability feel native with Vercel and . We wrote up all of it, from the OAuth flow, to the token-based upload design, to the tradeoffs we hit along the way📝 📚 Read the full blog: 👩‍💻 GitHub repository:

LlamaIndex 🦙

19,906 Aufrufe • vor 4 Monaten

We Parse PDFs We spent 7 figures to put this on billboards throughout SF. I thought long and hard about putting something more creative and whimsical. But then you wouldn’t know what we do. AI agents (and humans) are consuming exponentially more documents as they do real work. They need the best quality document parser to not output garbage on downstream tasks. This is what we do today as a company. If you have any PDFs (or other documents), we parse them :) If you’re around SF in June for one of the following events, come stop by our booths: ✅ Snowflake Summit (this week, Booth 1123) ✅ Databricks Data+AI Summit (June 15-18, Booth 137) ✅ AI Engineer World Fair(June 29-July 2, Booth L-G47) You can find us by the same sign we put on our billboards! We Parse PDFs LlamaIndex 🦙
2:26

We Parse PDFs We spent 7 figures to put this on billboards throughout SF. I thought long and hard about putting something more creative and whimsical. But then you wouldn’t know what we do. AI agents (and humans) are consuming exponentially more documents as they do real work. They need the best quality document parser to not output garbage on downstream tasks. This is what we do today as a company. If you have any PDFs (or other documents), we parse them :) If you’re around SF in June for one of the following events, come stop by our booths: ✅ Snowflake Summit (this week, Booth 1123) ✅ Databricks Data+AI Summit (June 15-18, Booth 137) ✅ AI Engineer World Fair(June 29-July 2, Booth L-G47) You can find us by the same sign we put on our billboards! We Parse PDFs LlamaIndex 🦙

Jerry Liu

15,150 Aufrufe • vor 3 Monaten

2026 might be the year where hedge fund level research becomes accessible to literally anyone. Some random guy with Claude, a few regulatory PDFs and $12 of API credits can now do the kind of reverse engineering that used to require an actual team of analysts. Meanwhile most people still think AI is for anime pictures. This Jane Street / SEBI breakdown is one of the first articles in a while that actually feels like a glimpse of where things are going More like, AI turning highly asymmetric institutional workflows into open source infrastructure. Great article to read. -> A multi-agent LLM framework that simulates a hedge fund team analyzing stocks and generating trading signals, with support for Anthropic, OpenAI, and local models. -> A Python library for parsing and analyzing all major SEC EDGAR filing types (13F, ADV, 10-K, 8-K, 13D) with a built-in Claude MCP server for natural language queries.
0:20

2026 might be the year where hedge fund level research becomes accessible to literally anyone. Some random guy with Claude, a few regulatory PDFs and $12 of API credits can now do the kind of reverse engineering that used to require an actual team of analysts. Meanwhile most people still think AI is for anime pictures. This Jane Street / SEBI breakdown is one of the first articles in a while that actually feels like a glimpse of where things are going More like, AI turning highly asymmetric institutional workflows into open source infrastructure. Great article to read. -> A multi-agent LLM framework that simulates a hedge fund team analyzing stocks and generating trading signals, with support for Anthropic, OpenAI, and local models. -> A Python library for parsing and analyzing all major SEC EDGAR filing types (13F, ADV, 10-K, 8-K, 13D) with a built-in Claude MCP server for natural language queries.

Couch

35,032 Aufrufe • vor 4 Monaten

If you’re building an “agent over your PDFs” in 2026, one of the most underrated things you can do is to provide exact grounding back to the source document for any agentic answers. Specifically, showing the exact word, line, or region that the answer came from. Frontier vision models do a terrible job at this. They have a hard time predicting exact bounding boxes over region, tying it back to the source answer, and surfacing it as context in a cost-effective and accurate manner. Dedicated VLM-based document OCR/extraction tools like LlamaParse are a lot better at visual grounding and specifically tying it to extracted outputs. One of our main evaluation areas in ExtractBench, our recently released real-world benchmark, is to evaluate the visual grounding capabilities of document extraction. ExtractBench: If you want to give LlamaParse a shot, come check it out:
0:52

If you’re building an “agent over your PDFs” in 2026, one of the most underrated things you can do is to provide exact grounding back to the source document for any agentic answers. Specifically, showing the exact word, line, or region that the answer came from. Frontier vision models do a terrible job at this. They have a hard time predicting exact bounding boxes over region, tying it back to the source answer, and surfacing it as context in a cost-effective and accurate manner. Dedicated VLM-based document OCR/extraction tools like LlamaParse are a lot better at visual grounding and specifically tying it to extracted outputs. One of our main evaluation areas in ExtractBench, our recently released real-world benchmark, is to evaluate the visual grounding capabilities of document extraction. ExtractBench: If you want to give LlamaParse a shot, come check it out:

Jerry Liu

14,515 Aufrufe • vor 1 Monat

Web scraping will never be the same. (100% open-source visual search at scale) PixelRAG is a retrieval system that skips HTML parsing completely. Instead of scraping a page into text and embedding chunks, it screenshots the page and retrieves the image. A vision-language model reads the answer straight off the pixels. Why that matters: parsing is where web RAG quietly loses information. - A single HTML-to-text parser can drop 40%+ of a page. - Tables, charts, and layout get flattened or thrown out. - Swapping parsers alone can move accuracy ~10 points on the same docs. PixelRAG indexes the page a person actually sees. The team built a visual index of all of Wikipedia, 30M+ screenshots, and it still beats the strongest text RAG baseline by 18.1% on text-only QA. The repo also ships a Claude Code plugin that gives Claude eyes. It lets Claude screenshot any URL and read the rendered page instead of scraping the DOM. So you can hand it a live page, an arXiv paper, or your local site and ask what it actually looks like. One setup script. No MCP server, no backend. How the pipeline works: - Renders each document (web, PDF, image) to image tiles. - Embeds them with Qwen3-VL-Embedding, LoRA fine-tuned on screenshots. - Builds a FAISS index and serves a search API. A stronger reader model lifts accuracy with no re-indexing, since the index is just pixels. Everything is open-source under Apache-2.0. GitHub repo: Talking about RAG, I recently wrote an article on a new approach that makes retrieval much more efficient by cutting corpus size by 40x, reducing tokens per query by 3x, and improving vector search relevance by 2.3x. The article is quoted below.
0:55

Web scraping will never be the same. (100% open-source visual search at scale) PixelRAG is a retrieval system that skips HTML parsing completely. Instead of scraping a page into text and embedding chunks, it screenshots the page and retrieves the image. A vision-language model reads the answer straight off the pixels. Why that matters: parsing is where web RAG quietly loses information. - A single HTML-to-text parser can drop 40%+ of a page. - Tables, charts, and layout get flattened or thrown out. - Swapping parsers alone can move accuracy ~10 points on the same docs. PixelRAG indexes the page a person actually sees. The team built a visual index of all of Wikipedia, 30M+ screenshots, and it still beats the strongest text RAG baseline by 18.1% on text-only QA. The repo also ships a Claude Code plugin that gives Claude eyes. It lets Claude screenshot any URL and read the rendered page instead of scraping the DOM. So you can hand it a live page, an arXiv paper, or your local site and ask what it actually looks like. One setup script. No MCP server, no backend. How the pipeline works: - Renders each document (web, PDF, image) to image tiles. - Embeds them with Qwen3-VL-Embedding, LoRA fine-tuned on screenshots. - Builds a FAISS index and serves a search API. A stronger reader model lifts accuracy with no re-indexing, since the index is just pixels. Everything is open-source under Apache-2.0. GitHub repo: Talking about RAG, I recently wrote an article on a new approach that makes retrieval much more efficient by cutting corpus size by 40x, reducing tokens per query by 3x, and improving vector search relevance by 2.3x. The article is quoted below.

Akshay 🚀

947,346 Aufrufe • vor 3 Monaten

Kicking off the Document Agent Olympics. Build a document agent - Win $200 🥇 Document agents turn messy PDFs, invoices, and filings into structured data you can actually use. Think: extracting financials from SEC filings, reconciling invoices against contracts, or processing a stack of resumes to surface top candidates. We're giving away three $200 prizes for the best agents built over the next 3 weeks. To enter: 💛 Deploy the agent to LlamaCloud 🤝 Make sure the agent repository is public 🚀 Explain what your document agent is solving 🔥 Bonus points for a good readme and demo video And most importantly, let us know what you think about our new LlamaAgents Builder! Ready to participate? Join the contest and start building your winning agent! Signup to LlamaCloud to get started
0:35

Kicking off the Document Agent Olympics. Build a document agent - Win $200 🥇 Document agents turn messy PDFs, invoices, and filings into structured data you can actually use. Think: extracting financials from SEC filings, reconciling invoices against contracts, or processing a stack of resumes to surface top candidates. We're giving away three $200 prizes for the best agents built over the next 3 weeks. To enter: 💛 Deploy the agent to LlamaCloud 🤝 Make sure the agent repository is public 🚀 Explain what your document agent is solving 🔥 Bonus points for a good readme and demo video And most importantly, let us know what you think about our new LlamaAgents Builder! Ready to participate? Join the contest and start building your winning agent! Signup to LlamaCloud to get started

LlamaIndex 🦙

12,111 Aufrufe • vor 7 Monaten

We’re open sourcing the first document OCR benchmark for the agentic era, ParseBench. Document parsing is the foundation of every AI agent that works with real-world files. ParseBench is a benchmark that measures parsing quality specifically for agent knowledge work: ✅ It optimizes for semantic correctness (instead of exact similarity) ✅ It has the most comprehensive distribution of real-world enterprise documents It contains ~2,000 human-verified enterprise document pages with 167,000+ test rules across five dimensions that matter most: tables, charts, content faithfulness, semantic formatting, and visual grounding. We benchmarked 14 known document parsers on ParseBench, from frontier/OSS VLMs to specialized parsers to LlamaParse. Here are some of our findings: 💡 Increasing compute budget yields diminishing returns - Gemini/gpt-5-mini/haiku gain 3-5 points from minimal to high thinking, at 4x the cost. 💡 Charts are the most polarizing dimension for evaluation. Most specialized parsers score below 6%, while some VLM-based parsers do a bit better. 💡 VLMs are great at visual understanding but terrible at layout extraction. GPT-5-mini/haiku score below 10% on our visual grounding task, all specialized parsers do much better. 💡 No method crushes all 5 dimensions at once, but LlamaParse achieves the highest overall score at 84.9%, and is the leader in 4 out of the 5 dimensions. This is by far the deepest technical work that we’ve published as a company. I would encourage you to start with our blog and explore our links to Hugging Face to GitHub. All the details are in our full 35-page (!!) ArXiv whitepaper. 🌐: Blog: 📄 Paper: 💻 Code: 📊 Dataset: 🎥 YouTube:
1:08

We’re open sourcing the first document OCR benchmark for the agentic era, ParseBench. Document parsing is the foundation of every AI agent that works with real-world files. ParseBench is a benchmark that measures parsing quality specifically for agent knowledge work: ✅ It optimizes for semantic correctness (instead of exact similarity) ✅ It has the most comprehensive distribution of real-world enterprise documents It contains ~2,000 human-verified enterprise document pages with 167,000+ test rules across five dimensions that matter most: tables, charts, content faithfulness, semantic formatting, and visual grounding. We benchmarked 14 known document parsers on ParseBench, from frontier/OSS VLMs to specialized parsers to LlamaParse. Here are some of our findings: 💡 Increasing compute budget yields diminishing returns - Gemini/gpt-5-mini/haiku gain 3-5 points from minimal to high thinking, at 4x the cost. 💡 Charts are the most polarizing dimension for evaluation. Most specialized parsers score below 6%, while some VLM-based parsers do a bit better. 💡 VLMs are great at visual understanding but terrible at layout extraction. GPT-5-mini/haiku score below 10% on our visual grounding task, all specialized parsers do much better. 💡 No method crushes all 5 dimensions at once, but LlamaParse achieves the highest overall score at 84.9%, and is the leader in 4 out of the 5 dimensions. This is by far the deepest technical work that we’ve published as a company. I would encourage you to start with our blog and explore our links to Hugging Face to GitHub. All the details are in our full 35-page (!!) ArXiv whitepaper. 🌐: Blog: 📄 Paper: 💻 Code: 📊 Dataset: 🎥 YouTube:

Jerry Liu

108,093 Aufrufe • vor 5 Monaten

Today we’re introducing Superhuman Docs, the evolution of Coda (Superhuman Docs) into the best place for teams and AI to work together. I co-founded Coda to reimagine the modern document and enable anyone to make a doc as powerful as an app. Superhuman Docs builds on that mission, and is reimagined for how teams work with AI now. With Superhuman Docs, AI is no longer a solo experience. Docs AI works with you the way a teammate would, with full context of everything your team has built: your data, your briefs, your roadmaps, your connected tools. You can ask it to summarize a sprint, draft a decision record from your meeting notes, or pull a competitor analysis into a new page, and that work stays right where your teammates can pick it up. I’m incredibly proud of the team for bringing Docs to life! There’s so much more we’re launching, including a way to create custom interfaces on top of your data just by describing it. We’re also introducing Superhuman Databases for teams to manage up to 1 million rows, launching Docs MCP to open it up to the AI tools you already use, and debuting a brand new Mac app. We’ve been building toward this moment for a long time, and Docs starts rolling out today. If you’re an existing Coda user, everything you rely on in your docs will remain the same, and if you’re new, now is a great time to jump in.
4:07

Today we’re introducing Superhuman Docs, the evolution of Coda (Superhuman Docs) into the best place for teams and AI to work together. I co-founded Coda to reimagine the modern document and enable anyone to make a doc as powerful as an app. Superhuman Docs builds on that mission, and is reimagined for how teams work with AI now. With Superhuman Docs, AI is no longer a solo experience. Docs AI works with you the way a teammate would, with full context of everything your team has built: your data, your briefs, your roadmaps, your connected tools. You can ask it to summarize a sprint, draft a decision record from your meeting notes, or pull a competitor analysis into a new page, and that work stays right where your teammates can pick it up. I’m incredibly proud of the team for bringing Docs to life! There’s so much more we’re launching, including a way to create custom interfaces on top of your data just by describing it. We’re also introducing Superhuman Databases for teams to manage up to 1 million rows, launching Docs MCP to open it up to the AI tools you already use, and debuting a brand new Mac app. We’ve been building toward this moment for a long time, and Docs starts rolling out today. If you’re an existing Coda user, everything you rely on in your docs will remain the same, and if you’re new, now is a great time to jump in.

Shishir

24,342 Aufrufe • vor 2 Monaten

Today we’re announcing r-1, our new document parsing model. It’s more accurate than our most powerful agentic OCR models, faster, and up to 6x cheaper. At Reducto, we spent two years building specialized models for complex visual layouts, tables spanning multiple pages, and key formatting like strikethroughs. We then used everything we learned to build r-1, the first in a new generation of models designed to handle the hardest documents without multiplying cost. This early preview delivers a 20% lower error rate than our most accurate legacy agentic models and will keep improving with new checkpoints over the next few weeks. Accuracy is only the beginning. r-1 preview is available at 1¢ per page all-in, with additional volume discounts as you scale. In the near term we’re also going to release r-1 mini, and an auto mode that intelligently selects the right approach for each page. If you’re currently using another parser, we’re offering up to $5,000 in credits to evaluate and migrate. You can claim the migration offer and learn more about r-1 using the links in the comments. Happy parsing!
1:22

Today we’re announcing r-1, our new document parsing model. It’s more accurate than our most powerful agentic OCR models, faster, and up to 6x cheaper. At Reducto, we spent two years building specialized models for complex visual layouts, tables spanning multiple pages, and key formatting like strikethroughs. We then used everything we learned to build r-1, the first in a new generation of models designed to handle the hardest documents without multiplying cost. This early preview delivers a 20% lower error rate than our most accurate legacy agentic models and will keep improving with new checkpoints over the next few weeks. Accuracy is only the beginning. r-1 preview is available at 1¢ per page all-in, with additional volume discounts as you scale. In the near term we’re also going to release r-1 mini, and an auto mode that intelligently selects the right approach for each page. If you’re currently using another parser, we’re offering up to $5,000 in credits to evaluate and migrate. You can claim the migration offer and learn more about r-1 using the links in the comments. Happy parsing!

Adit

299,605 Aufrufe • vor 23 Tagen