Where both of them live
A knowledge base and a documentation set are both content your customers can read and your AI can answer from, and both sit on the same screen: Brand → Knowledge. The upper table lists every one your brand owns (see what a brand is in Yaplet).
Publishing an article or a page is what makes it readable by your AI. There is nothing to connect first — no AI agent and no chat widget are needed for that part.
Two tools, two jobs
- Knowledge base — rich-text help articles written for end-users. Visitors reach them from the Help tab inside your chat widget and from your brand's public web address. Every article you publish is added to your AI's knowledge.
- Documentation — long-form, markdown-based pages aimed at developers or power users. Served at its own path on the same web address, and not listed in the widget's Help tab. Documentation is a paid add-on module at 19 US dollars a month, so a brand-new account does not have one.
If you are wondering which to open first, the answer for most teams is: start with the knowledge base. You can add documentation later, when you have technical content that needs structured, code-heavy formatting.
Use the knowledge base when…
- Your audience is an end-user — someone who bought your product and needs help using it.
- You want the article to be reachable inside the chat widget (the Help tab).
- The content is conversational: "How do I reset my password?", "What does X button do?"
- You want your AI to answer visitor questions from the article automatically.
- Articles are short to medium length with images, bullet points, and step-by-step instructions.
Use documentation when…
- Your audience is a developer or system administrator.
- The content is structured and technical: API references, SDK guides, configuration manuals.
- You need code blocks with a language label, MDC components like callouts and steps, or deeply nested page hierarchies.
- You are fine with a separate public page — documentation does not appear in the widget's Help tab, though the tab can carry a link to it.
Key differences at a glance
| Feature | Knowledge base | Documentation |
|---|---|---|
| Editor | Rich-text | Markdown with MDC components |
| Primary audience | End-users | Developers / technical users |
| Included in a new account | Yes | No — a paid module at 19 US dollars a month |
| Widget Help tab | Yes — the articles are listed and searchable there | No — but the tab can show a link to it |
| Read by your AI | Yes — the moment an article is published | Yes — the moment a page is published |
| Public web address | Yes, at /k/ |
Yes, at /d/ |
| Ask the AI on the public page | No — search only | Yes — visitors can chat with an AI that answers from your pages |
| Languages | One article per language, translated one by one | One language per documentation set |
Can I use both?
Yes — and many teams do. A common setup is a knowledge base for customer support articles and documentation for an API reference or integration guide. They are independent of each other, and one of each can be on your brand's public web address at the same time.
To get started, pick the one that matches your first piece of content. If you need help articles for your end-users, create your first knowledge base article. If you are building a developer reference, set up your documentation site.