knowhere

Overview

Knowhere is the memory layer between complex, dirty documents and AI agents.

It ingests unstructured documents and produces persistent, navigable memory: parsing, hierarchy extraction, multi-modal structuring, and graph construction in a single pipeline. Every chunk retains full semantic context, making the output a natural fit for Agentic RAG, vector-based RAG, or any LLM workflow.

[!NOTE] Get started in seconds with Knowhere Cloud. Avoid the complexity of self-deployment. Use our managed API at knowhereto.ai and enjoy $5 in free credits upon registration.

📢 News

• June 1, 2026: 📚 Knowhere now supports ultra-long PDFs and atlas-style documents. The parsing pipeline can process long-form PDFs with hundreds of pages (for example, 300, 500, or more) and route technical atlases or drawing collections through a dedicated layout-aware parser.
• May 7, 2026: 🚀 Knowhere is now Open Source! We have open-sourced our entire stack for document ingestion, parsing, and agentic RAG. You can now self-host the full platform using knowhere-self-hosted. Check out our Contribution Guide to get involved!

How it Works

Knowhere runs in two steps: build memory from documents, then let agents retrieve from it.

Step 1: Parse and Build Memory

• Parse: Route PDFs, Office files, images, tables, Markdown, and text to specialized parsers.
• Structure: Our proprietary Tree-like algorithm reconstructs the full document hierarchy instead of flattening it into a sequence, preventing semantic fragmentation across chunks.
• Build Memory: Store chunks, navigation trees, summaries, and graph links as agent-ready context.

Step 2: Agentic Retrieval

• Discover: Fuse keyword, path, content, and semantic signals for broad first-pass coverage.
• Navigate: Walk section trees and graph links to drill into the most relevant document regions.
• Cite Evidence: Return traceable results with source document, section, chunk, and linked assets.

FAQ

Q: What is Knowhere's relationship with MinerU?

A: Knowhere uses MinerU as its default parser because it performs best in our tests. Any parser only gets you raw Markdown. Knowhere's value is what comes after: hierarchy reconstruction, multi-modal normalization, and cross-document graph construction. Any Markdown-outputting tool works.

Q: What LLM / VLM dependencies does Knowhere have?

A: By default, DeepSeek (deepseek-chat) handles text and table summarization, and Qwen-VL (qwen3.6-flash) handles image OCR and descriptions. Knowhere is model-agnostic. Swap in OpenAI, DashScope, Zhipu, or Volcengine via environment variables.

Q: How is Agentic Retrieval different from traditional RAG?

A: Traditional RAG does a flat vector lookup and returns isolated snippets. Knowhere's agents navigate the document's section tree and cross-document graph, drilling into the most relevant regions the way a human reader would, returning traceable, well-contextualized evidence.

Q: Does it handle images and tables?

A: Yes. Knowhere extracts them, runs them through VLMs for summarization and feature extraction, and links them back to their source chunks so agents can retrieve and cite multi-modal assets at inference time.

Performance Benchmark

Agents using Knowhere outperform those working from raw documents, Markitdown, Unstructured, or MinerU output on real-world tasks: searching, modifying, and answering questions.

We're not developing the next MinerU — we're building document memory infrastructure that agents can effectively consume.

Key Advantages

• Accuracy: +36% first-try accuracy and +11% recall over raw documents.
• Reliability: 79% accuracy with feedback, vs. a ~53% ceiling on raw docs.
• Efficiency: Fewer loops, fewer tokens, less time. Agents navigate a structured graph instead of reading monolithic text.

(Internal evaluation across identical agentic RAG tasks. Baselines: raw documents and parser output fed directly to agents.)

[!NOTE] 📊 Benchmarks are actively expanding. More parsers and retrieval baselines coming soon.

Ecosystem

Features

• Multi-modal Parsing: High-fidelity extraction from PDF, Office, and images, preserving headings, tables, and hierarchical paths.
• Lightweight Memory Graph: Context-aware organization that links documents and chunks for better relationship understanding.
• Agentic RAG: A hybrid retrieval engine combining traditional search (RRF) with autonomous agent navigation.
• Evidence-based Citations: Every result is backed by traceable source paths, ensuring reliability for AI Agent decision-making.

Supported Formats

✅ Supported

• .pdf .docx .pptx .xlsx .csv
• .jpg .png
• .md .txt .json

⏳ Coming Soon

• .epub .html .xml
• .mp4 .mp3
• .skills.md

Want to see a new format supported? Adding a parser is a great first contribution. Check out CONTRIBUTING.md to get started.

Prerequisites

• Python 3.11+
• uv
• Docker with docker compose

Quick Start

1. Sync the workspace dependencies:

uv sync --all-packages

2. Copy the environment examples:

cp apps/api/.env.example apps/api/.env
cp apps/worker/.env.example apps/worker/.env

3. Update the copied .env files with the values you need for local work:

• database and Redis connection settings
• S3-compatible storage credentials
• at least one LLM provider key: DS_KEY, ALI_API_KEYS, GPT_API_KEY, or GLM_API_KEY
• MINERU_API_KEYS if you need PDF parsing
• a vision-capable model provider if you need image summaries, OCR, atlas classification, or image-aware retrieval
• any optional billing or webhook providers you want to enable

Most parser and retrieval tuning values have code defaults. Start with the required external services first, then override model names, provider URLs, budgets, or concurrency limits only when your deployment needs different behavior. See docs/external-services.md for the full dependency matrix.

4. Start the local infrastructure stack:

./deploy/local-dev/start-dev.sh

5. Start the API and worker in separate terminals:

cd apps/api && uv run main.py
cd apps/worker && uv run worker.py

Run API migrations explicitly before starting the API when the database schema needs updating:

cd apps/api
uv run alembic upgrade heads

For API-only development without the dashboard, create an API-only user/key after the API service starts:

cd apps/api
uv run scripts/init_user.py --email you@example.com

If you plan to use the dashboard, register through the dashboard instead of using scripts/init_user.py.

The API is now running at http://localhost:5005. If you want the full prod