Cabi.Chat

Cabi.Chat is the marketing layer behind your social reach, built on an open graph of knowledge. Your project gets found, answers for itself and brings leads. Why a feed is not enough: The marketing layer your Telegram is missing · topic by topic: Why Cabi.Chat - articles

Who it is for

What you get

Pricing

A project is Free until you make it Pro: Cabi.Chat Projects — Pro · prices Cabi.Chat Pricelist · top up How to make a deposit on Cabi.Chat

Start

2 contact channels (website, telegram) — sign in on the project page to reveal.

Article

Cabi.Chat — Start here

New to Cabi.Chat? Here are the first steps, one line each, with the card that explains each one. What Cabi.Chat is: Cabi.Chat

How a person does each step in the web app: FE pipelines — index. The same steps as API calls, for your scripts and your AI: API pipelines — index

First steps

  1. Post a project. Say what you offer, for whom, where and at what price; only the title is required. Cabi.Chat Projects — Create a project
  2. Shape it. Anchor articles, posts and workspaces to the project and link them, so it is known by what it knows. Cabi.Chat Projects — Shape the image.
  3. Decide who sees what. Set each card Private, Unlisted or Public. Cabi.Chat Graph — Card Policies.
  4. Get found. Search, the map and the landing are where people find projects. Cabi.Chat Search, Cabi.Chat Landing, Cabi.Chat Search — Geo filter and preference
  5. Let it answer. Assign an oracle that answers for the project in Telegram or on your site. Cabi.Chat Graph — Oracles™, Cabi.Chat Ignite
  6. Act first. On a Pro project, campaigns find people who ask for what you offer and post where group rules allow. Cabi.Chat Campaigns, Cabi.Chat Radar, Cabi.Chat Announcements
  7. Work the leads. Every conversation lands in your inbox; step in when the oracle hands one to you. Cabi.Chat Inbox
  8. See what works. Count the visits and the links that brought them. Cabi.Chat Analytics — Visits and traffic sources

How the graph works

Also inside

Cabi.Chat Graph — Oracles™

An Oracle™ is an AI agent assigned to your project's hotspot. It carries that knowledge and answers for it on your behalf, grounded in the graph and serving your goals. What a hotspot is: Cabi.Chat Projects — Shape the image.

One oracle, three kinds. The oracle is the knowledge carrier; the kind decides where people meet it and who writes the answers: your Telegram account Cabi.Chat Oracles — Telegram account oracle, your Telegram bot Cabi.Chat Oracles — Telegram bot oracle, or a Cabi.Chat widget, run by Cabi.Chat or by your own program Cabi.Chat Oracles — Cabi.Chat widget. Side by side, with setup: Cabi.Chat Oracles — kinds and setup

How it thinks and writes: Cabi.Chat Ignite

An oracle is a card. It belongs to a project, has its own visibility and can be shared with a teammate like any other card. Cabi.Chat Graph — Card Policies.

Its own identity. An oracle is not you. It reads the cards of its agenda without any share link: putting a card into the agenda is enough. Which cards it may read: Cabi.Chat Graph — Card Policies. Cabi.Chat Ignite — Agendas On the API: Cabi.Chat API — Apps

Lifecycle. A new oracle starts stopped. Start it when its agenda is ready, stop it at any time; deleting it stops it and removes its keys. Which plans include which oracles: Cabi.Chat Pricelist

Where its conversations land: Cabi.Chat Inbox

Oracles in action: Cabi.Chat Campaigns Cabi.Chat Radar Cabi.Chat Announcements

Cabi.Chat Radar — With or without an oracle

A radar has two modes: two distinct products inside the same mechanism. How a radar finds requests: Cabi.Chat Radar

Radar without an oracle. Matches only, nothing is sent. You open a match, read the context, and reach out yourself. This is the volume-and-control mode: see who is asking for what you offer across many groups at once, and keep the conversation in your own hands. No oracle and no agenda needed.

Radar with an oracle. Turn outreach on, give the radar Telegram account oracles and a Swappable agenda Cabi.Chat Ignite — Agendas. A match can now become a conversation. Cabi.Chat Graph — Oracles™

  • Outreach. Open a match and ask for a draft, with a note if you like. The oracle writes the first message from the project's knowledge; you edit it and send.
  • Auto outreach. The oracle writes first, on its own, to the requests that resemble the canonical matches you marked. It can be switched on once you have marked five canonical matches.

Who it writes to. The oracle writes to the person behind the request and speaks as your project. The radar is built never to write to bots, nor to write first twice to the same person for the same project, and it does not keep writing to someone who has not answered. A reply opens a room that becomes your lead. Cabi.Chat Inbox — Leads

Switch any time. Outreach off returns the radar to matches only, and switches auto off with it.

Starting and stopping a radar: Cabi.Chat Campaigns
Drafts and first messages are AI usage: Cabi.Chat Balance

Spectral — plugins via the Telegram bot emulator

The plugin system on the platform is called Spectral. It's a Telegram bot emulator: it speaks the Telegram Bot API, so anything which already works as a Telegram bot, or could be built as one, plugs into Cabi.Chat and works inside Cabi.Chat conversations alongside the platform's own capabilities.

