The Knowledge Base is the foundation of your agent’s knowledge. By adding approved source material — documents, websites, curated Q&A pairs, and text snippets — you give your agent the content it needs to provide accurate, evidence-based responses grounded in your own materials rather than general AI knowledge.Documentation Index
Fetch the complete documentation index at: https://docs.roserx.ai/llms.txt
Use this file to discover all available pages before exploring further.
Access the Knowledge Base by selecting an agent from the Agents list and clicking the Knowledge Base tab.
How it works
When a user asks a question, the RoseRx Platform retrieves relevant information from your Knowledge Base in two stages:- Q&A pair lookup — The platform first checks whether the question semantically matches one of your curated Q&A pairs. If a confident match is found, the exact pre-approved answer is returned to the user.
- Document retrieval (fallback) — If no Q&A match is found, the platform searches your PDFs, URLs, and text snippets using Retrieval-Augmented Generation (RAG). The most relevant chunks are passed to the AI model as context, and the model generates a grounded response.
Source types
You can add four types of source material to your Knowledge Base. Each is suited to different content and behaves differently at runtime.PDF documents
Upload PDFs such as prescribing information, clinical study reports, product information leaflets, and approved marketing materials.
Website URLs
Add web page URLs to scrape and index content from your existing websites, product pages, or online resources.
Q&A pairs
Define a question and an exact, pre-approved answer. When a user’s question matches semantically, the answer is returned verbatim.
Text snippets
Paste free-form text — paragraphs of product information, policy excerpts, or supporting context — for the agent to reference.
At a glance
| PDF documents | Website URLs | Q&A pairs | Text snippets | |
|---|---|---|---|---|
| Best for | Long, authoritative source material (PI, CSR, leaflets) | Existing public web content you don’t want to duplicate | Canonical, pre-approved answers to common questions | Free-form context that doesn’t fit a single question/answer |
| Format | PDF file (≤ 10 MB) | Public URL | Question + answer | Plain text (≥ 100 characters) |
| How it’s used | Chunked, embedded, retrieved as context | Scraped, chunked, embedded, retrieved as context | Returned verbatim when the question matches | Chunked, embedded, retrieved as context |
| Processing | Asynchronous indexing | Asynchronous indexing | Available immediately | Asynchronous indexing |
| Retrieval priority | Fallback after Q&A lookup | Fallback after Q&A lookup | Checked first | Fallback after Q&A lookup |
Uploading PDF documents
Select your file
Click the upload area or drag and drop a PDF file. The file must be in PDF format and no larger than 10 MB.
Add metadata
Fill in the document details:
- Name — A descriptive name for the document
- Author — The document author or organization
- Publication date — When the document was published
- Therapeutic area — The relevant therapy area
- Source type — The category of the document
Adding website URLs
Enter the URL
Paste the full website URL you want to index. The page content will be scraped and processed.
Add metadata
Fill in the source details — name, author, publication date, therapeutic area, and source type — just as you would for a PDF.
Adding Q&A pairs
A Q&A pair is a curated question with an exact, pre-approved answer. When a user asks a question that semantically matches yours, the platform returns your answer verbatim — no model paraphrasing.Open the Q&A pair sheet
On the Knowledge Base tab, click Add Q&A Pair. A creation sheet will appear.
Write the question
Enter the question the way a user would naturally ask it. The question is what the platform matches against — phrasing matters.
Write the answer
Enter the exact answer you want returned. This text is shown to the user as-is, so use the wording you would approve for any other communication.
Only the question is embedded for semantic matching. If users phrase the same question in significantly different ways, consider adding multiple Q&A pairs covering each phrasing.
Adding text snippets
Text snippets are free-form passages of text — a paragraph from a leaflet, a policy excerpt, a section of product information — that the agent can reference when answering questions.Open the text snippet sheet
On the Knowledge Base tab, click Add Text Snippet. A creation sheet will appear.
Add optional metadata
Set a source (where the content came from) and a category if you want to organize your snippets.
Q&A pairs vs text snippets
These two formats often overlap in subject matter, but they behave very differently. Use this guide to choose the right one. Use a Q&A pair when:- You want a single, canonical answer returned word-for-word.
- Wording is high-stakes — regulatory, legal, brand, or scripted.
- The content fits naturally as one question and one answer.
- You want the answer returned even if surrounding documents don’t contain it.
- The information is a paragraph or section that the agent should weave into responses with surrounding context.
- The same content might be relevant to many different questions.
- You want the agent to summarize, quote, or combine the snippet with other sources.
- The content doesn’t fit neatly as a single question/answer.
Document processing pipeline
After you add a PDF, URL, or text snippet, it moves through a processing pipeline. Q&A pairs are not part of this pipeline — they are stored and matched directly without chunking.| Status | Description |
|---|---|
| Pending | The source has been submitted and is queued for processing. |
| Processing | The source is being chunked, embedded, and indexed. |
| Indexed | Processing is complete. The source is now available to your agent. |
| Error | Something went wrong during processing. Check the source and try again. |
The Knowledge Base page automatically checks for status updates every 5 seconds while sources are processing. You’ll receive a toast notification when indexing is complete.
Managing sources
Once a source is indexed (or, for Q&A pairs, saved), you can manage it from the Knowledge Base list:- Edit — Update the question and answer, the snippet content and metadata, or the document name and metadata.
- Reindex — For PDFs, URLs, and text snippets, trigger reprocessing if the underlying content has changed. (Q&A pairs are re-embedded automatically when the question is edited — no manual reindex needed.)
- Delete — Permanently remove the source from the Knowledge Base.
Best practices
Choose authoritative sources
Choose authoritative sources
Use Q&A pairs for high-stakes phrasing
Use Q&A pairs for high-stakes phrasing
When wording is regulated, branded, or otherwise must not be paraphrased, write a Q&A pair. The exact answer is returned to the user verbatim — the model does not rewrite it.
Keep snippets focused
Keep snippets focused
A text snippet should cover a single topic. Tightly scoped snippets produce more coherent chunks, which leads to more accurate retrieval and cleaner responses.
Cover the way users actually ask
Cover the way users actually ask
Q&A pair matching is semantic but not magic. If the same question is asked in very different ways, consider adding a Q&A pair for each phrasing.
Keep documents up to date
Keep documents up to date
When product information changes (new indications, updated safety data, revised labeling), update or replace the relevant sources in your Knowledge Base promptly.
Use descriptive metadata
Use descriptive metadata
Accurate metadata helps you manage a growing knowledge base. Use clear, consistent names and always specify the therapeutic area and publication date.
Monitor for errors
Monitor for errors
Check back after adding a PDF, URL, or text snippet to confirm it reaches Indexed status. If a source shows an Error status, review it and re-add or reindex if needed.

