API pipelines — index

API layer of the pipelines. How a person does the same in the web app and the Telegram Mini App: FE pipelines — index

A pipeline is one user goal written as the ordered API calls that reach it: what to call, with which body, what comes back, what to check before the next step, and what the platform does behind the scenes. The API is the main interface: the FE, Cabi.Chat's own oracles and your own AI call the same operations. Auth, conventions and errors for every call: Cabi.Chat API

Pipelines

Account

API pipeline: Sign in to Cabi.Chat with Telegram: sign in with Telegram on the web or in the Mini App, accept the Terms.
API pipeline: Personal access tokens: mint, list and revoke personal access tokens.
Connect your AI assistant to Cabi.Chat (MCP): connect your AI assistant (Claude Code, Codex, Cursor, Claude Desktop) through MCP with your token.
API pipeline: Take over an account a Cabi.Chat oracle set up for you: take over an account an oracle set up for you; revoke its access.
API pipeline: Profile settings: name, language, units, time format, timezone, translation agenda.

Money

API pipeline: Top up your balance with Telegram Stars, TON, USDT on TON or BTC: top up with Telegram Stars (in the bot), TON, USDT on TON or BTC; transactions.
API pipeline: See your AI spend: AI spend by campaign and oracle; what is left.
API pipeline: Make a project Pro: Pro for one project: activate, extend, stop auto-renew, end.
API pipeline: Buy a Pro plan for up to 10 projects: Pro plan for up to 10 projects: buy, attach, release, cancel.
API pipeline: Redeem a coupon: check, clip and pay with a coupon.
API pipeline: Issue your own coupons: issue and manage your own coupons.

Find and read

API pipeline: Browse Cabi.Chat and open any card: browse without an account, open any card with the cards around it.
API pipeline: Search the graph: search by keywords or meaning, with filters; jump to a card by reference.
API pipeline: Find projects by place and on the map: projects in a city or country, on the map.
API pipeline: Reveal a project's contact: reveal a hidden project contact.
API pipeline: Like cards and find them again: like cards and find them again.

Your cards

API pipeline: Create and edit your project page: create and edit your project page: text, place, photos, contacts, visibility.
API pipeline: Write articles and posts: articles and posts: images, languages, visibility.
API pipeline: Draw boards, keep docs and sheets: boards, docs and sheets.
API pipeline: Tag cards with rubrics: tag cards with rubrics; who may mark with a rubric; your own rubric tree.
API pipeline: Link two cards with a relation: named relations between cards; other edges.
API pipeline: Collect cards in workspaces: collect cards in workspaces.
API pipeline: Everything you own or were given (Cabinet): everything you own or were given, type by type.
API pipeline: Archive, restore or delete your cards: archive, restore or delete.
API pipeline: Keep a card's version history: version history, snapshots, roll back.
API pipeline: See who viewed your card: who viewed your card.
API pipeline: Project visits and your website's traffic: visits your campaigns bring; your website's traffic and domain check.

Sharing

API pipeline: Share cards through access links: share cards through access links; manage holders.
API pipeline: Claim an access link: claim a link for a project or an agenda; what is shared with you.

Conversations

API pipeline: Read and answer your conversations: read and answer your rooms live.
API pipeline: Create and manage your own room: create and run your own room.
API pipeline: Talk to another project: start a conversation with another project.

Oracles and agendas

API pipeline: Write an agenda for your oracles: write an agenda: instructions, tools, model.
API pipeline: Give your oracle tools: give your oracle tools: your HTTP endpoints and their keys.
API pipeline: Connect a Telegram account as an oracle (phone → code → 2FA), start and stop it, sign it in again when Telegram asks: connect a Telegram account as an oracle; start, stop, sign in again.
API pipeline: Connect your Telegram bot as an oracle: connect your Telegram bot as an oracle.
API pipeline: Supervise conversations your oracles hold: turn the listener off/on, clear a handoff, set a room's agenda, ask the oracle to continue: supervise your oracles' conversations: listener, handoff, personal agenda, continue.

Telegram campaigns