This is the integration axis for builders. Instead of the platform trying to build every adjacent tool itself, third parties bring what they already do well, and users get a richer workspace without leaving the cabinet.

It already carries Cabi.Chat's own widget. Every Cabi.Chat widget is a Spectral bot: Cabi.Chat's AI answers through it, or your own program does, with the widget's token. Cabi.Chat Oracles — Cabi.Chat widget

How a bot sees Cabi.Chat. As Telegram. The bot is added to a conversation, receives updates by long polling (getUpdates) or an HTTPS webhook with a secret token, and answers with the usual methods. Chats and users carry Telegram-style numeric ids, formatting arrives as entities.

Supported methods

  • Messages — send, edit, delete, forward, copy, pin, reactions, typing; HTML or entity formatting; replies; inline keyboards with callback buttons.
  • Media — photos, documents, audio, voice, video, video notes, animations, stickers, albums of up to 10, file download.
  • Location, venue, contact, polls — with results when a poll is closed.
  • Chats — chat info, members and administrators; ban, unban, mute, promote; forum topics.

Other Bot API methods are not supported.

Categories Spectral is designed to host:

  • CRM — managing contacts, deals, pipelines on top of platform-generated leads.
  • Scheduling — calendars, meeting booking, time-slot coordination.
  • Escrow and payments — holding funds between parties until conditions are met.
  • TON integrations and smart contracts — non-custodial flows, on-chain settlement, smart-contract-driven behavior wired through bot interfaces.
  • Ticketing and support — issue trackers, helpdesk systems.
  • Project management — tasks, boards, milestones tied to platform projects.
  • Analytics — extended dashboards, reporting, custom views on platform data.

Bringing a plugin is a partnership conversation: write to the oracle of Cabi.Chat. The interface contract is Telegram-bot-compatible, which makes the bar for integration low: if your service runs as a bot, it's most of the way there.

Also in Telegram: Cabi.Chat Bot

Cabi.Chat Graph — Card Policies.

There are three card policies you have to know about. Each decides its own axis.

Visibility — who may ever surface the card. Publicity — whether anonymous visitors and search engines may. Audience rights — what a reader may do with it.

Visibility

  • Private — yours only, absolutely. No access link, no shared workspace, no grant ever reveals a Private card, and no oracle's model ever reads one, not even your own oracle's. Your own campaigns can still use your Private cards; only what an oracle reads must be Unlisted or Public. Every card starts Private.
  • Unlisted — shared privately. The card stays out of public search and listings, but reaches the people you choose: through a grant or an access link on the card itself, or on any workspace that contains it, at any depth Cabi.Chat Graph — Sharing with access links. A card's number alone, or a Public workspace around it, gives no reach. Use it for team material and for everything your oracles must read.
  • Public — free to read and discover: by other users, by third-party oracles, by search engines.

Unlisted and Public cards must be anchored to a project, and a card is never more visible than its project: an Unlisted project cannot hold a Public card. Cabi.Chat Graph — Data types

Publicity fine-tunes your public exposure.

  • Ecosystem (default) — only signed-in users see the card; anonymous visitors are denied, even with an access link. Reasonable for semi-sensitive content.
  • Everyone — anonymous visitors too. Only in this mode can crawlers such as Google, Bing and Yandex index your content, and only in this mode does an anonymous visitor holding an access link see the card. How such cards get indexed: Cabi.Chat SEO — Getting indexed by search engines.

Audience rights are three bits set per card, the way files have them.

  • Read — a reader sees the whole card and may copy it. Without it a reachable card shows masked: title and teaser only, the rest stays closed.
  • Write — a reader may edit and operate the card: content, settings, and starting or stopping an oracle or a campaign. Counts only on Unlisted cards and only for signed-in readers; on a Public card it never applies, so the open web cannot rewrite you.
  • Execute — the card may be assigned into a field of another card, so the system uses it while that card works: groups as a campaign's sources, articles and workspaces as an oracle's instructions, endpoints as tools, agendas as the mind behind an oracle, a project as the anchor of a campaign or an oracle. Starting and stopping needs Write. A Public project never gives Execute; a project's Execute is shared only by grants and links.

What grants and links add: Cabi.Chat Graph — Sharing with access links

The owner's word is final. A share counts only when it comes from the card's owner: a shared workspace or an access link carries only the sharer's own cards. Place someone else's card into your workspace and share it, and that card does not travel with it: readers see it only if its owner already let them in. And no share, by containment or by link, ever reveals a Private card. Cabi.Chat Graph — Workspaces and containment

Cabi.Chat Pricelist

Pricing on Cabi.Chat is per project. A project stays Free until you make it Pro: on its own, or through a plan that covers up to ten projects. Prices are in USD and are paid from your Cabi.Chat Balance.

Free

Pro for one project: 18 USD / month

Pro plan monthly: 81 USD / month

Pro plan yearly: 818.18 USD

  • up to 10 projects for a year, about 16% less than twelve monthly payments

Founding supporter: 999 USD, once

  • lifetime Pro plan for up to 10 projects
  • available only during pre-beta / beta, 18 seats in total; your profile shows how many are left. After beta, lifetime is not offered
  • personal help with setting up your first project
  • this is early funding: it goes to faster development and infrastructure. For those who feel it and want it to grow.

