Skip to main content

​
What it is for

The knowledge base gives the agent a retrieval layer for the content your users should rely on when they ask product questions. Good examples:
  • product documentation
  • onboarding guides
  • help center articles
  • policy documents
  • a public docs site or help center

​
What the user experience looks like

  1. Upload documents or add a public website.
  2. Wait for processing to finish.
  3. Enable the knowledge base.
  4. Warpy starts using those sources in answers.
You can turn the knowledge base on before the first source is ready. Warpy starts grounding answers as soon as processing finishes. New agents start with the knowledge base enabled by default. If onboarding added your first website, Warpy already turned the knowledge base on for you.

​
Websites

You can add a public website instead of uploading files.
  • Enter a domain like docs.example.com or a specific path like docs.example.com/help.
  • Warpy reads every page under that website or path.
  • The website must be publicly accessible.
  • Private, internal, and localhost-style addresses are not supported.
  • Warpy follows page links and sitemap files, which helps with JS-heavy docs sites too.
  • Warpy reads the full cleaned page content under that website or path, including card and grid content and meaningful pricing or option values that are embedded in page controls.
  • You can open the website view at any time to see page-by-page progress.
  • Warpy checks websites again weekly so removed pages disappear, new pages are added, and changed pages stay fresh.
  • You can also trigger a refresh manually when the website is idle.

​
Processing pipeline

Upload document or add website
  -> Read content
  -> Section-aware chunk content
  -> Create embeddings
  -> Store in pgvector

User question
  -> search_knowledge_base
  -> combine semantic + lexical + source matching
  -> rank source-aware evidence
  -> grounded answer
For websites, Warpy keeps the full cleaned page text but chunks it around real page sections so factual answers like pricing, limits, support tiers, policies, and integrations are easier to retrieve accurately.

​
Best practices

Website sources must be reachable without a login.

Add the product docs or help center your users should actually rely on.

If you only want a docs section, add that path instead of the whole domain.

Turn it on when you want, then test a few real questions once your first source finishes processing.

​
Operational details

  • The page auto-polls while documents or websites are still processing.
  • Website detail shows each page and whether it is ready or failed.
  • Removing a website stops future refreshes and removes its content from the knowledge base.
  • Ready documents can be previewed in the app.
  • Uploading documents or adding websites may be blocked on plans with no remaining actions.

​
When to use it

Use the knowledge base when the agent should answer:
  • “How do I do this?”
  • “Where is this setting?”
  • “What does this policy mean?”
  • “What does the docs site say about this?”
Use tools when the user wants Warpy to actually perform the action.