OpenAI compatibility
What Relixr supports on the OpenAI-compatible surface — and what it does not (yet).
Relixr's gateway speaks the OpenAI Chat Completions wire format. Use this matrix before assuming a feature port.
Supported today
| Surface | Status |
|---|---|
POST /v1/chat/completions (non-stream) | Supported |
Streaming SSE (stream: true) | Supported (keepalive comments; no Last-Event-ID resume) |
| Tool / function calling | Supported when the upstream model supports it |
| JSON mode | Supported when the upstream model supports it |
POST /v1/embeddings | Supported |
GET /v1/models | Supported (live catalog) |
Relixr response extension (relixr / cost / route headers) | Supported |
Not supported in v1
| Surface | Notes |
|---|---|
| OpenAI Responses API | Use Chat Completions |
| Assistants / Threads / Runs | Not available |
| Batches API | Not available |
| Images / audio / video endpoints | Not on the public v1 surface |
Stream resume via Last-Event-ID | Retry the full request with a new id |
| Fine-tuning | Out of scope |
Client guidance
- Keep using the official
openaiSDKs withbase_url/baseURLset to Relixr. - Prefer Relixr error codes (
insufficient_balance,policy_violation,rate_limited) over scraping message text. - See Errors and Chat completions.
Was this helpful?
Still stuck? Help center · Doctor