Cabi.Chat Ignite — Tools, endpoints and secrets
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.Chat Ignite decides when to call; your agenda decides what can be called. link Cabi.Chat Ignite — Agendas
Base tools. Every oracle gets them from the platform:
- send — answer on its surface: Telegram account, bot or widget;
- hand over to a human — mark the conversation for you, with the reason Cabi.Chat Inbox — Human handoff;
- end the conversation — stop answering a person who should not be answered;
- look — see a photo sent in the conversation and ask a vision model what it shows, again with another question when needed;
- timer — come back to the conversation later, once or repeating;
- notes — write and clear the short notes on the person link;
- history — page back to older messages of the conversation.
Endpoints. Anything else is an API endpoint card: a method, a path, a domain, an operation name, a description, and request and response schemas. The oracle can call only the endpoints listed in its agenda. It searches them by plain words, reads the full schema of the one it needs, and calls it. A workspace of endpoints works as a toolbox: its description tells the oracle what the whole set is for.
Secrets. Keys are secret cards. A secret has a name (secret_ followed by lowercase letters, digits and underscores), a value, and the host it belongs to.
- The value is write-only: it is never shown again, never returned by the API, never seen by the model. To rotate, delete the secret and create a new one.
- A key is only ever sent to the host it is bound to.
- A secret must sit in a workspace. List it in the agenda, and the platform injects it into the calls at call time.
- Delete a secret, and every agenda that used it reloads at once.
When a call fails. Each call has a time limit. A host that cannot be reached is skipped for the rest of the turn, while the reply can still be sent. A send whose delivery is unknown is never repeated: the oracle is built to avoid duplicate messages.