Skip to main content
Set stream: true on Chat Completions, Responses, or Messages. The response is text/event-stream in that API’s own event format, so SDK stream helpers work unchanged.

Usage

Chat Completions sends a final chunk with usage only if you ask for it with stream_options.include_usage: true. Responses and Messages always include usage in their final events.

Keepalives

While the model is thinking, or while a response policy holds the output, a stream can go quiet. After 15 seconds of silence Antara sends a keepalive: an SSE comment (: keepalive) on Chat Completions and Responses, and a ping event on Messages. SDKs ignore them. They keep proxies and load balancers from closing an idle connection. Long reasoning and long outputs don’t time out between your client and Antara. Toward the model, a request may run for up to 15 minutes in total, and the model may go up to 2 minutes without sending anything; past either limit the request ends with 504 upstream_timeout (or that terminal error mid-stream).

Errors during a stream

An error before the stream starts is a normal HTTP error. Once the 200 and the first bytes are sent, a failure ends the stream with that API’s terminal error event instead: A stream that ends without its normal last event didn’t finish. Treat it as failed.

Stopping early

Close the connection to stop. Antara cancels the model’s work at once and bills only the tokens generated until then.