Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Home
Chuk Chat Overview
Getting Started
User Guide
FAQ
Concepts and Terms
Privacy and Security
Billing and Subscription
Troubleshooting
How Chuk Chat Works
Architecture
AI Providers and Services
Backend and API
All Products
Chuk Development
Open Web App
Downloads
Status
Technical Docs
Support
Special Pages
Recent Changes
Random Page
Chuk Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Chuk Chat Backend and API
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
= Chuk Chat Backend and API = This page explains the backend in practical terms. == Base backend URL == https://api.chuk.chat == Authentication model == Most endpoints require a Bearer token from your signed-in account session. == Key endpoint groups == * '''Health''': service status * '''Chat streaming''': SSE and WebSocket chat endpoints * '''Model/config endpoints''': list models and configuration * '''Media endpoints''': image generation, audio transcription, file conversion * '''User endpoints''': status, billing, and account actions == Streaming protocols == === SSE (HTTP) === * Endpoint: POST /v1/ai/chat * Great compatibility for browser-style request/response streaming === WebSocket === * Endpoint: /v1/ai/chat/ws * Better for long-lived sessions and mobile stability == Typical chat response events == * content chunks * reasoning chunks (for reasoning-capable models) * usage/tokens * provider/model metadata * done marker == Rate limit examples == The backend includes request limits to protect stability, including separate limits for chat, audio transcription, and image generation. == Billing-related backend flows == * checkout session creation * customer portal session creation * subscription sync endpoint == Why this backend design exists == * Fast streaming UX * Multi-provider AI routing * Security and privacy controls * Clear separation of chat, media, and billing responsibilities == Related pages == * [[How Chuk Chat Works]] * [[Chuk Chat Architecture]] * [[Chuk Chat AI Providers and Services]] [[Category:Chuk Chat]] [[Category:Architecture]]
Summary:
Please note that all contributions to Chuk Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Chuk Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Chuk Chat Backend and API
Add topic