pageindex.ai valid

PageIndex

PageIndex is a vectorless, reasoning-based RAG engine that mirrors how humans read documents, delivering traceable, explainable retrieval with exact page references — no vector database and no chunking.

For agents: Vectorless reasoning-based RAG engine with REST API, SDK and MCP server for traceable page-referenced retrieval over long documents; docs, OpenAPI spec and quic

vectorless ragdocument retrievalpdf question answeringmcp serverreasoning retrieval

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T16:32:38.255Z. Cached copy · Source on pageindex.ai

# PageIndex

> PageIndex is a vectorless, reasoning-based RAG engine that mirrors how humans read documents, delivering traceable, explainable retrieval with exact page references — no vector database and no chunking.

PageIndex builds a hierarchical, reasoning-optimized tree of a document and navigates it with logical reasoning instead of semantic similarity. It takes long-form PDFs as input and returns retrieved passages with exact page references, so every answer is auditable. It achieves 98.7% accuracy on the FinanceBench benchmark. Integration surfaces are a REST API, an MCP server, and a Python SDK.

Common use cases: financial reports and SEC filings, regulatory and compliance documents, healthcare and medical reports, legal contracts and case law, and technical manuals and scientific documentation.

PageIndex is built and operated by Vectify AI Limited.

## Docs

- [Documentation](https://docs.pageindex.ai): Developer documentation for the API, SDK, and MCP server.
- [Quickstart](https://docs.pageindex.ai/quickstart): Shortest path from an API key to a first retrieval call.
- [Cookbook](https://docs.pageindex.ai/cookbook): Worked examples and integration recipes.
- [MCP documentation](https://docs.pageindex.ai/mcp): Setup and authentication for the PageIndex MCP server.
- [OpenAPI specification](https://api.pageindex.ai/openapi.json): Machine-readable schema for the REST API.

## Products

- [PageIndex Chat](https://chat.pageindex.ai): Hosted chat product for asking questions across long documents.
- [Developer dashboard](https://developer.pageindex.ai): Self-serve signup, API key management, and usage. Keys are created at https://developer.pageindex.ai/api-keys.
- [PageIndex API](https://api.pageindex.ai): REST API base URL. Marketing overview at https://pageindex.ai/api.
- [MCP overview page](https://pageindex.ai/mcp): Human-readable documentation page describing the MCP integration. This is an HTML page, NOT an MCP server endpoint — do not attempt to connect an MCP client to it. See the MCP section below for the real endpoints.

## MCP

Connect an MCP client to the endpoint below. `https://pageindex.ai/mcp` is a web page and will not respond to MCP requests.

- `https://api.pageindex.ai/mcp`: **The developer platform MCP server — start here.** Authenticate with an API key via the `Authorization: Bearer <API key>` header. Keys are created at https://developer.pageindex.ai/api-keys, no OAuth flow required.
- Server card (machine-readable endpoint list): https://pageindex.ai/.well-known/mcp
- [pageindex-mcp on GitHub](https://github.com/VectifyAI/pageindex-mcp): Source for the MCP server package.
- [MCP setup docs](https://docs.pageindex.ai/mcp): Client configuration and authentication details.

## CLI

The MCP server also runs locally as a command-line tool, published on npm as
`@pageindex/mcp` with the `pageindex-mcp` binary (Node.js 18 or newer). It
speaks MCP over stdio, so any MCP client can launch it directly, and unlike the
remote
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=pageindex.ai · GET /v1/domain/pageindex.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for pageindex.ai:
1. POST https://agentwebmap.com/v1/sites/pageindex.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://pageindex.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/pageindex.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pageindex.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.