The knowledge base holds what only you know: pricing sheets, product specs, case studies, positioning, the pages of your own site. Every article for the brand draws on it, cites it, and has each fact it took from it checked against the passage it came from.
Go to Content > Knowledge base in the sidebar. It is per brand: switch brands to see another brand's.
Click Add knowledge and pick one:
Add | What happens |
|---|---|
Upload files | PDF (every page), Word (.docx), Markdown, plain text, CSV (each row keeps its column names) and images (described by AI). Up to 10 MB each, several at once. You can also drop files straight on the list. |
Web page | Paste an address and the page is read. Choose Keep it fresh to read it again every 7, 30 or 90 days, so a changed price reaches the next article. |
Site section | Pick a section of your own site (for example |
Note | Type or paste the facts with a title. |
Each item shows Reading while it is read and split into passages (usually seconds, up to a minute for a long PDF), then Ready. A Failed item says why when you hover it: no text found, a file that could not be read, a page that did not load, or a file over 10 MB. Use Read again from the row menu to retry, or to pick up a page that changed.
Adding to the knowledge base is free on every plan.
Before the outline, the passages closest to the article's keyword and topic are picked: up to eight, by meaning and by the words they share.
The writer gets them with the brand's facts and cites them where they fit. Facts from your knowledge base need no outside link.
After editing, every sentence taken from a passage is checked: its numbers and names must be in that passage. When two items disagree on a number, the one with the later Facts true as of date wins, and the article notes the conflict.
The article's quality panel shows how many passages it cited, and flags facts that do not match their passage and passages that disagree.
Nothing about this reaches your published article: the marks are removed before it is saved.
By default every article draws on the whole knowledge base (Auto). Through the API, a brief can limit it to the items you pick or turn it off for that article (content_context.knowledge).
In use: turn an item off to keep it listed but out of every article (an old price list, for example).
Open an item to rename it, tag it, set Facts true as of (the date its facts held), change how often a page is read again, and see the passages articles retrieve from it.
Try a search shows the passages an article about a topic would draw on, best first. Use it to check the knowledge base knows what you think it knows.
Delete removes the item, its passages and its stored file. Articles already written keep their text.
Search the list by title or address and filter it by status.
What | Who |
|---|---|
See the knowledge base and try a search | Anyone with access to the brand |
Add, change and delete items | Editors |
Articles that use it need the brand owner on Starter or higher.
The knowledge base is in the public API at /v1/brands/{brand_id}/knowledge-base: list, add notes and pages, upload files (/files), change, delete and search (/search). The agent and the MCP server can search it (search_brand_knowledge).
Brand voice: how the articles sound. Learning the voice from your site also adds the posts it read to the knowledge base.
