HTTP API

Use the API for server-side or custom clients. All requests are HTTPS and authenticated per your project keys (see Auth & security).

Base URL

Point clients at your deployment’s API host (same origin as configured in the app, or your gateway). Paths are versioned under /v1/… where applicable.

Typical flow

• Create or select a conversation.
• Send messages with your user or session id so context stays consistent.
• Stream or poll for assistant replies, depending on endpoint support in your build.

Errors

Expect standard HTTP status codes. Retry transient 5xx with backoff; do not retry 4xx without fixing the request.