https://llm.modellix.ai with three protocol surfaces:
Also available on the same host:
GET /v1/models and GET /v1/logs.
Calls are synchronous (optional streaming SSE). Request and response shapes follow the corresponding official protocols; this guide lists core fields only. Full OpenAPI specs: Chat Completions, Responses, Messages, List models, Request logs.
Media generation (image, video, speech) uses
https://api.modellix.ai and async tasks. Do not mix that host with the LLM gateway.Base URL and Auth
Models
Passmodel in the JSON body as provider/name. See Models & Pricing for the full Model ID list and rates. Availability follows the console and product releases.
You can also list currently available Model IDs via GET /v1/models.
Choose a Protocol
The three endpoints use different URLs and body shapes. Do not mix fields across protocols.
Routing tips
Chat Completions
Responses
Messages (Anthropic)
Auth may use Bearer or
x-api-key. Optional anthropic-version header is forwarded when present.
Session Header
For multi-turn session affinity, send:
Some native tools send their own session header (for example Claude Code’s
X-Claude-Code-Session-Id). If both are present, X-Mdlx-Session-Id takes precedence.
End-User ID Header
Optional. Tag requests with your own end-user identifier so you can filter request logs later. Invalid values return400.
List Models
object: list, data[].id in provider/name form). IDs are de-duplicated. This endpoint uses the query rate limit (shared with request-log listing and similar read APIs)—not the inference RPM quota.
Request Logs
Response shape (fields useful for debugging and auditing):
The list response does not include a
mdlx_user_id field; filter with the query parameter instead.
https://api.modellix.ai, see List media request logs.
Success Responses
- Non-streaming: HTTP
200with a JSON body matching the protocol (chat.completion, response, or message). - Streaming: HTTP
200,Content-Type: text/event-stream, protocol-specific SSE events.
usage (often on the final stream event). Billing uses token usage; see Billing.
Errors
code and param.
Billing
Successful responses are billed from tokenusage. Unit prices and final charges follow the console and account invoice. Insufficient balance returns 402 with insufficient_quota.
Rate Limits
Back off and reduce request rate after
429.
Client Quick Reference
Google models (
google/...) on the OpenAI-compatible path use OPENAI_* and the /v1 base URL.
Differences from Vendor Docs
Official field catalogs: OpenAI Chat Completions, OpenAI Responses, Anthropic Messages.