Overview
What the Smeeware API does and how the docs are organized.
The Smeeware API answers chat requests as a stream. These docs take you from your first call to the full endpoint reference.
How the docs are organized
The docs are grouped into four tracks. Getting started takes you from an empty project to a first streamed answer. Basics covers what every call relies on — authentication, the request and response shape, streaming, attachments, errors and rate limits. Endpoints is the full reference, one page per route. Chat app documents the bundled web client: the command palette, workspaces, steering and the voice call.
Every endpoint page follows the same layout: a short lead, the parameters, an example request, and the response.
Conventions
Examples come as cURL, TypeScript and Python — pick the tab you like. The base URL is written as https://your-host/api/v1; locally that is http://127.0.0.1:8000/api/v1. Anything in UPPER_CASE is an environment variable, and sk_smee_… stands in for a real API key.