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.
OPENAI_API_KEY before running the example. ChromaDB uses Agno’s default OpenAI embedder when no embedder is supplied.
Next Steps
Search & Retrieval
How agents search and find information in your knowledge base
Readers
Explore content parsing and ingestion options in detail
Chunking Strategies
Optimize how content is broken down for better search results
Vector Databases
Choose the right storage solution for your knowledge base