Introduction
OpenAI compatibility
How myt AI Cloud aligns with the OpenAI HTTP API and how to migrate existing integrations.
myt AI Cloud follows OpenAI-compatible path names and JSON shapes for chat, audio, moderation, and model listing. Point your existing OpenAI client at the platform base URL and swap the API key.
Compatible endpoints (typical)
| Area | Path |
|---|---|
| Chat | POST /v1/chat/completions |
| Models | GET /v1/models |
| Moderation | POST /v1/moderations |
| Speech to text | POST /v1/audio/transcriptions |
| Text to speech | POST /v1/audio/speech |
Exact availability depends on models enabled for your organisation.
Migration: base URL only
Set baseURL (or base_url in Python) to your deployment’s API root—including /v1 if your gateway uses that prefix:
# Use MYT_BASE_URL as the OpenAI-compatible root (often includes /v1)
export MYT_API_KEY="sk-..."
export MYT_BASE_URL="https://api.example.com/v1"SDK replacement
You keep the official openai SDKs. The only migration steps are endpoint/base URL, API key, and verifying model names supported by your tenant.
Notes
- Response fields may include extra keys; ignore unknown fields (forward-compatible clients already do this)
- If you used OpenAI-specific betas or headers, confirm equivalents with your platform operator