Introducing Page Search API

The Pages That Answer, Instantly
Published on

Today we are introducing Page Search API: give it a document and your questions, and it returns the pages that answer each one, with a relevance score for every page. Your LLM or agent then reads only those pages, not the whole document.

It is the retrieval step of PageIndex Agent, offered on its own for teams that already have an LLM, an agent, or a pipeline of their own and want the right pages to feed it.

Why pages

Most retrieval returns chunks: fixed-size slices of text, ranked by how close their embeddings sit to the question. Chunks cut tables, figures and arguments in half, and closeness in meaning is not the same as relevance.

Page Search returns pages, the unit a document was written and laid out in. A page keeps its table whole, its chart next to its caption, and its footnote under its claim, and every result is already a citation: page 39 of report.pdf.

Results

We compared Page Search with three embedding models, Voyage 4 Large, Gemini Embedding 2 and OpenAI text-embedding-3-large, on 80 questions over 39 annual reports (10-K filings), every method searching the same page text. The measure is the share of the pages that answer that each method returns among its first k pages:

Top 5Top 10Top 20
Page Search API93.2%97.5%99.3%
Voyage 4 Large65.5%83.8%90.3%
Gemini Embedding 254.0%70.1%86.3%
OpenAI text-embedding-3-large47.5%68.0%79.9%

In its top 5, Page Search finds 42% more of the pages that answer than the best embedding model. For 93.8% of questions, every page that answers is in its first 10 results, against 65.0% for Voyage.

It is also faster, because there is nothing to build first. Searching a new 160-page filing with one question, upload and processing included, takes 1.1 seconds, against 2.4 to 3.2 seconds to embed the same pages with the embedding models.

And it saves tokens. Left to its default, Page Search lists the pages likely to help: 4.7 pages a question on average, out of a filing's 186. Those few pages hold 95% of the evidence and leave out 97% of the filing, and so of the tokens you would otherwise send your LLM.

The questions, documents, results and code are on GitHub.

How to use it

Install the PageIndex SDK, upload a PDF, and ask:

pip install -U pageindex
from pageindex import PageIndexClient

client = PageIndexClient(index="cloud")  # reads PAGEINDEX_API_KEY
doc_id = client.submit_document("report.pdf", wait=True)["doc_id"]

result = client.search(["What was capital expenditure in 2018?", "Who is the CEO?"], document=doc_id)
for answer in result["results"]:
    print(answer["question"])
    for page in answer["documents"][0]["pages"]:
        print("  page", page["page"], page["relevance"])

Ask up to 10 questions in one search; ten take about as long as one.

What it can do

  • Pictures too. The search is multimodal: it reads scans, photos, charts and diagrams, so you need no OCR model or PDF parser.
  • One document or many. Search one document, a collection, documents matching a metadata filter such as {"ticker": "NVDA", "year": 2026}, or all of them. Search documents finds which documents answer before you search their pages.
  • Built for agents. The SDK gives your agent ready-made search tools, and the API is also available over MCP.
  • One account with Page Extract. The same key, credit and documents work with Page Extract API: upload once, then search a document or extract from it.

Get started

Create a key in the Developer Dashboard and follow the Quick start, or paste this into Claude Code, Cursor, or any coding agent that can read a URL:

Read https://pageindex.ai/docs/search/quick-start.md and follow it to set up Page Search API in this project.

See pricing, or read more on the Page Search API page.