A Knowledge Base is a searchable index of unstructured content — PDFs, markdown docs, text files, scraped pages, transcripts. Agents query knowledge bases when they need authoritative context that’s specific to your business.Documentation Index
Fetch the complete documentation index at: https://docs.hyperfx.ai/llms.txt
Use this file to discover all available pages before exploring further.
When to use this
Use a knowledge base when you have a body of content that doesn’t change minute-to-minute but matters for a lot of agent work:- Brand voice and style guides — every piece of content the agent generates should follow these
- Internal wikis and SOPs — how your team does things
- Customer research and persona docs — so agents can ground recommendations in your actual ICP
- Product documentation — so support and sales agents can answer questions accurately
- Past campaign post-mortems — so the next campaign benefits from what you learned
Creating a knowledge base
Name and describe it
Give it a clear name (e.g. “Brand Guidelines”, “Product Wiki”, “ICP Research”) and a description telling agents when to use it. The description matters — agents read it before deciding to query.
Add content
Upload files (PDFs, markdown, txt, docx, csv) and/or paste URLs to scrape. Hyper indexes everything for semantic search.
How agents use knowledge bases
When an agent has a knowledge base attached, it can:- Search — “Find what our brand guidelines say about tone for paid ads”
- Cite — return specific passages so you can verify the source
- Compose — pull excerpts into reports, drafts, and analyses
Updating content
Knowledge bases are meant to live and grow. Add new files anytime; remove or update old ones. Re-indexing is automatic — content is searchable within minutes of being added. If the underlying content changes a lot (e.g. live product docs), consider:- Re-uploading files on a schedule via a task
- Pointing a scraper task at the source URLs and refreshing weekly
Going further
- For structured data, use Hyper Database
- To turn knowledge-base outputs into shared dashboards, see Interfaces
- To attach a single file to a single chat instead of creating a knowledge base, see Files