APIQIKAPIQIK
Docs
Guides

OpenAI Compatibility Matrix

Distinguish confirmed, partially compatible, and unconfirmed OpenAI endpoints, parameters, message roles, and response fields.

APIQIK confirms compatibility with the core OpenAI Chat Completions request and response structures. Compatibility means common SDK calling patterns can be reused, not that every OpenAI endpoint, parameter, or model capability is identical.

Endpoint status

Endpoint or capabilityStatusNotes
POST /v1/chat/completionsCore compatibility confirmedStandard authentication, messages, common generation parameters, non-streaming, and streaming.
Tool calling with toolsModel-dependentUses an OpenAI-style request; verify the target model's capabilities in the catalog.
Vision messages, JSON mode, reasoning fieldsModel-dependent / partialParameters and response fields can vary by upstream model.
GET /v1/modelsCore compatibility confirmedReturns { object: "list", data: [{ id, object, created, owned_by }] }; take model names from data[].id; created is a fixed value. Authenticate with a valid API key using Authorization: Bearer <API_KEY>; missing or invalid keys return 401. Use the unauthenticated /v1/public/models endpoint for catalog filters and pagination.
Embeddings, Images, Audio, Files, Batch, ModerationsPending platform confirmationAn SDK method does not prove APIQIK support.
Responses, Assistants, Realtime, Fine-tuningNot promisedNo compatibility commitment in the current documentation.

Chat Completions core fields

CategoryConfirmed / current baselineConfirm by model
Message rolessystem, user, assistant, tooldeveloper and provider-specific roles.
Generation parametersmodel, messages, temperature, max_tokens, streamseed, logprobs, audio output, and provider-specific options.
Tool fieldstools, tool_choice, tool_callsParallel tools, strict schemas, and custom tool types.
Streaming fieldschoices[].delta, finish_reason, terminal eventsExact stream_options and streaming usage behavior.
Response objectsid, choices, usageCached tokens, reasoning tokens, and provider metadata.

SDK validation baseline

  • Use the current Python openai client's OpenAI(...) initialization.
  • Use the current Node.js openai client's new OpenAI(...) initialization.
  • Record validated SDK versions and dates for APIQIK releases, and rerun examples after upgrades.
  • Ignore unknown response fields and handle optional fields as nullable.

Migration rule: Validate the endpoint and model with a minimal request, then add streaming, tools, multimodal input, and structured parameters one at a time. Do not assume all advanced parameters are compatible.