LIFEHUBBER
Choose theme

AI Resources

PageIndex

GitHub stars: 39.1K GitHub forks: 3.4K Declared license: MIT: MIT Last pushed October 12, 2026: Pushed today
Stats from GitHub

PageIndex builds a section tree for searching long PDFs and Markdown documents with an LLM.

Its SDK supports local and cloud indexing, document questions and agent tools. Retrieval follows document structure, with references that let the reader locate the material behind an answer. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

A document tree index for RAG

A RAG framework that searches a document hierarchy rather than starting with vector similarity.

Why it stands out

Reasoning-first retrieval

Sections stay connected to their source locations, so retrieved context can be checked against the document.

Availability

Repository and SDK documentation

Public repository and SDK documentation, with local and cloud workflows and agent-integration examples.

Why it matters

What makes it useful

For a question buried in a long report, PageIndex lets an LLM navigate the report through its sections. This gives document search a structure to follow instead of treating every passage as an isolated match.

Notable points

What stands out

The SDK offers two indexing paths: Flash uses layout statistics to form the initial structure and an LLM for summaries; Standard retains the LLM-based indexing pipeline.

Before using

What to review

Check supported document formats and the configured indexing and answering providers, including their API requirements and costs.

Local index storage does not by itself keep answering calls local; choose the provider and deployment path to suit the documents.

When connecting an agent to a particular report, document_context can steer it toward that report, but it does not restrict which documents its tools can access. Keep the default read-only tools for a reading task; enable management tools only when the agent should also modify the library.

Reader fit

Who may find it relevant

Builders working with long reports, manuals or document-based agents. It is a retrieval component to integrate, rather than a model checkpoint or a finished general chatbot.

Editorial note

Why LifeHubber lists it

For a builder who already has an agent framework, PageIndex offers matching integration tools for a local index or cloud library. Document retrieval can therefore be added while retaining the agent framework and its model configuration.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Test the whole long-document retrieval path.

PageIndex changes how sections are found. The next step is to check whether parsing preserves the document, compare a full RAG platform, and map the wider retrieval stack.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving