PageIndex: Vectorless, Reasoning-based RAG
Build hierarchical tree indexes and reason over them for context-aware retrieval - no vector DB, no chunking.
Evidence: The repository provides no permission model, user confirmation mechanism, data flow transparency, sensitive data handling policy, dependency security audit, external impact assessment, rollback mechanism, or source attribution. All trust criteria lack evidence, hence score 0.
Evidence: Code and tests are internally consistent, tests cover key paths, but dependencies are pinned (e.g., litellm==1.84.0) without availability guarantees; error handling is tested but production failure messages are not explicit. Thus self-consistency 2, dependency availability 1, failure messages 1.
Evidence: README defines target audience (professionals handling long documents) and scenarios (finance, legal), capability boundaries (standard PDF parsing, complex PDFs need cloud) are stated, but trigger precision (e.g., CLI args) not detailed, environment fit (OS, Python version) not specified. Hence audience/scenarios 2, capability boundaries 2, trigger precision 1, environment fit 1.
Evidence: README is well-structured, install steps clear, examples and FAQ exist, known limitations (e.g., standard PDF parsing) mentioned, MIT license explicit, but versioning/changelog missing, maintenance responsibility unclear (publisher unverified). Thus information architecture 2, install notes 2, naming stability 1, examples/FAQ 2, known limitations 1, license 2, versioning/changelog 0, maintenance responsibility 1.
Evidence: Output is tree-structured JSON usable for RAG, marginal value in avoiding vector DB, but cost-benefit not quantified (e.g., API costs, performance comparisons). Hence output usability 2, marginal value 2, cost-benefit 1.
Evidence: README claims 98.7% accuracy but no reproducible verification steps; cross-source corroboration limited (only external benchmark mentioned); facts vs inferences not clearly separated. Hence claim traceability 1, cross-source corroboration 1, fact/inference separation 1.
- No security or privacy documentation provided; assess data exposure risks before use.
- Dependencies are pinned but not security-audited; check for known vulnerabilities.
- Performance claims (98.7% accuracy) lack reproducible verification steps; treat with caution.
What does this agent do, and when should you use it?
PageIndex is an open-source vectorless, reasoning-based RAG engine that constructs a hierarchical tree index from long documents and uses LLMs to reason over that index for retrieval. Unlike traditional vector similarity search, PageIndex mirrors human reading patterns through tree search, prioritizing relevance and interpretability. The repository provides a self-hosted Python package that generates tree structures from PDF or Markdown documents, with standard PDF parsing and an optional 'Flash' mode for faster generation. The project claims state-of-the-art 98.7% accuracy on FinanceBench, outperforming vector RAG. Deployment options include self-hosted, cloud service via API/MCP, and enterprise private deployment.
PageIndex transforms PDF or Markdown documents into a hierarchical tree structure (like a table of contents), where each node includes a title, summary, and page ranges. Retrieval involves LLM-based reasoning over the tree to find the most relevant sections. Key operations: run run_pageindex.py to generate the tree with --pdf_path or --md_path; optionally use --flash for heuristic-based fast generation; the examples/agentic_vectorless_rag_demo.py demonstrates Agentic RAG. Output is a JSON tree with fields like node_id, start_index, end_index, and summary.
- Financial analysts extracting specific data points from SEC filings or earnings reports for investment decisions.
- Legal teams searching through thousands of pages of regulations to find relevant clauses for compliance.
- Medical researchers retrieving specific study findings from academic literature for systematic reviews.
- Technical writers looking up API details in product manuals to update user guides.
- Enterprises implementing traceable and explainable document Q&A for internal knowledge management.
What are this agent's strengths and limitations?
- No vector database or chunking, avoiding the similarity-relevance mismatch of traditional RAG.
- Tree-based reasoning provides better traceability and explainability.
- Achieved 98.7% accuracy on FinanceBench, outperforming vector RAG.
- Flexible deployment: self-hosted, cloud, and enterprise options.
- Reliance on LLM reasoning leads to higher latency and cost, plus requires API keys.
- Standard PDF parsing struggles with complex layouts; cloud service needed for better OCR.
- Self-hosted version only supports PDF and Markdown; advanced features like OCR are paid.
- Project is early-stage; Flash mode is preview and may be unstable.
How do you install or deploy this agent?
Clone the repository from GitHub and install dependencies: pip3 install --upgrade -r requirements.txt. Set your LLM API key by creating a .env file in the root directory with OPENAI_API_KEY=your_key (LiteLLM supports multiple providers).
How do you use this agent?
Generate a tree from a PDF using python3 run_pageindex.py --pdf_path /path/to/document.pdf or from Markdown with --md_path. Optional arguments include --model (default gpt-4o-2024-11-20), --max-pages-per-node, etc. Use --flash for faster heuristic-based generation. For Agentic RAG, install openai-agents and run python3 examples/agentic_vectorless_rag_demo.py.
How does this agent compare with similar options?
Compared to traditional vector-DB RAG systems (e.g., based on FAISS or Pinecone), PageIndex emphasizes reasoning over similarity, claiming higher accuracy on professional documents.