Skip to main content

title: “OpenAI SDK compatibility matrix” description: “Every gateway operation: whether the official OpenAI SDK reaches it, and what to do when it doesn’t.”

This page is generated from the same operation list the Infery TypeScript SDK is built from, so it can’t drift from what actually ships the way a hand-written table would. For the migration story and the reasoning behind the gaps, read Migrating from OpenAI first — this page is the full reference table it links to. 7 operations work with the OpenAI SDK unchanged, 4 are partial (they work for the common case but have a documented divergence — read the note), and 24 have no OpenAI SDK method at all (call them over plain HTTP, or use the matching Infery SDK method named below once it ships).
The Infery SDK column names the TypeScript SDK method that serves each operation. The infery package is not published to npm yet — there is deliberately no install snippet on this page. Until it ships, every “Infery SDK” and every “no”/“partial” row is reached the same way: plain HTTP.

Chat & embeddings

Images

Video

Music

Audio

3D

Files

Models & tools

Capabilities

Workflows

Reading “Partial”

A “Partial” verdict means the OpenAI SDK’s own method for that route sends a request this gateway accepts and can parse the normal response — but there is at least one real, non-hypothetical situation where the response diverges from what the OpenAI SDK expects (a different status code, a dropped parameter, an enveloped body where the SDK wants a bare one). The note says exactly what diverges and what to do about it. Treat “Partial” as “read the note before you ship,” not as “basically yes.”