No. SleekAI is configured to ground every API answer in your published docs. If an endpoint, header, or parameter is not in the live reference, the bot says so honestly rather than inventing one. For developer audiences this is critical; an invented endpoint is the fastest way to lose technical trust, and the system prompt explicitly disallows fabrication of API surface area not in the docs.

Yes. SleekAI reads your docs' code blocks as separate content and can quote them in chat replies with their language and formatting preserved. For inline code, the bot uses the standard code formatting from the chat UI. Developers can copy-paste the snippet from the chat reply just as they would from the docs page itself.

Yes, if the field is in your reference. SleekAI reads your API reference (whether OpenAPI-generated or hand-written) and can quote field names, types, defaults, and notes. For developers building against the API, this is faster than ctrl-F across a long reference page, and the bot can include the relevant request example alongside the field description.

If your docs are versioned in WordPress (separate posts per major version, or version metadata on each post), the bot can scope to a version on request. We recommend tagging each docs post with its version so the bot does not quote v2 docs to a v1 user. For sites with only one current version, this is not a concern.

Yes. SleekAI supports multibot, so the admin docs, API reference, and SDK docs can each run their own chatbot scoped to that section. Each starts with its own initial message and presets, matched to the audience. For docs spanning admin, developer, and partner audiences, the per-section bot keeps each conversation focused and the answers grounded in the right reference.

It complements rather than replaces. SleekAI is an answer layer in front of the docs; the docs search remains useful for power users who want a list of pages. The chatbot is most useful for one-shot questions and for users who want an answer in their own terms rather than a search-result page. Many sites run both in parallel with display conditions keeping the chatbot off pure-reference index pages.

SleekAI is a one-time WordPress plugin license. You bring your own OpenAI, Anthropic, Google, or OpenRouter API key, so usage cost is just the tokens, typically a few cents per conversation. Docs pages tend to attract high-volume traffic from developers, but the conversation length is usually short (one or two questions before they have what they need), so the per-page cost stays low.

Only published docs feed the bot. SleekAI does not read drafts, private posts, or internal-only post types unless explicitly configured to. We strongly recommend keeping internal docs in a separate post type with the bot scoped only to published docs. The system prompt is configured to refuse requests for content not in scope, which keeps the surface area clean.