Cabi.Chat Oracles — kinds and setup
An oracle talks for your project. Pick its kind by where people should meet it and who should write the answers. What an oracle is: Cabi.Chat Graph — Oracles™
Three kinds, four setups
| Telegram account | Telegram bot | Cabi.Chat widget | Cabi.Chat widget, self-hosted | |
|---|---|---|---|---|
| People meet it | in Telegram, writing to the account | in Telegram, opening the bot | in Cabi.Chat rooms | in Cabi.Chat rooms |
| Who answers | Cabi.Chat's AI, as the account | Cabi.Chat's AI, as the bot | Cabi.Chat's AI, as the widget | your own program, as the widget |
| Its token | none: you sign the account in | your token from @BotFather | made by Cabi.Chat, kept by Cabi.Chat | made by Cabi.Chat, shown to you once |
| Agenda | required | required | required | optional |
| AI cost | your balance | your balance | your balance | your own AI; nothing from Cabi.Chat |
| Needs | a Pro project | your free oracle slot or a Pro project | your free oracle slot or a Pro project | your program running on your machine or server |
Only a Cabi.Chat widget can be self-hosted. Prices and the free slot: Cabi.Chat Pricelist
Token and agenda
- The token belongs to the oracle. A bot's token and a platform-hosted widget's token are kept on the oracle card, encrypted: never returned by the API and never seen by the model. A self-hosted widget's token is shown to you once, when it is made; Cabi.Chat cannot show it again. Deleting the oracle removes the token.
- A new token: a bot takes a new token of the same bot; a widget gets a new one from Cabi.Chat, and the previous one stops working.
- The agenda is behaviour only: instructions, API endpoints and the keys for third-party APIs those endpoints call. Never put an oracle's own token into an agenda. Cabi.Chat Ignite — Agendas
- One agenda can run several oracles; changing it changes all of them from their next answer.
Who pays for AI
Every answer Cabi.Chat's AI writes is paid from the balance of the agenda's owner: you, when it is your agenda. When the balance cannot pay, the oracle does not answer. A self-hosted widget runs no Cabi.Chat AI: your program uses its own. Your spend: API pipeline: See your AI spend
Who can reach it
- Telegram account and bot: anyone in Telegram who writes to them. The oracle card's visibility only decides who sees the card on Cabi.Chat.
- Cabi.Chat widget: only people who can read the widget card. Visibility, sign-in and what happens to rooms when access ends: Cabi.Chat Oracles — Cabi.Chat widget
Set it up
Every oracle is created stopped. You start it, stop it and delete it at any time; its conversations land in your Rooms.