AI usage

  • billed at the model provider's cost + 18% to the owner of the campaign or oracle, on every plan Cabi.Chat Ignite

Custom work, paid separately

  • building your portfolio on the graph, integration with your website, connecting a calendar, a CRM or anything else is discussed in chat
  • custom integrations for an additional fee

Your own Telegram account as an oracle — we help you connect it.

Barter — we are open to it, ask the oracle.

How to pay: How to make a deposit on Cabi.Chat, then How to Make Subscription Payment?.

To start or to ask: How to Report a Bug or Request a Feature. Founding supporters get priority.

How to Report a Bug or Request a Feature

The easiest way to report a bug, ask a question or request a feature is to message the Cabi.Chat Support oracle in Telegram: https://t.me/CabiSupport. Questions about payments and your balance go there too.

What to send

  • what you did, what you expected, what happened instead;
  • a link to the card, project or page where it happened;
  • a screenshot, if it helps: the oracle looks at photos.

What happens next

The oracle answers what it can on the spot, from the platform's own docs on the graph. What it cannot settle, it passes to the Cabi.Chat team through a human handoff, and a human reply may take some time. Cabi.Chat Inbox — Human handoff

How to make a deposit on Cabi.Chat

Cabi.Chat accepts two ways to top up: Telegram Stars and crypto (TON, USDT on TON and Bitcoin). Bank card payments are not available.

Telegram Stars. You top up in our Telegram bot @CabiChatBot with /deposit: pick a package and pay the invoice with Stars. Stars are bought inside Telegram, no crypto wallet needed. You need a Cabi.Chat account first: sign in at cabi.chat with Telegram, or send /start to the bot.

Crypto: TON, USDT on TON and Bitcoin. Your Cabi.Chat account comes with two deposit addresses, one TON and one BTC; the TON address takes both TON and USDT on TON. They are yours and they never change: every deposit you make goes to the same address. Crypto goes through no third-party processor, and the addresses are on-chain, so you can check them in any explorer before you send. You find them in your Profile under Account balance.

Important:

  • Crypto payments are not detected automatically: after sending, press Update balance in your Profile. If you forget, the payment is not lost; it stays undetected until you check.
  • Send USDT over the TON network only. On the TON address, native TON and USDT issued by Tether are credited. Other tokens on TON are not credited, so do not send them.
  • When and how a deposit is credited: Cabi.Chat Balance

Step by step in the app: FE pipeline: Top up your balance with Telegram Stars, TON, USDT on TON or BTC · through the API: API pipeline: Top up your balance with Telegram Stars, TON, USDT on TON or BTC

Questions about payments: write to Cabi.Chat Support in Telegram, https://t.me/CabiSupport.

For paying for Pro, see: How to Make Subscription Payment?

Cabi.Chat Search

Cabi.Chat Search is the graph's discovery engine. It is the other half of the platform's traffic: campaigns push a project outward to a new audience Cabi.Chat Campaigns; search brings the audience to the project. People come on their own, describe what they need in their own words, and the graph answers with the cards that fit: projects, articles, audiences, workspaces, rubrics.

One engine, every seeker. The search page, the landing prompt and oracles in conversations run on the same logic and the same data. An oracle that looks for a project for its correspondent finds what a person would find, within what its grants reach. Cabi.Chat Graph — Oracles™

Who sees what. Search, the landing and the map never show more than the card's policies allow. Anonymous visitors see Public cards open to Everyone. Signed-in users also see Public cards open to the Ecosystem, and in search they also find their own cards and cards shared with them. Private cards of others never surface, not even by their exact title. Cabi.Chat Graph — Card Policies.

How it finds

Where it shows up

Cabi.Chat Analytics — Visits and traffic sources

Every project on Cabi.Chat counts its visits. Nothing to install: a visit to the project page, or to any card anchored to the project, is recorded for that project. Pages that belong to no project count for the platform itself.

What a visit records

  • the page and the referrer, where the visitor came from
  • the UTM tags of the link, if any Cabi.Chat UTMs
  • page load time
  • an anonymous visitor id, kept in the visitor's browser
  • the IP address and browser of the request, as any website sees them

Project view

  • Visits and Unique visitors for the last 30 days.
  • A daily timeline: the bar is visits, the inner bar is the share of unique visitors.
  • A table: campaign → source → visits → unique visitors. A visit without tags is "direct".
  • Your website, when the project has a Website contact: verify it, add the tag, and the site's own visits join this view. Cabi.Chat Analytics — Track your own website

Campaign view

The same totals and timeline for one campaign, with rows by source and by the project each visit landed on.

Where both views open in the web app: FE pipeline: Project visits and your website's traffic. One card's own stats: FE pipeline: See who viewed your card

Impressions

Cabi.Chat also notes when a card's tile is actually seen, in search and on the landing: at least half of it on screen for a moment, once per page view, no double counting. And when it is opened. Opens feed search: what people open helps decide what people are shown. Cabi.Chat Search, Cabi.Chat Landing

Errors

If something breaks in the browser while you use Cabi.Chat, the error and the page it happened on are reported automatically, so it can be fixed. To tell more, How to Report a Bug or Request a Feature

Cabi.Chat Inbox

Cabi.Chat Inbox is where you read and answer the conversations of your projects and oracles. In the web app it is Rooms in the sidebar: rooms on the left, the thread on the right. New messages arrive live, with an unread counter on each room. The Cabi.Chat Assistant, the platform's own AI assistant, is pinned at the top.

Where the conversations come from: Cabi.Chat Inbox — Leads

Oracle rooms. One room per oracle and person. Text, photos, voice, video, stickers, files, edits and reactions are mirrored from Telegram as they happen; a message deleted in Telegram shows as deleted here too, without its content. Cabi.Chat Graph — Oracles™

Take over at any time. In an oracle room you write as the oracle: your message goes out in the same chat, from the oracle's account or bot. Step by step: FE pipeline: Read and answer your conversations

Listener. You can switch the oracle off for one chat and back on: messages keep arriving here and you answer yourself. The oracle also switches itself off when the person asks it to stop replying. How: FE pipeline: Supervise conversations your oracles hold: turn the listener off/on, clear a handoff, set a room's agenda, ask the oracle to continue

When the oracle asks for you, the room is marked: Cabi.Chat Inbox — Human handoff

Privacy. Oracle rooms start private: only you, as the owner of the oracle, see them, unless you share one. To write its replies, the oracle sends the conversation to the AI model it runs on.

Rooms between projects can also be run through the API: API pipeline: Create and manage your own room

Cabi.Chat Inbox — Leads

A lead is a conversation. On Cabi.Chat there is no lead form and no export to fill in: every conversation, found or caught, lands in your inbox as a room, and that room is the lead. Reading and answering rooms: Cabi.Chat Inbox

Where leads come from

  • Search and the graph. People and oracles find your project through search, the map and the cards around it, then write. Cabi.Chat Search — Keywords, meaning and intentions
  • Your oracle. Someone writes to your oracle in Telegram or in the widget on your site, and gets their own room with that oracle. Cabi.Chat Graph — Oracles™
  • Radar. Your oracle answers a public request a radar found; the room remembers which campaign and project brought the person. Cabi.Chat Radar — With or without an oracle
  • Another project. Projects talk to projects. Press To the chat on a project card and choose which of your projects speaks: a private room opens between the two projects, and the other owner finds it in their inbox. Opening the same pair again lands in the room you already have. When another project opens a chat with yours, that room is your lead. Talks are project to project, so you need a project first.

Cabi.Chat Projects — Shape the image.

A project is known by its hotspot: the project card plus every card its edges reach, the cards anchored to it and the cards they mention. People, oracles and search engines know the project by its hotspot, not by the project card alone. An oracle answers from it. Cabi.Chat Graph — Oracles™

Anchor your cards. Articles, posts, docs, boards and workspaces pick a project in the Project field. Anchored articles are the project's knowledge base: answers to frequent questions, details, cases. Publish the project before its cards; why: Cabi.Chat Graph — Card Policies.

Link them. Mention the project and your other cards in the text. Every mention is an edge, and the edges hold the hotspot together. How mentions work: Cabi.Chat Graph — Handles, mentions and relations

One topic per card. Each card answers one question. The project card says what you do; the articles carry the details, each in one place, never copied across cards. A reader, an oracle or a search engine then meets every answer once, where it belongs.

Where the hotspot gets found: Cabi.Chat Search — Keywords, meaning and intentions. How search engines read it: Cabi.Chat SEO — Getting indexed by search engines.. The fields of the project itself: Cabi.Chat Projects — What a project is made of

Cabi.Chat Projects — Pro

Pro is a membership of one project. A Free project can be found, read and reached; a Pro project acts.

What Pro adds

Renewal. Pro renews every month on the same day, from your balance, while auto-renew is on. Stop auto-renew any time and Pro runs to the end of the paid month.

When the balance is short. If the balance does not cover the renewal, Pro lapses and the project goes back to Free: its campaigns pause, its oracles stop except your one free oracle (a bot or a widget), and the platform bot tells you in Telegram. Nothing is deleted: make the project Pro again and start them.

Price: Cabi.Chat Pricelist. How to pay, for one project or with a plan: How to Make Subscription Payment?

Everything else a project is made of: Cabi.Chat Projects — What a project is made of

Cabi.Chat Campaigns

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 in the project's name. Telegram first.

Six kinds

  • Radar. Finds public messages in Telegram groups where people ask for what your project offers.
  • AI Scout. Reads the public groups you picked in batches, at the interval you set, and gives you an overview by your agenda: what matters to you and what is noise. Its picks can go to a radar.
  • Announcements. Posts your posts in public groups that allow promotion.
  • Reactions. Your oracles react to fresh messages in groups at a chosen pace.
  • Join chats. Your oracles join a list or preset of groups, following each group's rules and Telegram's limits.
  • Leave chats. The reverse.

What a campaign is made of

A project, Telegram groups, oracles, and where the job needs it, posts and a Swappable agenda Cabi.Chat Ignite — Agendas. Every slot takes cards or workspaces of cards, so one preset of groups or one team of oracles serves many campaigns. Cards shared with you with execute (x) rights can be attached too.

Lifecycle

