Migrate from the OpenAI API
Point your OpenAI SDK at idapt and keep your code: chat, Responses, embeddings, images, and audio, all through one API.
How to migrate
- 1
Create an idapt API key
Settings → Gateway → API keys. Keys are scoped (completions read/write) and can carry a lifetime USD spend cap.
Create an API key - 2
Change the base URL
Set your SDK's baseURL to https://idapt.app/api/openai/v1 and the API key to your uk_ key. Everything else stays.
- 3
Pick your models
Browse /models for 200+ ids and switch per request. One key reaches all of them.
Change the base URL
- https://api.openai.com/v1
+ https://idapt.app/api/openai/v1Authenticate with an idapt API key (Authorization: Bearer uk_…). Create one in Settings → the Gateway tab.
What is supported
| OpenAI API | In idapt | How |
|---|---|---|
| POST /chat/completions (stream + tools) | Identical endpoint, 200+ models | Automatic |
| POST /responses | Non-streaming Responses bridge (stateless text)stream:true is an explicit 501. Use /chat/completions for streaming. | Automatic |
| Embeddings / images / audio (TTS, STT) | Same-shape endpoints | Automatic |
| Model names | idapt model ids (see /models); gpt-… slugs resolve where unambiguous | Manual |
| auto model / n > 1 / assistants state | Not supported on the compat surfaceUnsupported fields are rejected with a clear error, never silently ignored. | No equivalent |
Also yours to keep: Local AI runs open models on hardware you own, free, beside the 200+ cloud models in the same chat.