/v1/chat/completions

Generate a chat completion. OpenAI-compatible wire shape — existing OpenAI SDKs work with a base_url swap to https://api.tokenfactory.omniva.com/v1.

#Authentication

Bearer token in the Authorization header. See Authentication for how to mint a key.

Authorization: Bearer YOUR_API_KEY

#Parameters

Where dedicated endpoints are in use, their Model IDs route to that endpoint's own GPU capacity instead of the shared pool — everything else about the request (auth, shape, streaming) stays the same. See Call a dedicated endpoint for where to find that id and how it behaves.

#Message object

#Response

{
"id": "cmpl-1748044800000",
"object": "chat.completion",
"created": 1748044800,
"model": "Omniva/glm-5.3",
"choices": [
  {
    "index": 0,
    "message": {
      "role": "assistant",
      "content": "A vector database stores high-dimensional embeddings and retrieves nearest neighbors by similarity."
    },
    "finish_reason": "stop"
  }
],
"usage": {
  "prompt_tokens": 18,
  "completion_tokens": 19,
  "total_tokens": 37
}
}

The top-level fields follow OpenAI's chat.completion shape: id, object, created (epoch seconds, UTC), model, choices[], usage. Each choices[i] has index, message ({ role, content }), and finish_reason (typically stop).

#Streaming response shape

When stream: true, the response is text/event-stream. Each event is a data: line carrying a JSON chunk in OpenAI's chat.completion.chunk format. Chunks accumulate via delta.content; the final chunk sets finish_reason: "stop". The stream terminates with a sentinel data: [DONE] frame — clients should stop reading at that point.

The on-the-wire shape is one SSE event per chunk, blank-line separated:

data: {"id":"cmpl-1748044800000","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{"role":"assistant","content":"Hello"},"finish_reason":null}]}

data: {"id":"cmpl-1748044800000","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{"content":" there"},"finish_reason":null}]}

data: {"id":"cmpl-1748044800000","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{},"finish_reason":"stop"}]}

data: [DONE]

When a model emits tool calls (not yet supported by Token Factory — included here for wire-shape reference), the tool_calls array streams incrementally. Each chunk carries a partial function.arguments string that the client concatenates by index:

data: {"id":"cmpl-...","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{"tool_calls":[{"index":0,"id":"call_abc","type":"function","function":{"name":"get_weather","arguments":""}}]},"finish_reason":null}]}

data: {"id":"cmpl-...","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{"tool_calls":[{"index":0,"function":{"arguments":"{\"city\":"}}]},"finish_reason":null}]}

data: {"id":"cmpl-...","object":"chat.completion.chunk","created":1748044800,"model":"Omniva/glm-5.3","choices":[{"index":0,"delta":{"tool_calls":[{"index":0,"function":{"arguments":"\"SF\"}"}}]},"finish_reason":"tool_calls"}]}

data: [DONE]

See the Streaming guide for client-side consumption patterns.

#Errors

Errors raised by the platform return a JSON body with an error field; a request that can't reach a serving replica can instead end in a gateway timeout whose body is not JSON. The HTTP status indicates the class.

See Errors for the full error catalog and retry guidance.

#Code samples

from openai import OpenAI
import os

client = OpenAI(
  api_key=os.environ["OMNIVA_API_KEY"],
  base_url="https://api.tokenfactory.omniva.com/v1",
)

resp = client.chat.completions.create(
  model="Omniva/glm-5.3",
  messages=[{"role": "user", "content": "Hello in one sentence."}],
)
print(resp.choices[0].message.content)

#Not yet supported

The Parameters table above marks each unsupported OpenAI field with "Not supported today" in its Description. The handler accepts these fields in the request body without erroring, but ignores them — the response will not change. Track support status in Models overview.

#What next