pageindex 0.3.0.dev2__tar.gz → 0.4.0__tar.gz

pageindex-0.4.0/PKG-INFO

@@ -0,0 +1,308 @@
+Metadata-Version: 2.4
+Name: pageindex
+Version: 0.4.0
+Summary: Python SDK for PageIndex — reasoning-based, vectorless document retrieval, cloud and local
+License: MIT
+License-File: LICENSE
+Keywords: rag,document,retrieval,llm,pageindex,vectorless
+Author: Ray
+Author-email: ray@vectify.ai
+Requires-Python: >=3.10
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3.15
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Provides-Extra: anthropic
+Provides-Extra: claude
+Provides-Extra: openai
+Requires-Dist: Pillow (>=9.0)
+Requires-Dist: PyPDF2 (>=3.0.0)
+Requires-Dist: anthropic (>=0.122.0) ; extra == "anthropic"
+Requires-Dist: claude-agent-sdk (>=0.1.53) ; extra == "claude"
+Requires-Dist: litellm (>=1.105.0)
+Requires-Dist: mcp (>=1.19.0,<3)
+Requires-Dist: openai (>=1.70.0)
+Requires-Dist: openai-agents (>=0.18.1)
+Requires-Dist: pypdfium2 (>=5)
+Requires-Dist: python-dotenv (>=1.0.0)
+Requires-Dist: pyyaml (>=6.0)
+Requires-Dist: regex (>=2024.0.0)
+Requires-Dist: requests (>=2.28.0)
+Requires-Dist: sortedcontainers (>=2.4.0)
+Requires-Dist: urllib3 (>=1.26)
+Project-URL: Documentation, https://docs.pageindex.ai
+Project-URL: Homepage, https://pageindex.ai
+Project-URL: Issues, https://github.com/VectifyAI/PageIndex/issues
+Project-URL: Repository, https://github.com/VectifyAI/PageIndex
+Description-Content-Type: text/markdown
+
+<div align="center">
+  
+<a href="https://vectify.ai/pageindex" target="_blank">
+<img width="1471" alt="pi_github_banner_low" src="https://github.com/user-attachments/assets/bae02956-6c4e-4a0b-adea-257b0be4aaa1" />
+</a>
+
+<br/>
+<br/>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/14736" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14736" alt="VectifyAI%2FPageIndex | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+</p>
+
+# PageIndex: Vectorless, Reasoning-based RAG
+
+<p align="center"><b>Reasoning-based RAG&nbsp; ◦ &nbsp;No Vector DB, No Chunking&nbsp; ◦ &nbsp;Context-Aware Retrieval&nbsp; ◦ &nbsp;Reads Like a Human</b></p>
+
+<h4 align="center">
+  <a href="https://pageindex.ai/developer">🌐 Website</a>&nbsp; • &nbsp;
+  <a href="https://developer.pageindex.ai/">☁️ Cloud</a>&nbsp; • &nbsp;
+  <a href="https://docs.pageindex.ai">📖 Docs</a>&nbsp; • &nbsp;
+  <a href="https://pageindex.ai/blog">📝 Blog</a>&nbsp; • &nbsp;
+  <a href="https://pageindex.ai/contact">✉️ Contact</a>&nbsp;
+</h4>
+  
+</div>
+
+
+
+<details open>
+<summary><h2>Updates</h2></summary>
+
+- [Aug '26] 🔥 [**PageIndex SDK**](#quickstart): `pip install -U pageindex` now ships **local mode**: index, retrieve, and chat entirely on your machine with your own LLM key, or point the same client at PageIndex Cloud with an API key.
+- [Aug '26] ⚡ [**PageIndex Flash**](https://pageindex.ai/blog/pageindex-flash): fast tree index generation for text-based PDFs, now the default indexing method in PageIndex SDK local mode.
+- [Scale PageIndex to Millions of Documents](https://pageindex.ai/blog/pageindex-filesystem): *PageIndex File System* is a file-level tree indexing layer that lets PageIndex reason over an entire corpus, not just a single document.
+- [PageIndex App](https://app.pageindex.ai): a human-like document analysis agent for long professional documents.<!-- Also available via [MCP](https://pageindex.ai/developer) or [API](https://pageindex.ai/developer). -->
+
+</details>
+
+
+
+# What is PageIndex?
+
+Are you frustrated with vector database retrieval accuracy for long and complex documents? Vector-based RAG retrieves by semantic **similarity**. But **similarity ≠ relevance** — what retrieval actually needs is relevance, and relevance requires **reasoning**. On professional documents that demand contextual understanding, domain expertise, and multi-step reasoning, similarity search misses what is relevant but not similar, and returns what is similar but not relevant.
+
+Inspired by AlphaGo, **[PageIndex](https://vectify.ai/pageindex)** replaces the vector index with a **hierarchical tree index** and lets an LLM **reason** its way through it, the way a human expert turns to and reads the right section of a long report. Retrieval happens in two steps:
+
+1. **Index**: generate a **tree-structure index** for each document
+2. **Retrieve**: agentically **search that tree** with LLM reasoning
+
+<div align="center">
+  <a href="https://pageindex.ai/blog/pageindex-intro" target="_blank" title="The PageIndex Framework">
+    <img src="https://docs.pageindex.ai/images/cookbook/vectorless-rag.png" width="70%">
+  </a>
+</div>
+
+
+### TL;DR
+
+<blockquote>PageIndex is a <b>vectorless</b>, <b>reasoning-based RAG</b> engine that <b>mirrors how humans read</b>, delivering <b>traceable</b>, <b>explainable</b>, and <b>context-aware</b> retrieval, with <b>no vector DBs</b> or <b>chunking</b>.</blockquote>
+
+### Compare with Vector RAG
+
+| | Vector RAG | **PageIndex** |
+|---|---|---|
+| **Index** | vector index | tree index |
+| **Retrieval** | semantic similarity search | LLM reasoning over the tree |
+| **Result** | opaque, “vibe retrieval” | traceable to explicit references |
+| **Context** | query embedding only | full context: conversation history, domain knowledge, etc. |
+
+It is ideal for financial reports, legal documents, regulatory filings, technical manuals, medical literature, academic textbooks, and any other long, complex professional document.
+
+
+
+
+# Quickstart
+
+```bash
+pip install -U pageindex
+```
+
+
+```python
+import os
+from pageindex import PageIndexClient
+
+os.environ["OPENAI_API_KEY"] = "your-openai-key"
+
+client = PageIndexClient(
+    index="gpt-6-luna",                 # model to build the tree index
+    chat="gpt-6-sol",                   # model to search the tree
+)
+doc_id = client.submit_document("report.pdf")["doc_id"]
+
+answer = client.chat("What was the 2023 operating margin?", doc_id=doc_id)
+print(answer)
+```
+
+### Model Recommendations
+
+- **`index=`: a basic model is sufficient.** The tree structure itself is extracted from the document layout without an LLM; the index model only summarizes and refines it, which a basic model does well.
+- **`chat=`: use the best model you can afford.** The chat model searches the tree to retrieve information. See [Query cost and accuracy](#query-cost-and-accuracy).
+
+### [Use PageIndex through the SDK client →](https://docs.pageindex.ai/getting-started)
+
+Configure other models, streaming, multi-document search, citations, and more.
+
+### [Integrate PageIndex with your own agent →](https://docs.pageindex.ai/sdk/agents)
+
+Drop PageIndex tools into the OpenAI Agents SDK, the Claude Agent SDK, or any other framework.
+
+
+# Benchmarks
+
+### Local indexing cost and time
+
+Building a tree locally runs **about $0.001 per page** with `gpt-5.6-luna` as the index model, so a 1,000-page textbook costs a little over a dollar and a few minutes, once, and every later question reuses it. PageIndex is designed not to rely heavily on the model used at index time, so in our experiments a basic model does not hurt quality.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-cost-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-cost-light.png" width="75%" alt="Indexing cost against document length, log-log, for nine PDFs from 9 to 1,098 pages. Points track a $0.0011-per-page reference line; the spread around it is text density, not length.">
+</picture>
+</div>
+
+Indexing time also scales predictably with document length. In the same local setup, the benchmark documents (9 to 1,098 pages) finished in roughly **13 seconds to 4.5 minutes**.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-time-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-time-light.png" width="75%" alt="Indexing time against document length, log-log, for nine PDFs from 9 to 1,098 pages. The measured indexing times range from about 13 seconds to 4.5 minutes and increase predictably with document length.">
+</picture>
+</div>
+
+
+
+### Query cost and accuracy
+
+[**PageIndex-OSS-Benchmark**](https://github.com/VectifyAI/PageIndex-OSS-Benchmark) measures exactly the setup in the quickstart above (`PageIndexClient()` in local mode, flash indexing, no OCR) on 62 lookup questions over 34 PDFs (1,945 pages) drawn from [MMLongBench-Doc-V2](https://github.com/VectifyAI/MMLongBench-Doc-V2). Every question's answer is a fact stated in running text, so a wrong answer is a **retrieval or reading failure**, not a reasoning one.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/results-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/results-light.png" width="75%" alt="Accuracy against average cost per question. Each model forms a near-vertical reasoning-effort ladder; moving between models costs an order of magnitude a step.">
+</picture>
+</div>
+
+
+Full results, data, and the runner are in the [benchmark repo](https://github.com/VectifyAI/PageIndex-OSS-Benchmark).
+
+### Cost per query vs. native PDF input
+
+The alternative to retrieval is handing the model the whole PDF on every question. That cost grows with the document; PageIndex's does not, because it reads only the nodes its reasoning reaches. On documents where both routes return the same answer, native PDF input costs **2.1× more at 52 pages and 16.6× more at 420** (`gpt-5.6-sol`, prompt caching excluded) — and at 805 pages the document no longer fits in the context window at all.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/query-cost-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/query-cost-light.png" width="75%" alt="Cost per query relative to PageIndex retrieval, for five PDFs from 52 to 805 pages. Passing the PDF natively costs 2.1x, 3.4x, 7.8x, and 16.6x more at 52, 85, 198, and 420 pages; at 805 pages it exceeds the model's context window.">
+</picture>
+</div>
+
+### Leading accuracy on FinanceBench
+
+PageIndex reached a state-of-the-art [**98.7% accuracy**](https://vectify.ai/blog/Mafin2.5) on [FinanceBench](https://arxiv.org/abs/2311.11944) (financial document QA benchmark), vastly outperforming vector-based RAG.
+
+<div align="center">
+<a href="https://github.com/VectifyAI/Mafin2.5-FinanceBench">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/financebench-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/financebench-light.png" width="70%" alt="FinanceBench accuracy: PageIndex 98.7%, vector RAG 50%.">
+</picture>
+</a>
+</div>
+
+Explore the full FinanceBench [evaluation results](https://github.com/VectifyAI/Mafin2.5-FinanceBench) and the [blog post](https://vectify.ai/blog/Mafin2.5).
+
+
+# PageIndex Cloud
+
+The open-source version is ideal for text-heavy PDFs and local workflows. With **PageIndex Cloud, document indexing and storage run in the cloud**: PageIndex handles parsing, OCR, image understanding, tree-index construction, and managed storage for you. The chat and retrieval layer remains **compatible with your model**, so you can search the cloud-hosted index using the model provider your application already uses.
+
+Moving indexing and storage from Local to Cloud only requires a [PageIndex API key](https://developer.pageindex.ai/):
+
+```python
+import os
+from pageindex import PageIndexClient
+
+os.environ["PAGEINDEX_API_KEY"] = "your-pageindex-key"
+os.environ["OPENAI_API_KEY"] = "your-openai-key"
+
+client = PageIndexClient(
+    index="cloud",                       # build and store the index in PageIndex Cloud
+    chat="gpt-6-sol",                    # use your preferred compatible model for chat
+)
+doc_id = client.submit_document("report.pdf", wait=True)["doc_id"]
+print(client.chat("What was the 2023 operating margin?", doc_id=doc_id))
+```
+
+| | **Local** | **Cloud** |
+|---|---|---|
+| Handles | Text-based PDFs | Text-based, scanned, and image-rich documents |
+| Indexing | On your machine | Managed by PageIndex |
+| Storage | Local directory | Cloud storage |
+| Citations | Page-level | Block-level |
+| OCR & image understanding | — | ✓ |
+| [Metadata](https://docs.pageindex.ai/sdk/documents#metadata-cloud) | — | ✓ |
+| [Folders](https://docs.pageindex.ai/sdk/documents#folders-cloud) | — | ✓ |
+| [MCP server](https://docs.pageindex.ai/mcp) | — | ✓ |
+
+### More About PageIndex Cloud
+
+- [Scale PageIndex to Millions of Documents](https://pageindex.ai/blog/pageindex-filesystem): **PageIndex File System** is a Cloud-only, file-level tree indexing layer that lets PageIndex reason over an entire corpus, not just a single document.
+
+### Ready to Try It?
+
+- Get a [PageIndex API key](https://developer.pageindex.ai/)
+- Read the [PageIndex Cloud documentation](https://docs.pageindex.ai/)
+
+For dedicated deployment (VPC or on-premises), [contact us](https://pageindex.ai/contact) or [book a demo](https://calendly.com/pageindex/meet).
+
+
+
+---
+
+# ⭐ Support Us
+
+Leave us a star 🌟 if you like our project. Thank you!  
+
+<p>
+  <img src="https://github.com/user-attachments/assets/eae4ff38-48ae-4a7c-b19f-eab81201d794" width="80%">
+</p>
+
+Please cite this work as:
+```
+Mingtian Zhang, Yu Tang and PageIndex Team,
+"PageIndex: Next-Generation Vectorless, Reasoning-based RAG",
+PageIndex Blog, Sep 2025.
+```
+
+<details>
+<summary>Or use the BibTeX citation.</summary>
+
+```bibtex
+@article{zhang2025pageindex,
+  author = {Mingtian Zhang and Yu Tang and PageIndex Team},
+  title = {PageIndex: Next-Generation Vectorless, Reasoning-based RAG},
+  journal = {PageIndex Blog},
+  year = {2025},
+  month = {September},
+  note = {https://pageindex.ai/blog/pageindex-intro},
+}
+```
+</details>
+
+
+
+
+---
+
+© 2026 [PageIndex AI](https://pageindex.ai)
+
+<img width="288" height="80" alt="pageindex-wordmark-animated-288-warm" src="https://github.com/user-attachments/assets/e1c677f2-b590-4ffc-859d-e8cc7d794bdf" />
+

pageindex-0.4.0/README.md

@@ -0,0 +1,262 @@
+<div align="center">
+  
+<a href="https://vectify.ai/pageindex" target="_blank">
+<img width="1471" alt="pi_github_banner_low" src="https://github.com/user-attachments/assets/bae02956-6c4e-4a0b-adea-257b0be4aaa1" />
+</a>
+
+<br/>
+<br/>
+
+<p align="center">
+  <a href="https://trendshift.io/repositories/14736" target="_blank"><img src="https://trendshift.io/api/badge/repositories/14736" alt="VectifyAI%2FPageIndex | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
+</p>
+
+# PageIndex: Vectorless, Reasoning-based RAG
+
+<p align="center"><b>Reasoning-based RAG&nbsp; ◦ &nbsp;No Vector DB, No Chunking&nbsp; ◦ &nbsp;Context-Aware Retrieval&nbsp; ◦ &nbsp;Reads Like a Human</b></p>
+
+<h4 align="center">
+  <a href="https://pageindex.ai/developer">🌐 Website</a>&nbsp; • &nbsp;
+  <a href="https://developer.pageindex.ai/">☁️ Cloud</a>&nbsp; • &nbsp;
+  <a href="https://docs.pageindex.ai">📖 Docs</a>&nbsp; • &nbsp;
+  <a href="https://pageindex.ai/blog">📝 Blog</a>&nbsp; • &nbsp;
+  <a href="https://pageindex.ai/contact">✉️ Contact</a>&nbsp;
+</h4>
+  
+</div>
+
+
+
+<details open>
+<summary><h2>Updates</h2></summary>
+
+- [Aug '26] 🔥 [**PageIndex SDK**](#quickstart): `pip install -U pageindex` now ships **local mode**: index, retrieve, and chat entirely on your machine with your own LLM key, or point the same client at PageIndex Cloud with an API key.
+- [Aug '26] ⚡ [**PageIndex Flash**](https://pageindex.ai/blog/pageindex-flash): fast tree index generation for text-based PDFs, now the default indexing method in PageIndex SDK local mode.
+- [Scale PageIndex to Millions of Documents](https://pageindex.ai/blog/pageindex-filesystem): *PageIndex File System* is a file-level tree indexing layer that lets PageIndex reason over an entire corpus, not just a single document.
+- [PageIndex App](https://app.pageindex.ai): a human-like document analysis agent for long professional documents.<!-- Also available via [MCP](https://pageindex.ai/developer) or [API](https://pageindex.ai/developer). -->
+
+</details>
+
+
+
+# What is PageIndex?
+
+Are you frustrated with vector database retrieval accuracy for long and complex documents? Vector-based RAG retrieves by semantic **similarity**. But **similarity ≠ relevance** — what retrieval actually needs is relevance, and relevance requires **reasoning**. On professional documents that demand contextual understanding, domain expertise, and multi-step reasoning, similarity search misses what is relevant but not similar, and returns what is similar but not relevant.
+
+Inspired by AlphaGo, **[PageIndex](https://vectify.ai/pageindex)** replaces the vector index with a **hierarchical tree index** and lets an LLM **reason** its way through it, the way a human expert turns to and reads the right section of a long report. Retrieval happens in two steps:
+
+1. **Index**: generate a **tree-structure index** for each document
+2. **Retrieve**: agentically **search that tree** with LLM reasoning
+
+<div align="center">
+  <a href="https://pageindex.ai/blog/pageindex-intro" target="_blank" title="The PageIndex Framework">
+    <img src="https://docs.pageindex.ai/images/cookbook/vectorless-rag.png" width="70%">
+  </a>
+</div>
+
+
+### TL;DR
+
+<blockquote>PageIndex is a <b>vectorless</b>, <b>reasoning-based RAG</b> engine that <b>mirrors how humans read</b>, delivering <b>traceable</b>, <b>explainable</b>, and <b>context-aware</b> retrieval, with <b>no vector DBs</b> or <b>chunking</b>.</blockquote>
+
+### Compare with Vector RAG
+
+| | Vector RAG | **PageIndex** |
+|---|---|---|
+| **Index** | vector index | tree index |
+| **Retrieval** | semantic similarity search | LLM reasoning over the tree |
+| **Result** | opaque, “vibe retrieval” | traceable to explicit references |
+| **Context** | query embedding only | full context: conversation history, domain knowledge, etc. |
+
+It is ideal for financial reports, legal documents, regulatory filings, technical manuals, medical literature, academic textbooks, and any other long, complex professional document.
+
+
+
+
+# Quickstart
+
+```bash
+pip install -U pageindex
+```
+
+
+```python
+import os
+from pageindex import PageIndexClient
+
+os.environ["OPENAI_API_KEY"] = "your-openai-key"
+
+client = PageIndexClient(
+    index="gpt-6-luna",                 # model to build the tree index
+    chat="gpt-6-sol",                   # model to search the tree
+)
+doc_id = client.submit_document("report.pdf")["doc_id"]
+
+answer = client.chat("What was the 2023 operating margin?", doc_id=doc_id)
+print(answer)
+```
+
+### Model Recommendations
+
+- **`index=`: a basic model is sufficient.** The tree structure itself is extracted from the document layout without an LLM; the index model only summarizes and refines it, which a basic model does well.
+- **`chat=`: use the best model you can afford.** The chat model searches the tree to retrieve information. See [Query cost and accuracy](#query-cost-and-accuracy).
+
+### [Use PageIndex through the SDK client →](https://docs.pageindex.ai/getting-started)
+
+Configure other models, streaming, multi-document search, citations, and more.
+
+### [Integrate PageIndex with your own agent →](https://docs.pageindex.ai/sdk/agents)
+
+Drop PageIndex tools into the OpenAI Agents SDK, the Claude Agent SDK, or any other framework.
+
+
+# Benchmarks
+
+### Local indexing cost and time
+
+Building a tree locally runs **about $0.001 per page** with `gpt-5.6-luna` as the index model, so a 1,000-page textbook costs a little over a dollar and a few minutes, once, and every later question reuses it. PageIndex is designed not to rely heavily on the model used at index time, so in our experiments a basic model does not hurt quality.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-cost-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-cost-light.png" width="75%" alt="Indexing cost against document length, log-log, for nine PDFs from 9 to 1,098 pages. Points track a $0.0011-per-page reference line; the spread around it is text density, not length.">
+</picture>
+</div>
+
+Indexing time also scales predictably with document length. In the same local setup, the benchmark documents (9 to 1,098 pages) finished in roughly **13 seconds to 4.5 minutes**.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-time-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/index-time-light.png" width="75%" alt="Indexing time against document length, log-log, for nine PDFs from 9 to 1,098 pages. The measured indexing times range from about 13 seconds to 4.5 minutes and increase predictably with document length.">
+</picture>
+</div>
+
+
+
+### Query cost and accuracy
+
+[**PageIndex-OSS-Benchmark**](https://github.com/VectifyAI/PageIndex-OSS-Benchmark) measures exactly the setup in the quickstart above (`PageIndexClient()` in local mode, flash indexing, no OCR) on 62 lookup questions over 34 PDFs (1,945 pages) drawn from [MMLongBench-Doc-V2](https://github.com/VectifyAI/MMLongBench-Doc-V2). Every question's answer is a fact stated in running text, so a wrong answer is a **retrieval or reading failure**, not a reasoning one.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/results-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/results-light.png" width="75%" alt="Accuracy against average cost per question. Each model forms a near-vertical reasoning-effort ladder; moving between models costs an order of magnitude a step.">
+</picture>
+</div>
+
+
+Full results, data, and the runner are in the [benchmark repo](https://github.com/VectifyAI/PageIndex-OSS-Benchmark).
+
+### Cost per query vs. native PDF input
+
+The alternative to retrieval is handing the model the whole PDF on every question. That cost grows with the document; PageIndex's does not, because it reads only the nodes its reasoning reaches. On documents where both routes return the same answer, native PDF input costs **2.1× more at 52 pages and 16.6× more at 420** (`gpt-5.6-sol`, prompt caching excluded) — and at 805 pages the document no longer fits in the context window at all.
+
+<div align="center">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/query-cost-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/query-cost-light.png" width="75%" alt="Cost per query relative to PageIndex retrieval, for five PDFs from 52 to 805 pages. Passing the PDF natively costs 2.1x, 3.4x, 7.8x, and 16.6x more at 52, 85, 198, and 420 pages; at 805 pages it exceeds the model's context window.">
+</picture>
+</div>
+
+### Leading accuracy on FinanceBench
+
+PageIndex reached a state-of-the-art [**98.7% accuracy**](https://vectify.ai/blog/Mafin2.5) on [FinanceBench](https://arxiv.org/abs/2311.11944) (financial document QA benchmark), vastly outperforming vector-based RAG.
+
+<div align="center">
+<a href="https://github.com/VectifyAI/Mafin2.5-FinanceBench">
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/financebench-dark.png">
+  <img src="https://raw.githubusercontent.com/VectifyAI/PageIndex/main/assets/financebench-light.png" width="70%" alt="FinanceBench accuracy: PageIndex 98.7%, vector RAG 50%.">
+</picture>
+</a>
+</div>
+
+Explore the full FinanceBench [evaluation results](https://github.com/VectifyAI/Mafin2.5-FinanceBench) and the [blog post](https://vectify.ai/blog/Mafin2.5).
+
+
+# PageIndex Cloud
+
+The open-source version is ideal for text-heavy PDFs and local workflows. With **PageIndex Cloud, document indexing and storage run in the cloud**: PageIndex handles parsing, OCR, image understanding, tree-index construction, and managed storage for you. The chat and retrieval layer remains **compatible with your model**, so you can search the cloud-hosted index using the model provider your application already uses.
+
+Moving indexing and storage from Local to Cloud only requires a [PageIndex API key](https://developer.pageindex.ai/):
+
+```python
+import os
+from pageindex import PageIndexClient
+
+os.environ["PAGEINDEX_API_KEY"] = "your-pageindex-key"
+os.environ["OPENAI_API_KEY"] = "your-openai-key"
+
+client = PageIndexClient(
+    index="cloud",                       # build and store the index in PageIndex Cloud
+    chat="gpt-6-sol",                    # use your preferred compatible model for chat
+)
+doc_id = client.submit_document("report.pdf", wait=True)["doc_id"]
+print(client.chat("What was the 2023 operating margin?", doc_id=doc_id))
+```
+
+| | **Local** | **Cloud** |
+|---|---|---|
+| Handles | Text-based PDFs | Text-based, scanned, and image-rich documents |
+| Indexing | On your machine | Managed by PageIndex |
+| Storage | Local directory | Cloud storage |
+| Citations | Page-level | Block-level |
+| OCR & image understanding | — | ✓ |
+| [Metadata](https://docs.pageindex.ai/sdk/documents#metadata-cloud) | — | ✓ |
+| [Folders](https://docs.pageindex.ai/sdk/documents#folders-cloud) | — | ✓ |
+| [MCP server](https://docs.pageindex.ai/mcp) | — | ✓ |
+
+### More About PageIndex Cloud
+
+- [Scale PageIndex to Millions of Documents](https://pageindex.ai/blog/pageindex-filesystem): **PageIndex File System** is a Cloud-only, file-level tree indexing layer that lets PageIndex reason over an entire corpus, not just a single document.
+
+### Ready to Try It?
+
+- Get a [PageIndex API key](https://developer.pageindex.ai/)
+- Read the [PageIndex Cloud documentation](https://docs.pageindex.ai/)
+
+For dedicated deployment (VPC or on-premises), [contact us](https://pageindex.ai/contact) or [book a demo](https://calendly.com/pageindex/meet).
+
+
+
+---
+
+# ⭐ Support Us
+
+Leave us a star 🌟 if you like our project. Thank you!  
+
+<p>
+  <img src="https://github.com/user-attachments/assets/eae4ff38-48ae-4a7c-b19f-eab81201d794" width="80%">
+</p>
+
+Please cite this work as:
+```
+Mingtian Zhang, Yu Tang and PageIndex Team,
+"PageIndex: Next-Generation Vectorless, Reasoning-based RAG",
+PageIndex Blog, Sep 2025.
+```
+
+<details>
+<summary>Or use the BibTeX citation.</summary>
+
+```bibtex
+@article{zhang2025pageindex,
+  author = {Mingtian Zhang and Yu Tang and PageIndex Team},
+  title = {PageIndex: Next-Generation Vectorless, Reasoning-based RAG},
+  journal = {PageIndex Blog},
+  year = {2025},
+  month = {September},
+  note = {https://pageindex.ai/blog/pageindex-intro},
+}
+```
+</details>
+
+
+
+
+---
+
+© 2026 [PageIndex AI](https://pageindex.ai)
+
+<img width="288" height="80" alt="pageindex-wordmark-animated-288-warm" src="https://github.com/user-attachments/assets/e1c677f2-b590-4ffc-859d-e8cc7d794bdf" />

pageindex-0.4.0/pageindex/__init__.py

@@ -0,0 +1,54 @@
+"""PageIndex SDK."""
+from typing import TYPE_CHECKING as _TYPE_CHECKING
+
+from .chat_stream import ChatStream
+from .client import PageIndexClient, PageIndexCloudClient, PageIndexLocalClient
+from .errors import PageIndexAPIError
+from .types import (ChatConfig, ChatProcessOptions, CloudIndexConfig,
+                    IndexConfig, LocalIndexConfig)
+
+if _TYPE_CHECKING:
+    from .flash import page_index_flash
+    from .imaging import highlight_region
+    from .page_index_classic import page_index, page_index_main
+    from .page_index_md import md_to_tree
+    from .tree_optimize import optimize_tree
+
+__all__ = [
+    "PageIndexClient", "PageIndexCloudClient", "PageIndexLocalClient",
+    "PageIndexAPIError",
+    "IndexConfig", "CloudIndexConfig", "LocalIndexConfig", "ChatConfig",
+    "ChatProcessOptions", "ChatStream",
+    "page_index", "page_index_main", "page_index_flash",
+    "optimize_tree", "md_to_tree", "highlight_region",
+]
+
+_LAZY = {
+    "highlight_region": ".imaging",
+    "page_index_flash": ".flash",
+    "optimize_tree": ".tree_optimize",
+    "md_to_tree": ".page_index_md",
+}
+_SUBMODULES = {"agent_tools", "chat_stream", "client", "cloud_api", "errors",
+               "flash", "imaging", "integrations", "local_api", "local_chat",
+               "local_store", "mcp_bridge", "page_index_classic",
+               "page_index_md", "tree_optimize", "types", "utils"}
+
+
+def __getattr__(name):
+    if name.startswith("_"):
+        raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
+    import importlib
+    if name in _SUBMODULES:
+        return importlib.import_module(f".{name}", __name__)
+    module = importlib.import_module(_LAZY.get(name, ".page_index_classic"), __name__)
+    try:
+        value = getattr(module, name)
+    except AttributeError:
+        raise AttributeError(f"module {__name__!r} has no attribute {name!r}") from None
+    globals()[name] = value
+    return value
+
+
+def __dir__():
+    return sorted(set(globals()) | set(__all__) | _SUBMODULES)

pageindex-0.4.0/pageindex/_version.py

@@ -0,0 +1,10 @@
+"""Installed-package version, shared by every surface that reports it upstream."""
+from __future__ import annotations
+
+
+def sdk_version() -> str:
+    try:
+        from importlib.metadata import version
+        return version("pageindex")
+    except Exception:
+        return "0.0.0"