Cabi.Chat Ignite

Cabi.Chat Ignite is the graph's conversation engine. Radar finds; Ignite speaks. Every oracle reply, widget answer, first contact and LLM translation is one Ignite run: your instructions, the live conversation and the tools you granted. No script, no canned replies.

What runs on it

Telegram account oracles and bot oracles. Cabi.Chat Oracles — Telegram account oracle Cabi.Chat Oracles — Telegram bot oracle
The website widget. Cabi.Chat Oracles — Website widget
The reply to a public request found by Radar, written by the same agenda that continues the chat. link Cabi.Chat Campaigns
Card translation with your own translation agenda. Cabi.Chat Graph — Languages and translation

Every run follows an agenda: Cabi.Chat Ignite — Agendas

The turn. Messages a person sends in quick succession are read and answered together, as one turn. Inside a turn the model works step by step: it reads, looks things up, calls tools and sends its answer through the surface's send tool. A turn may also end in silence when nothing should be said. What it can call: Cabi.Chat Ignite — Tools, endpoints and secrets Which model runs it: Cabi.Chat Ignite — Models and AI usage

Notes about the person. Ignite keeps short notes on each conversation: name, city, what the person wants, what was promised. They are read on every next turn, belong to that one conversation and are used nowhere else. A person can ask for them to be deleted, and the oracle can clear them.

Mentioned

Cabi.Chat Radar · Article — Cabi.Chat Radar is the graph's intent detection infrastructure. Seekers ask, offerers answer, and the radar is how a project finds the asks: it finds public messages in public Telegram groups where pe

Cabi.Chat Ignite — Agendas · Article — An agenda is the oracle's mind, kept as a card. Cabi.Chat Ignite turns it into the agent's prompt on every reply: the instructions you wrote, the tools you allowed, the keys those tools may use and th

Cabi.Chat Campaigns · Article — Cabi.Chat Campaigns are the graph's executables. A project does not only wait to be found; it acts through campaigns. A campaign belongs to a project, runs on that project's oracles, and does one job

Cabi.Chat Oracles — Telegram account oracle · Article — A Telegram account oracle is your own phone-backed Telegram account with an AI assistant that writes on your behalf. It answers whoever writes to it and does the account's work in campaigns. []( https

Cabi.Chat Oracles — Telegram bot oracle · Article — A Telegram bot oracle is your own Telegram bot with an oracle behind it. Anyone who opens the bot and writes to it talks to your project, and the bot answers from your agenda. Set it u

Cabi.Chat Oracles — Website widget · Article — A website widget is an oracle that lives on your own site or in your app: a visitor types a question, and the oracle answers from your project's graph. Two hosting modes Platform

Cabi.Chat Ignite — Tools, endpoints and secrets · Article — An oracle acts only through tools you grant it. Talking is one tool among many: sending a message, booking a slot, checking an order, creating a lead in your CRM are all calls the oracle makes. Cabi.C

Cabi.Chat Ignite — Models and AI usage · Article — Every oracle reply is an LLM run, and you choose the model. The model is set per agenda, so one oracle can answer on a fast, cheap model while a campaign's first contact runs on a stronger one. []( ht

Cabi.Chat Graph — Languages and translation · Article — Every card speaks several languages. Each language is its own version of the card: title, teaser and text. One of them is canonical : the original the others are translated from, and the one shown whe