API pipeline: Submit your Telegram groups, find groups by keyword, place or rubric, vet them and attach them to a campaign: submit your own groups, find groups by keyword, place and rubric, attach them to a campaign or exclude them.
API pipeline: Create, configure, start, stop, measure and delete a Telegram campaign of any kind: the campaign kinds, the shared lifecycle, measuring, one oracle's activity.
API pipeline: Listen to Telegram groups for people who need you: create and tune a radar, work its matches and make first contact (draft, send, auto outreach): create, start and tune a radar; read matches; the groups they come from; first contact.
API pipeline: Receive a free 7-day starter radar for your project and watch its matches: a free 7-day starter radar for a project.
API pipeline: Post your posts into groups at a pace set by their traffic and follow what was sent and deleted: announcements: your posts into groups at a pace set by their traffic; oracles take turns per group and can join groups first.
API pipeline: Have AI read groups in batches, post an overview to your channel and hand picks to a radar: AI scout: overviews of your groups, picks handed to a radar.
API pipeline: Have your oracles join or leave a list of Telegram groups within Telegram limits: join or leave a list of groups.
API pipeline: Have your oracles react to fresh messages in groups at a chosen pace: react to fresh messages in groups.

How to read a pipeline

Goal: what you get at the end.
Steps: numbered; one call each, with a request and the part of the response the next step uses. Samples are trimmed (…); nonces are examples.
Behind: what the platform does asynchronously, and how to observe it through the API.
Rules: conditions a call checks, and the 400 reasons it answers with.
API surface: endpoint | purpose | used by the FE | useful to an AI or oracle.

Mentioned

Cabi.Chat API · Article — 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

API pipeline: Submit your Telegram groups, find groups by keyword, place or rubric, vet them and attach them to a campaign · Article — Index: Goal: choose the Telegram groups a campaign works in: submit your own groups by username, find more in the open index by keyword, place or rubric, vet them, attach groups or prese

API pipeline: Create, configure, start, stop, measure and delete a Telegram campaign of any kind · Article — Index: Goal: create, configure, start, stop, measure and delete a Telegram campaign of any kind. A campaign is a card ( card_type: "campaign" ) that does one job for a project in Telegra

API pipeline: Listen to Telegram groups for people who need you: create and tune a radar, work its matches and make first contact (draft, send, auto outreach) · Article — Index: Goal: hear people in Telegram groups asking for what your project offers, collect their messages as matches, tune the radar, and make first contact: a draft you approve, or automa

API pipeline: Receive a free 7-day starter radar for your project and watch its matches · Article — Index: Goal: a person with a project page on Cabi.Chat gets a free 7-day radar for that project and watches its matches. What the person gets A radar run by Cabi.Chat for their pr

API pipeline: Tag cards with rubrics · Article — Index: Goal: tag your cards with rubrics, build your own rubric tree, and browse the public rubrics. A rubric is a card ( card_type: rubric ). Kind tag classifies cards; kind place

API pipeline: Link two cards with a relation · Article — Index: Goal: link two cards with a named relation ("supplies", "works with", "part of") and read a card's relations and other edges. A relation is an edge source → target labelled by

API pipeline: Write articles and posts · Article — Index: Goal: write an article (long form) or a post (short; what announcement campaigns send to Telegram groups) in one or more languages, with images; choose who sees it; edit, archive

API pipeline: Draw boards, keep docs and sheets · Article — Index: Goal: draw a board (a free canvas, or cards laid out on a canvas) and keep doc and sheet cards whose body you store yourself. Boards, docs and sheets are cards with a title, text

