Knowledge Vault
Knowledge Vault
The Knowledge Vault is the brand memory Compose and the rest of the product already use. These endpoints read and manage the same sections you see in the vault.
What an entry is
Open Knowledge Vault in the product and you see a row of sections: Offers & pricing, Proof & results, Customer stories, Objections & FAQs, Positioning, and Additional context. Each saved card in one of those sections is an entry. It has a title, a short summary, the full write-up, and optional tags.
The API calls the section id pillarId. You never invent that id. Sections lists the six you can write, with the same names the product shows. offers is Offers & pricing. There is no second label to pick.
What stays in the product
Three parts of the vault are not entries, so this API does not create them. Industry categories, Business & audience, and Voice & guardrails are edited on their own screens. Voice rules apply to every draft whether or not a search finds an entry.
An empty section in the product can show a sample card, so you can see the shape of a good entry. Those samples are not your content. List, read, update, and delete skip them.
Reading is free of AI tokens
Listing entries and reading one entry are ordinary requests. They return the full write-up, so you can edit it or show it in your own tool. Search is different: it looks for the entries that answer a question, and that spends AI tokens. Adding an entry, or changing its text, tags, or section, also spends tokens while we index it for later search. If indexing cannot run, the entry is still saved and indexed is false. You can still list it.
Guides
- Sections — the six places an entry can live
- Entries — list, read, add, update, and delete
- Search — ask a question across the vault
OpenAPI: /openapi/knowledge-v1.yaml