Knowledge Content Types

Agno Knowledge uses Content as the record for each knowledge source. Content can be added to knowledge from different sources.

Knowledge content needs to be read and chunked before it can be passed to the vector database for embedding, storage, and retrieval. For supported file and URL types, Knowledge selects a reader from the file extension or content type. Raw text uses the text reader. Topic ingestion requires an explicit reader such as ArxivReader or WikipediaReader. Readers parse content from the origin and chunk it into smaller pieces that are then embedded and stored in the vector database.

To override the default reader or its settings, pass a reader when adding content. The example below creates a PDFReader with a custom chunk_size. Other parameters like chunking_strategy work the same way and control how content is ingested and processed.

uv pip install -U agno chromadb openai pypdf

Set OPENAI_API_KEY before running the example. ChromaDB uses Agno's default OpenAI embedder when no embedder is supplied.

import asyncio

from agno.knowledge.knowledge import Knowledge
from agno.knowledge.reader.pdf_reader import PDFReader
from agno.vectordb.chroma import ChromaDb

reader = PDFReader(
    chunk_size=1000,
)

knowledge_base = Knowledge(
    vector_db=ChromaDb(
        collection="pdf-content",
        path="tmp/chromadb",
        persistent_client=True,
    ),
)

asyncio.run(
    knowledge_base.ainsert(
        path="data/pdf",
        reader=reader
    )
)

See Readers for the available readers and their capabilities.

Next Steps