PageIndex (@PageIndexAI) header
PageIndex (@PageIndexAI) profile picture

The last Document AI you'll ever need.

London
Joined June 2023
Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)Photo by PageIndex (@PageIndexAI)
Jev for RAG? How does the decision model's retrieval performance compare to the top Vector-based model? We announce the Page Search API, faster and more accurate than SOTA embedding models. Learn more: search.pageindex.ai/
10
19
4
169
10,943
PageIndex retweeted
Replying to @jerryjliu0
Parsing and OCR are inherently lossy representations. No single lossy representation can be universally optimal across all downstream tasks, since we can always define a task that depends on the information it discards. Therefore, benchmarks should focus on downstream task performance rather than intermediate representation quality. But if we rethink the problem from first principles, why use a vision model to generate an intermediate lossy representation at all? Why not eliminate that step entirely and let vision models work directly with the original documents?
1
21
Do we still need OCR? We have removed OCR from all our document AI pipelines, including question answering, retrieval, and extraction. The result? Higher accuracy, faster processing, and lower costs. pageindex.ai/blog/do-we-need…
16
14
1
138
11,121
Great talk! If OCR benchmarks don't reflect downstream performance, perhaps it's time to rethink OCR from first principles. OCR was invented when machines couldn't understand images and layouts. Now that multimodal models can, do we still need to convert PDFs into text? 🧵👇
Benchmarking is hard, even for experts. And most benchmarks are made by vendors who want to rank #1, not help you judge things fairly. I gave a talk on how you can stress-test benchmarks yourself.
1
2
6
854
2/3 No representation is lossless for every downstream task. The fundamental problem with OCR-first pipelines is that they decide what information to preserve before knowing the downstream task. For example, "What does the blue text say?" becomes impossible to answer if color information is lost.
1
158
3/3 We recently removed OCR from our Page Extract pipeline, and the improvement in extraction accuracy has been significant. Perhaps the future of Document AI isn't better OCR, but reasoning directly over original documents. pageindex.ai/extract
1
89
Page Extract API is #1 on ExtractBench from @llama_index, and much cheaper than the other top methods. The secret? We removed OCR from the standard extraction pipeline and use a pure vision model that reads each page as an image. Accuracy went up, and cost went down.
2
4
14
1,330
Gemini 4 Carbon. Now on PageIndex. We tested it across 40 10-K filings. Carbon (high) averaged 98.7% accuracy, tied for #2 in our Financial QA Benchmark. It scored slightly higher than Argon (high)’s 98.0%, but at about 48% higher query cost under current introductory pricing. Try the new model on PageIndex, with answers linked to their sources → developer.pageindex.ai/playg…
4
1
7
502
Meta (@AIatMeta) positions Muse Ember as delivering Haiku-level intelligence at ~1/3 the cost. We tested it with PageIndex on long financial documents. ✨ Ember (max) joins the accuracy–cost frontier in our Financial QA Benchmark: ▸ 87.7% accuracy — 1 pp below Claude Haiku 5.5 (max), at ~1/10 the query cost ▸ Lowest-cost config (of 39 tested) to exceed 85% accuracy Run Muse Ember on your own documents → developer.pageindex.ai/playg…
1
1
11
786
Full benchmark results, methodology and code → github.com/VectifyAI/pageind…
1
149
🚀 Introducing Page Extract, our first document extraction API powered by PageIndex! Turn complex PDFs into structured JSON with your own schema. Our Standard and Pro APIs outperform all other extractors on @llama_index's Extracbench at a lower cost. extract.pageindex.ai
20
10
1
68
23,513
Engineering documents are the hardest PDFs for document AI. Page Search Agent finds the exact page and gives the answer with visual citations. Try it now: search.pageindex.ai/examples…
3
5
1
79
4,085
Tencent Hy4 surprised us. Hy4 (high) just joined the Pareto frontier on our Financial QA benchmark. ➤ Accuracy: 99.0%, the highest score measured on the benchmark. ➤ Cost: About 1/12 the cost of Claude Opus 5.5 (max) per 100-question run. Congrats @TencentHunyuan ! Try it with your own documents: developer.pageindex.ai/playg…
2
1
18
970
Maps, drawings, scanned forms: PDFs where the answer is in the image, not the text. The hard case for document AI. Page Search agent reads the page, zooms in to search it, and cites the exact region it read. Try it now: search.pageindex.ai/examples…
3
5
17
1,014
Finding images in PDFs with classic RAG is painful: → PDF parsing → text embedding model → image embedding model → a pipeline to sync them Page Search API: upload, ask, and get the page with the image in seconds. No embeddings. No indexing time. search.pageindex.ai
3
22
1,270