Skip to main content
1

Swap the credentials

Keep your OpenAI SDK and change what the constructor points at (create the key on the API Keys page first):
2

Map your model names

Model IDs are namespaced (vendor/model), and capability isn’t one-to-one across families, treat this as the starting map, then spot-check on your own prompts in the playground:
3

Adjust for the differences

  • Structured outputs: json_object is supported; json_schema is not, describe keys in the prompt and validate client-side (see Structured outputs).
  • Images: image_url accepts base64 data URIs only, the engine never fetches remote URLs (see Vision).
  • Reasoning: unlike the o-series, the chain of thought is returned to you, in reasoning, billed as output tokens (see Reasoning).
  • Endpoints: chat completions, completions, and models only, embeddings, image generation, audio, batches, and assistants aren’t served, so keep those workloads where they are.
  • Extra knobs: top_k, min_p, and the reasoning object exist here and don’t exist on OpenAI, via extra_body; conversely OpenAI’s reasoning_effort is rejected with 400 here, send {"reasoning": {"effort": …}} instead. Parameters outside the documented surface aren’t guaranteed.
  • Billing: prepaid credits instead of monthly invoicing, an empty balance returns 402, so turn on auto-recharge before pointing production traffic here.
4

Verify, then watch the numbers

Run your own evaluation prompts side by side in the playground before cutting over, then watch the first days of traffic in Analytics, cost per model tells you quickly whether the mapping you chose is the right one.
Migrating an agent or tool rather than code? The coding agent setup guide covers opencode, Aider, and IDE assistants.