Jump to content

Chuk Chat Backend and API

From Chuk Wiki

Chuk Chat Backend and API

[edit]

This page explains the backend in practical terms.

Base backend URL

[edit]

https://api.chuk.chat

Authentication model

[edit]

Most endpoints require a Bearer token from your signed-in account session.

Key endpoint groups

[edit]
  • 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

[edit]

SSE (HTTP)

[edit]
  • Endpoint: POST /v1/ai/chat
  • Great compatibility for browser-style request/response streaming

WebSocket

[edit]
  • Endpoint: /v1/ai/chat/ws
  • Better for long-lived sessions and mobile stability

Typical chat response events

[edit]
  • content chunks
  • reasoning chunks (for reasoning-capable models)
  • usage/tokens
  • provider/model metadata
  • done marker

Rate limit examples

[edit]

The backend includes request limits to protect stability, including separate limits for chat, audio transcription, and image generation.

[edit]
  • checkout session creation
  • customer portal session creation
  • subscription sync endpoint

Why this backend design exists

[edit]
  • Fast streaming UX
  • Multi-provider AI routing
  • Security and privacy controls
  • Clear separation of chat, media, and billing responsibilities
[edit]
Retrieved from "https://wiki.chuk.dev/index.php?title=Chuk_Chat_Backend_and_API&oldid=25"