Chat Completions
Changed onOpenAI-compatible chat completions endpoint.
Supports both streaming and non-streaming responses. Handles reasoning content from otari providers.
Authentication modes:
- Master key + user field: Use specified user (must exist)
- API key + user field: Use specified user (must exist)
- API key without user field: Use the shared "default" user
Request
- The document declares no server URL.
- Auth: one of:
- API key in header Otari-Key
- API key in header x-api-key
Headers
A unique value, such as a UUID, that makes a non-streaming request safe to retry. A retry with the same key and body returns the original response, request ID and cost without calling the provider or billing again. A retry while the original is still running is answered 409 with Retry-After. Reusing a key for a different body is refused with 422. Ignored for streaming requests, in hybrid mode, and on a deployment without OTARI_SECRET_KEY, which encrypts the stored response.
Request body
Response
Successful Response
Changes
- info
added the optional property
to the response with the status
- info
- info
added the new optional request property
- info