Every campaign is created paused. Start and stop are one button. Radar, AI Scout, Announcements and Reactions run until you stop them. Join and Leave finish on their own once every oracle has walked the list. Start checks what is missing and says so; a run whose groups or oracles resolve to nothing ends as Failed.

Campaigns run only on Pro projects.

Operators

A campaign can be shared with write access. An SMM specialist or an agency can tune, start and stop it on your behalf; the performance stays with you.

Performance

Every campaign that sends has a performance view: messages sent, groups, oracles, replies, a timeline, a breakdown per group, and each message with its status: live, replied, removed.

Cabi.Chat Radar
Cabi.Chat Radar — With or without an oracle
Cabi.Chat Announcements
Cabi.Chat Radar — Telegram group presets
Cabi.Chat Ignite
Cabi.Chat Pricelist

Cabi.Chat SEO — Getting indexed by search engines.

Cabi.Chat SEO is how the graph meets search engines. Every public card open to Everyone is served to search engines as a complete page, with a social preview and every language it has. You do not run a site.

What gets indexed

Only Public cards open to Everyone: Cabi.Chat Graph — Card Policies.

What you get

Project page. Lives at cabi.chat/@handle once you claim a handle, at cabi.chat/project/ until then. The page carries the project's name, its description with working links, and the articles anchored to it. Contacts meant for signed-in people or given on request are never printed on it. Cabi.Chat Projects — Contacts

Articles. An article anchored to a public project is shown on the project page and adds depth to the project in search instead of competing with it.

Other cards. Workspaces, boards, docs and sheets get pages of their own. A workspace lists its public contents.

Languages. Each translation of a card is found by search engines in its own language.

Links. Mentions and cabi.chat links inside a text become real links between pages.

Sitemap and landing. Public pages open to Everyone are listed for search engines, and the landing shows them its projects.
Cabi.Chat Landing

Getting indexed

  1. Get on the landing: Cabi.Chat Landing; every landing project goes into the sitemap.
  2. A handle: it becomes the canonical address.
  3. A title and a description that say what you do. Cabi.Chat Search — Keywords, meaning and intentions
  4. Translations for the markets you serve.
  5. A proper graph: Cabi.Chat Projects — Shape the image.; over time it is indexed like a multipage website.

Indexing takes time, and no one can promise a ranking.

Cabi.Chat API

Cabi.Chat API is one API over the whole graph. Everything you do in Cabi.Chat, the web app does through this API: projects, articles, workspaces, campaigns, oracles, the inbox. Cabi.Chat is the first client of the graph, not the only possible one Cabi.Chat Graph — One Graph, Any Surface. Your scripts, your website, your own oracles and your AI assistant are clients too, on the same terms. An assistant connects through MCP: Connect your AI assistant to Cabi.Chat (MCP)

Two halves

Who is calling

Send Authorization: Bearer <token>. What a call reaches depends on whom the token speaks for.

Conventions

  • Base URL: https://api.cabi.chat/v0, JSON in and out; /v1 serves the same routes as an alias.
  • Spec: https://api.cabi.chat/api-docs/openapi.json. Generate a client from it.
  • Nonces: every card has a nonce, a 64-bit number. It travels as a string; keep it a string, because JavaScript numbers lose the last digits. Where a path says {ident}, a @handle works as well as a nonce; where it says {nonce}, send the nonce.
  • Language: ?lang=ru or Accept-Language. A card returns every language it is stored in, under i18n.
  • Errors: JSON {"error": "..."} that says what to fix. 400: the request needs a fix. 401: the token is wrong or revoked. 404: a card you cannot reach; the API does not confirm that a hidden card exists. 500 {"error": "internal error"}: retry later.
  • Request bodies: a create or an edit takes only the fields of that request. A field it does not know, or a misspelled one, is refused with a 400 that names it and lists the accepted fields (names are case-sensitive); fix it and send the request again.
  • Paging: lists take limit and offset. The contents of a workspace or a rubric page with contained_limit and contained_offset, and the answer gives contained_next_offset. Search and a campaign's sends page with page, from 1.
  • Timestamps: cards carry RFC 3339 in UTC; report rows (sends, performance) carry YYYY-MM-DD HH:MM:SS.mmm in UTC.
  • Card slots: a field that takes cards (tg_groups, not_tg_groups, oracles, posts) takes workspaces too, and a PATCH replaces the whole list.
  • Creates carry an Idempotency-Key. Cabi.Chat API — Creating cards: idempotency and limits
  • Rights: every call follows the card policies, exactly as in the app. Cabi.Chat Graph — Card Policies.

First call

curl -H "Authorization: Bearer $CABI_PAT" https://api.cabi.chat/v0/my/self
curl -H "Authorization: Bearer $CABI_PAT" https://api.cabi.chat/v0/my/projects

The first answers who you are (200 with your profile), the second lists your projects. Your first project over the API: API pipeline: Create and edit your project page

Cabi.Chat Graph — Handles, mentions and relations

Cards point at each other in three ways: by name, in text, and with a labelled relation.

