Cabi.Chat API

One API over the Cabi.Chat graph: everything the web app does, your scripts and agents can do too. 252 endpoints.
agendas (9): Agendas: the instructions, tools and secrets your oracles follow
analytics (5): Page analytics: visits, impressions and reach
api_endpoints (7): API endpoint cards: an operation (method, path, schemas) described for AI agents and oracles
articles (7): Article cards: owned CRUD and public reads
auth (6): Sign-in sessions: Telegram sign-in and logout
away (1): Signed outbound redirects
boards (8): Board cards: a canvas scene, saved with a revision check
call-ai (1): Answers from a self-hosted widget's oracle
campaigns (18): Campaigns: radars, announcements, reactions, joins and overviews
cards (7): Any card: archive, version history and view statistics
console (6): Your verified website and its traffic
contacts (5): Project contact points: the owner adds and edits them, sets who may see each one, and visitors reveal the ones that need a reveal
coupons (8): Coupon cards: template/clipped facets, clip into your wallet, public code validation; redeem with {coupon} on POST /v0/my/projects/{n}/pro and POST /v0/my/plan
docs (8): Doc cards: the document scene, saved with a revision check
funds (6): Balance, deposits, transactions and AI spend
geo (4): Geo lookups and autocomplete
graph (3): Find your cards, resolve handles, see how cards connect
landing (1): The public landing feed
likes (5): Per-viewer likes across card types
linked (2): Token-scoped access to shared cards
links (9): Access links: owner-minted share tokens
media (1): Image upload for cards
oracles (15): Oracles: Telegram accounts, Telegram bots and website widgets
pats (5): Personal access tokens
plan (5): Plans that make several projects Pro
posts (7): Post cards: written in the web app or collected by radars
projects (11): Project cards: owned CRUD and public reads
relations (3): Relations: a rubric labels a link from one card to another (A->B and B->A are separate relations); a relation never gives access to a card and is visible only to callers who can read both cards and the rubric
rooms (32): Conversation rooms: members and roles, history, sending, threads and read state
rubrics (10): Rubrics: tags and taxonomies
search (3): Graph search
secrets (5): Secrets your oracle tools use
self (2): The signed-in caller
sheets (8): Sheet cards: the sheet scene, saved with a revision check
sse (1): Live events
telegram_groups (7): Telegram group cards
unfurl (1): Link preview
workspaces (10): Workspace cards: owned CRUD and public reads