Publish your knowledge as a bot.

Open Bots, choose New bot, and give the Bot:

• Knowledge — one or more Library folders it answers from. The Bot only knows what is in those folders, which keeps answers grounded and citable.
• Instructions — optional saved prompts that set tone, scope, and rules (for example: "answer only from the docs; if unsure, point to the contact page").
• Model — the AI model that powers it.

Name the Bot, save it, and test representative questions before connecting a Channel. Updating the selected folders or prompts updates every connected Channel without recreating it. Your signed-in model picker is the authority for models available to your plan; see the live model and credit catalog for public cost guidance.

Telegram

1. In Telegram, open BotFather, create the Telegram bot identity, and copy its token.
2. In Keldura, open Telegram, choose Create bot, paste the token, and link the reusable Keldura Bot that should answer.
3. Set the welcome message, suggested questions, access rules, rate limits, and group behavior you need; then enable and test the Channel.

Keep the BotFather token secret. If the bot must read ordinary group messages, adjust privacy mode in BotFather and remove/re-add it to an existing group so Telegram applies the change.

Website widget

The Website widget page embeds a chat on a site you control (requires an eligible paid subscription):

1. Choose Create widget. Use the default guided setup, or the advanced option to link an existing reusable Bot.
2. Add the allowed domains. The widget refuses to load on unlisted sites.
3. Choose the inline or popup presentation, preview it in Light and Dark themes, then enable and save it.
4. Copy the generated script or iframe snippet into your site.

Visitors can then ask questions right on your page and get answers grounded in your content.

MCP and the developer API

MCP and the Developer API read your account Library directly; they do not expose or connect through a saved Bot.

1. Create a named key in Settings > API Keys, optionally set an expiry, and copy the secret from its one-time display.
2. For MCP, open MCP, choose your client, and copy its connection snippet. The client discovers the current owner-scoped tool catalog through tools/list.
3. For REST endpoints, examples, the interactive reference, and OpenAPI files, open the Developer API documentation.

Treat API keys like passwords and deactivate a key when it is no longer needed.

Keldura uses the same pattern described here: public help pages are kept as the durable source, synchronized into a support Library, and selected as knowledge for a reusable support Bot. The Website widget or Telegram Channel connects to that Bot.

After an updated public page is successfully synchronized and indexed, the support Bot can answer from the new guidance. That is why feature changes affecting indexed help must update the governed facts and public documentation in the same issue and pull request.