Handles. Most cards can carry an @handle, a readable name instead of a number: @cabichat. Lowercase letters, digits and _ . -, up to 64 characters. Projects keep bare handles; other types get a short prefix that says what they are: a. articles, ws. workspaces, rub. rubrics, p. posts, b. boards, doc. docs, sh. sheets, c. coupons, camp. campaigns, l. access links, o. oracles, ag. agendas, api. endpoints, rm. rooms, tgg. Telegram groups. Type the name, the prefix is added for you. Renamed a card? Its old handle keeps leading to it, so shared links do not break.

Reserved names. Handles named cabichat… (with any continuation), or cabi as a whole word (cabi-…, cabi.…), and similar spellings, as well as handles that start with _, belong to Cabi.Chat's own cards; words like cabinet stay free. cabi-… is a short form: it opens the card named cabichat-….

Mentions. Write a card into any text and it becomes an edge:

  • @handle, or @article/<nonce> with the type spelled out;
  • a link to the card on cabi.chat;
  • an empty Markdown link, [](https://cabi.chat/article/<nonce>): it renders as the card's own title, in the reader's language, and follows the title when it changes. This is how these docs link to each other.

Every mention is recorded on both sides: a card shows what it mentions, and the mentioned card knows who mentions it. Mentions are how a knowledge base links up, how oracles walk from one card to the next, and how search engines see your backlinks. Placing a card on a flow board mentions it too. Cabi.Chat Graph — Data types

Relations. A relation is an edge with a meaning: this article implements that decision, this one supersedes the old one, this one is derived from a source. The label is a rubric with a reading for each side: seen from the other end, "derived from" reads "source of". You relate a card you can edit to any card you can read. Relations are set through the API. Cabi.Chat Graph — Rubrics

Never a backdoor. A handle, a mention or a relation never opens a card. Each exists for a viewer only when the viewer can read everything it touches; anything else is not shown and not even counted. Cabi.Chat Graph — Card Policies.

Cabi.Chat Graph — Like, save, copy

Every card carries the same three buttons wherever it appears: on a tile, in a list, on its own page.

  • Like — tells the owner a card is good. One like per person; press again to take it back. The card shows how many likes it has.
  • Save — clips the card into your workspaces: one or several at once, or a new one created on the spot. Select several cards and save them together. A card's save count is the number of people who saved it, not the number of places. Cabi.Chat Graph — Workspaces and containment
  • Copy — copies the card's link. Press and hold to see the access links that share this card and to create a new one. Blue means you shared the card; purple means it was shared with you. Cabi.Chat Graph — Sharing with access links

A like or a save shows the same everywhere at once: like a card in a list and its page already knows.

Saving does not make a card yours: it stays its owner's, and so does the say over who sees it. Cabi.Chat Graph — Card Policies.

Operational layer

Telegram as an operational layer for doers

A generation across the post-Soviet space learned what the web can be through the work of Pavel and Nikolai Durov. VKontakte, launched in 2006, gave millions a free place to meet, share and organise themselves. Telegram, launched in 2013, carried the same instinct further: fast, free infrastructure that treats its users as capable adults - with their own identity, their own communities and room to build.

From messenger to operational layer

Telegram is usually seen as a messenger. For people who make things, it has become something more: the place where clients ask, teams coordinate, communities form and work gets done. Open APIs, bots, public groups and channels turn it into a shared layer of everyday operations - familiar, fast and trusted by the people already on it.

We see Telegram as an operational layer for doers: the ground on which independent work can be found, offered and delivered without leaving the tools people already rely on.

Cabi.Chat: built on that layer, not around it

For Cabi.Chat, Telegram is the main surface, not one more channel. The audience is already there, and its open APIs let a project work inside it instead of pulling people out to somewhere else. So the first encounter with a project happens right inside Telegram: in the group, the chat or the bot where the person already is. The aim is simple: less time searching and repeating, more time doing the work.

Teleosis and TeleOS

The non-commercial side of the same idea is Teleosis. Intro to Teleosis

TeleOS is the protocol direction behind it: an open way for people, projects and their assistants to describe what they do, find each other and work together on familiar technology.

Building something bigger, together

The invitation is to unite around tools that are already part of daily life, and to build on them with care: open where it helps, private where it should be, useful first.

Let your AI agent run your presence on Cabi.Chat

Your own AI agent, such as Claude Code, or a simple script can keep your Cabi.Chat presence current while you work. It works through the Cabi.Chat API with a personal access token, a key that acts as you: Cabi.Chat API — Personal access tokens

What your agent can do

With a token your agent works on your project the way you do in the app:

  • create and edit your project page: text, place, photos, contacts, who can see it;
  • write articles and posts, in several languages;
  • collect pages in workspaces, tag them by topic, link them to each other;
  • search Cabi.Chat by keywords or by meaning;
  • read and answer your conversations;
  • run Telegram campaigns on Pro projects and check how they and your pages perform.

Example

Dilnoza runs a small flower shop in Tashkent and takes orders in her Telegram channel. Every Monday she tells her Claude Code: "New this week: peony bouquets, order two days ahead. Closed on the 20th." The agent updates the catalogue on her project page and adds a short public post to the project. People who look her up see this week's bouquets, not a message lost three weeks down the feed.

Getting started

  1. Sign in to Cabi.Chat with Telegram.
  2. Open Profile → Personal access tokens and mint a token for your agent.
  3. Connect it: an assistant that speaks MCP through Connect your AI assistant to Cabi.Chat (MCP); any other agent from the API guide, with step-by-step recipes for each goal and a full machine-readable description of the API: Cabi.Chat API guide

Telegram instead of passwords: sign in with the account you already use

Your Telegram account is your Cabi.Chat account. There is no password to create, no email to confirm and nothing new to remember. If you already run your business from Telegram, you already have everything you need.

One account, on the website and in Telegram

  • The same Telegram account signs you in on the website and inside Telegram, and you see the same projects, pages and conversations in both.
  • Another Telegram account opens another, separate Cabi.Chat account. Sign in with the one you use for your business.
  • If a Cabi.Chat AI assistant set up a page for you in a Telegram chat, sign in with the same Telegram account that talked to it: the page is already yours. The assistant's setup access and how to revoke it: Cabi.Chat API — Personal access tokens

On the website

Tap Sign In, tick the box to accept the Terms of Service and Privacy Policy, then pick one:

  • Log in with Telegram: confirm in Telegram's window and you are in.
  • Challenge phrase: you get a short phrase. Send it to @CabiChatBot from your own Telegram account, come back, and the page signs you in by itself.

Send only the phrase shown on your own screen. If anyone sends you a phrase to forward to the bot, even someone who says they are from Cabi.Chat, do not send it.

Inside Telegram

Open the Cabi.Chat Mini App: https://t.me/CabiChatBot/MiniApp. The first time, and again whenever the Terms change, you accept them with one tap; otherwise you are signed in as soon as it opens. What is inside: Cabi.Chat Mini App

Example

Aziz repairs phones in Samarkand and takes orders in Telegram. At the counter he opens the Mini App and updates his prices. At home he opens the website on his laptop, taps Log in with Telegram and sees the same page. He has no password to forget.

Good to know

Why Cabi.Chat - articles

Start here: Cabi.Chat as your marketing layer - The marketing layer your Telegram is missing

What Cabi.Chat does for you, one topic per article.

Why Telegram first: Operational layer

The marketing layer your Telegram is missing

Telegram, Instagram and TikTok bring reach: followers, feeds, reposts. But a feed forgets. Prices, answers and your best work sink in the scroll, and the tools that turn attention into clients sit in a dozen apps. Cabi.Chat is where your social links lead: the depth, the knowledge and the marketing tools, in one place.

Take Lena: she runs a small cleaning service in Lisbon and gets most clients through Telegram. Her prices, districts and answers used to be scattered over months of channel posts, and every new client asked the same questions again in a private chat, often late at night. Now her Telegram bio leads to her Cabi.Chat project: her pages and her assistant answer those questions while she sleeps, fresh requests from local groups reach her in time, and she sees which of her links bring people. Her evenings go to clients, not to repeating herself.

What it does, topic by topic: Why Cabi.Chat - articles

Keep posting where people first see you, and put your Cabi.Chat link in your bio and in your posts. Create your page: FE pipeline: Create and edit your project page

Cabi.Chat Pilot program

Cabi.Chat picks a small number of people and businesses to pilot our Pro services with: your promotion and social marketing, personally curated by the Cabi.Chat team. We shape assistants and personas for your business, run the boosts, and grow your presence together with you; you bring what you know and keep it well organised on Cabi.Chat. For us it is a showcase, for you a boost.

Is this you?

You have a passion for what you do and you are ready to unfold your knowledge into a well-organised cluster of pages - what goes into it: Get found in search: your Telegram project as pages search engines can read

What you get

What to expect

The pilot is an ongoing boost of your project on Telegram, not an instant result. As with ads run by an agency, who we reach and what we say is tuned all the time, and your cluster of pages is kept up to date. Our AI does much of this work; results come from steady work together. At the start we agree on what you want to promote most - which service, for which clients, in which area - and build around it.

Terms

The AI work for you - your assistants, radars and announcements - is always paid from your own Cabi.Chat balance: How to make a deposit on Cabi.Chat. Your side: keep curating your cluster - answer, add, update.

How to get in

  1. Start with your page: create it yourself (FE pipeline: Create and edit your project page) or let one of our assistants set it up for you in a Telegram chat (FE pipeline: Take over an account a Cabi.Chat oracle set up for you).
  2. Grow it into a cluster. A strong, well-organised cluster is your best chance.
  3. We pick the pilots ourselves.

Connect your AI assistant to Cabi.Chat (MCP)

Your AI assistant can work in Cabi.Chat for you. Cabi.Chat runs an MCP server: Claude.ai, ChatGPT, Claude Code, Codex, Cursor, Claude Desktop or any other MCP client can find Cabi.Chat API operations, read how they work and run them on your account. Tell the assistant what you want in plain words and it makes the calls. What it can do for you: Let your AI agent run your presence on Cabi.Chat

Two ways to connect

The server

  • Address: https://api.cabi.chat/mcp
  • Transport: Streamable HTTP
  • Sign-in: an app connection approved through your Cabi.Chat sign-in (OAuth), or your token in every request as the header Authorization: Bearer YOUR_TOKEN

Connect a chat app

Claude.ai

  1. In Claude.ai open Settings → Connectors and add a custom connector with the address https://api.cabi.chat/mcp.
  2. Choose Connect. A Cabi.Chat window opens; sign in with Telegram if it asks.
  3. Cabi.Chat shows which app wants to connect and the access it asks for. Allow connects it and takes you back to Claude.ai; Deny stops here.

Claude Desktop uses the connectors of your Claude account, so the same connector works there too.

ChatGPT

  1. In ChatGPT settings add a custom connector (app) with the address https://api.cabi.chat/mcp. ChatGPT may ask you to turn on developer mode first; if it asks how to sign in, choose OAuth.
  2. Connect it. A Cabi.Chat window opens; sign in with Telegram if it asks.
  3. Check the app name on the Cabi.Chat screen, then Allow or Deny.

Allow only a request you started yourself in that app just now. A connected app acts as you, like a personal access token, with a few exceptions: Cabi.Chat API — Personal access tokens. It is listed next to your tokens in Profile → Personal access tokens, where Disconnect ends its access at once.

Connect with a token

Claude Code

claude mcp add --transport http cabi-chat https://api.cabi.chat/mcp --header "Authorization: Bearer YOUR_TOKEN"

Run /mcp in Claude Code to check that cabi-chat is connected.

Codex

Put the token in an environment variable, for example CABI_TOKEN, and add this to ~/.codex/config.toml:

[mcp_servers.cabi-chat]
url = "https://api.cabi.chat/mcp"
bearer_token_env_var = "CABI_TOKEN"

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "cabi-chat": {
      "url": "https://api.cabi.chat/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Claude Desktop with a token

To use a token in Claude Desktop instead of a connector, go through the mcp-remote bridge (needs Node.js). Add this to claude_desktop_config.json and restart Claude Desktop:

{
  "mcpServers": {
    "cabi-chat": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.cabi.chat/mcp", "--header", "Authorization:${CABI_AUTH}"],
      "env": { "CABI_AUTH": "Bearer YOUR_TOKEN" }
    }
  }
}

The server's tools

The server offers three tools:

  • search_api_endpoints - finds Cabi.Chat API operations for a task described in plain words, best match first.
  • get_api_endpoint - reads one operation in full: method, path, parameters, request body and response.
  • call_api - runs one operation and returns the status and the response.

A typical run: the assistant searches for what you asked, reads the operation, then calls it.

The assistant acts as you

Whether it connected through a chat app or with a token, what it creates belongs to you, and anything paid is charged to your balance, the same as when you do it yourself. Read what your assistant plans to do before you let it make changes.

If something does not work

  • The assistant reports that sign-in is required. In a chat app, connect Cabi.Chat again from the app's connector settings. With a token, check the Authorization: Bearer YOUR_TOKEN header, or create a new token.
  • An operation is not available: the assistant asked for something this server does not offer to your account. Ask it to search again for your task.

More about the API itself: Cabi.Chat API

Cabi.Chat and indexing of public Telegram.

Telegram has become a large public marketplace: businesses post offers, prices and contacts in open groups and channels every day. Then the feed moves on and the offer is hard to find again.

Search follows public content

When the web grew, search engines such as Google and Yandex made public pages searchable by default. Owners kept control: a site could opt out of indexing, and a business could claim its listing and decide how it appears.

Public Telegram is going the same way. What is posted for everyone becomes findable; what matters for a business is how it appears and who controls it.

Cabi.Chat indexes public Telegram

Cabi.Chat reads public Telegram groups and channels and collects the business offers posted there into one index: what is offered, by whom and where.

How we index

  • Public only. Only content posted in public groups and channels; private groups are never included.
  • Business offers. Services, products, prices.
  • The owner comes first. A business will be able to take its offer over as its own page: edit it, add photos and prices, see views and clicks.
  • Removal is yours. You will be able to remove your offer yourself, or ask our assistant in Telegram to do it for you.

Your page

Create your page yourself: FE pipeline: Create and edit your project page

Cabi.Chat is built for working with AI

We made Cabi.Chat to work in, not to scroll: for people who build their business into a cluster of pages, and for the AI that does that work with them. Cabi.Chat

AI is a first-class user here

Every task is written up twice, in parallel: how a person does it in the web app, and the exact API calls that do the same - a description made for AI to read and act on. The API reaches further than the buttons: some things are there before they reach a screen, so an agent can take on tasks the app has no screen for.

Your assistant plugs straight in

Connect your assistant through MCP and it works from those descriptions on your account: Connect your AI assistant to Cabi.Chat (MCP)

Where it pays off: your cluster

A cluster is never finished. Services change, clients ask new questions, a page needs a translation, a rubric, a link to the next one. That curation is what makes you findable, and it is the work that slips first when you are busy. An assistant takes it off your hands: you set the direction, it keeps the pages complete, linked and tagged. Let your AI agent run your presence on Cabi.Chat

Is this you?

  • You run your own marketing and want an AI to carry the routine.
  • You already use an AI assistant and want it to do real work, not only answer.
  • You know your clients' questions and want every answer to be findable.

Start

Create your page FE pipeline: Create and edit your project page, connect your assistant and hand it the first task: «Look at my Cabi.Chat project and tell me what is missing.»

Mentioned