Completions
OpenAI-Compatible Chat Completions
Drop-in replacement for the OpenAI Chat Completions API. Point the OpenAI SDK at Theo and keep writing code the way you already do.
POST
OpenAI-Compatible Chat Completions
Theo implements the OpenAI Chat Completions wire protocol at
Supported
Pass any Theo-branded model ID.
When to use
POST /api/v1/chat/completions. Any application that uses the OpenAI SDK can point baseURL at https://www.hitheo.ai/api/v1, swap in a Theo API key, and keep working — the endpoint accepts the same { model, messages, stream, temperature, ... } shape and returns the same chat.completion / chat.completion.chunk objects.
The response shape is identical to OpenAI. The routing underneath is Theo — intent classification, model selection, and automatic failover. Pass
model: "theo-1-auto" to let Theo pick the best engine per request.Base URL
Use the canonicalwww host. The OpenAI SDK appends /chat/completions, so this base URL resolves to the real POST /api/v1/chat/completions route:
Authentication
Uses the standard Bearer-token header. Your Theo API key replaces your OpenAI key.Drop-in Example (OpenAI SDK)
Streaming
Setstream: true to receive an SSE stream of chat.completion.chunk objects terminated by data: [DONE], exactly as OpenAI does.
Supported model Values
Pass any Theo-branded model ID. theo-1-auto is recommended so Theo’s intent classifier picks the best engine per request; pass a specific engine if you want to pin the routing.
Unknown model strings fall back to
auto and Theo routes the request like any other prompt.
Request Body
The body is the standard OpenAI Chat Completion shape. Fields not listed below are accepted but ignored (e.g.top_p, n, max_tokens, user).
A Theo model ID. See the table above for valid values.
The conversation so far. Each message has
{ role, content }. Supported roles: system, user, assistant. tool messages are accepted but ignored (Theo owns tool-call state internally).The last user message is treated as the prompt. All system messages are merged into a single system prompt that overrides Theo’s default persona. Prior user/assistant turns are injected as conversation context.When
true, returns an SSE stream of chat.completion.chunk objects terminated by data: [DONE].Sampling temperature (0–2).
Theo-specific. Attach this completion to an existing Theo conversation so its memory persists across channels. Omit to send a stateless request.
Theo-specific. Activate skills by slug for this request. Merged with the user’s installed skills.
Theo-specific. Arbitrary key-value data attached to the audit log.
Response
A standard OpenAIchat.completion (or chat.completion.chunk for streaming). Theo-specific metadata is returned under a theo_metadata extension so it doesn’t collide with existing OpenAI client expectations.
When to use /v1/completions instead
- You need a single-turn prompt string instead of a message array.
- You want the richer native Theo response (follow-ups, artifacts, tool traces) instead of the OpenAI shape.
- You want to control
personaorresponse_styleper request.
Errors
Returns the same error envelope as every other v1 endpoint:OpenAI-Compatible Chat Completions