API pipeline: Read and answer your conversations · Article — Index: Goal: read and answer your conversations live: list rooms, read history, send text and files, reply, edit, delete, react, pin, mark read. A room is a card ( card_type: room ). `t

API pipeline: Create and manage your own room · Article — Index: Goal: create your own room and run it: invite projects, see members, set roles, remove or ban, change settings, open threads, rename, set visibility. Rooms speak as projects: you

API pipeline: Talk to another project · Article — Index: Goal: start a conversation with another project's owner, speaking as one of your projects. Talks on Cabi.Chat are project to project: you need a project of your own. Steps

API pipeline: Give your oracle tools · Article — Index: Goal: give your oracle tools: describe your own HTTP endpoints as cards and store the keys they need as secrets, then attach both to the oracle's agenda. An API endpoint card

API pipeline: Write an agenda for your oracles · Article — Index: Goal: write an agenda — the instructions and persona your oracles and campaigns run on — and read a public agenda. An agenda is a card that bundles instruction articles, API endp

API pipeline: Sign in to Cabi.Chat with Telegram · Article — Goal: a signed-in Cabi.Chat session for a person, from their Telegram account, with the Terms of Service and Privacy Policy accepted. A person signs in on cabi.chat or in the Telegram Mini App ( https

API pipeline: Personal access tokens · Article — Goal: a personal access token, so your own Claude Code, scripts or backend act as you; list and revoke your tokens. A token sees what you see and may change what you may change. More:

API pipeline: Take over an account a Cabi.Chat oracle set up for you · Article — Goal: after a Cabi.Chat oracle set up your project page from a Telegram chat, take it over: review and edit the page, see the oracle's setup access and revoke it. What happens in the chat With your ag

API pipeline: Profile settings · Article — Goal: set your name, interface language, distance units, time format, timezone and the agenda that guides the AI translation of your cards. Steps 1. Read. GET /v0/my/self → {"nonce": "<you>", "tg_id":

API pipeline: Top up your balance with Telegram Stars, TON, USDT on TON or BTC · Article — Goal: add money to your Cabi.Chat balance with Telegram Stars (in the Cabi.Chat bot) or in crypto (TON, USDT on TON or BTC) and see your transactions. The balance is kept in USDT; Pro and plans are pa

API pipeline: See your AI spend · Article — Goal: see what the AI of your oracles and campaigns costs, by campaign and by oracle, and what is left on your balance. Steps 1. Spend for a period. GET /v0/my/funds/ai-usage?from=2026-10-01&to=2026-1

API pipeline: Make a project Pro · Article — Goal: make a project Pro from your balance (one month at a time) or from a slot of your Pro plan; extend it, stop auto-renew, or end it now. Pro is what runs campaigns: a campaign starts only on a pro

API pipeline: Buy a Pro plan for up to 10 projects · Article — Goal: buy a Pro plan (monthly, yearly or lifetime) that makes up to 10 of your projects Pro, attach and release projects, stop auto-renew. Steps 1. Offer and state. GET /v0/my/plan → {"active": false,

API pipeline: Redeem a coupon · Article — Goal: check a coupon code, clip it into your wallet, see the price with it, and pay Pro or a plan with it. Steps 1. Check (signed in). GET /v0/graph/coupons/validate?code=SPRING25 → {"valid": true, "m

API pipeline: Issue your own coupons · Article — Goal: issue your own discount coupons (templates) and manage them. Coupons you issue do not discount Cabi.Chat Pro or plans: those take only coupons issued by Cabi.Chat. Steps 1.

API pipeline: Share cards through access links · Article — Goal: share cards you own with chosen people or agendas through an access link: rights, limits, duration; then manage the link and who holds it. Rules of rights and visibility: Steps 1. Min

API pipeline: Claim an access link · Article — Goal: open an access link someone sent you and get the shared cards into your account, for one of your projects or for one of your agendas; see what is shared with you. Steps As a person Open it. GET

API pipeline: Reveal a project's contact · Article — Index: Goal: get a project's contact (phone, email, Telegram…) that its owner shows only on request or only to signed-in people. Steps Read the project's contacts. GET /

API pipeline: Keep a card's version history · Article — Index: Goal: keep every saved state of a card, take a snapshot on demand and roll back to an older version. Steps Switch history on (the owner only). PUT /v0/my/cards/47

API pipeline: Archive, restore or delete your cards · Article — Index: Goal: put cards you no longer use out of sight, bring them back, or delete them for good. Steps Archive. POST /v0/my/archive {"nonce": "470000000000000001", "arch

API pipeline: Collect cards in workspaces · Article — Index: Goal: collect cards of any type in workspaces: create one, add, remove and reorder cards, find which of your workspaces hold a card. Steps Create. POST /v0/my/wor

API pipeline: Like cards and find them again · Article — Index: Goal: like cards and find them again; check which cards you liked or saved. All calls need a token, except the count. Steps Like or unlike (a toggle). POST /v0/l

API pipeline: Search the graph · Article — Index: Goal: find cards by keywords or by meaning, narrowed by card type, rubric, country, place and distance; or jump straight to a card by its link, @handle or nonce. No token needed

API pipeline: Find projects by place and on the map · Article — Index: Goal: find projects (and other cards) in a city or country and place them on a map. No token needed for public cards. Steps Find the place. GET /v0/search/geo/ci

API pipeline: Browse Cabi.Chat and open any card · Article — Index: Goal: browse Cabi.Chat without an account, open any card you may see (project, article, post, workspace…) together with the cards around it, and get its public link. No token nee

API pipeline: Create and edit your project page · Article — Index: Goal: create your project page and keep it current: text, place, photos, contacts, translations and who can see it. Steps Create. POST /v0/my/projects Idempotency

API pipeline: See who viewed your card · Article — Index: Goal: see how many people opened your card, which pages they viewed and where they came from. Steps Read the stats (you need write access to the card: its owner or an

API pipeline: Project visits and your website's traffic · Article — Index: Goal: see the visits your campaigns bring to your project, and count visits on your own website. Steps Visits to a project (its owner). GET /v0/my/console/traffic

API pipeline: Everything you own or were given (Cabinet) · Article — Index: Goal: list everything you own, and everything shared with you, type by type. Steps What you own, per type. GET /v0/my/projects?limit=20&offset=0 → {"projects": [{

API pipeline: Connect a Telegram account as an oracle (phone → code → 2FA), start and stop it, sign it in again when Telegram asks · Article — Index: Goal: a Telegram account of yours works as an oracle: it answers people under its agenda and runs your campaigns. You sign it in once (phone → code → 2FA), start and stop it, and

API pipeline: Connect your Telegram bot as an oracle · Article — Index: Goal: your own Telegram bot (made with @BotFather) answers people under an agenda you choose. Cabi.Chat hosts it: no server of yours is needed, and its conversations land in your

API pipeline: Supervise conversations your oracles hold: turn the listener off/on, clear a handoff, set a room's agenda, ask the oracle to continue · Article — Index: Goal: stay in charge of the conversations your oracles hold in Telegram: stop or resume the oracle for one person, clear a request for a human, give one conversation its own agend

API pipeline: Post your posts into groups at a pace set by their traffic and follow what was sent and deleted · Article — Index: · Lifecycle: Goal: your oracles post your posts into a list of groups, each group at a pace set by its own traffic, and you follow

API pipeline: Have AI read groups in batches, post an overview to your channel and hand picks to a radar · Article — Index: · Lifecycle: Goal: AI reads what is said in your groups in batches, posts an overview with its picks to a Telegram channel of your

API pipeline: Have your oracles join or leave a list of Telegram groups within Telegram limits · Article — Index: · Lifecycle: Goal: your oracles join (or leave) a list of Telegram groups, paced within Telegram limits, and you see where each on

API pipeline: Have your oracles react to fresh messages in groups at a chosen pace · Article — Index: · Lifecycle: Goal: your oracles react to fresh messages in groups with emoji you choose, at a pace you choose. Steps 1. Cre

FE pipelines — index · Article — Web app as of 2026-10-19 The Cabi.Chat web app and the Telegram Mini App are a layer over the Cabi.Chat API: every button calls the same operations your own Claude Code, scripts and oracles can call w

Connect your AI assistant to Cabi.Chat (MCP) · Article — Your AI assistant can work in Cabi.Chat for you. Cabi.Chat runs an MCP server: Claude Code, Codex, Cursor, Claude Desktop or any other MCP client can find Cabi.Chat API operations, read how they work