Skip to content
OpenAI-compatible path

If your current stack already looks like OpenAI, the first test is usually four changes.

Most migration risk is not the SDK. It is proving quality, latency, and cost on real calls. Start with the smallest code change, then replay production-like traffic before switching the route.

Change the API surface

Point `base_url` at `https://api.pyai.com/v1`, pass a PyAI key, and map the model and voice ids shown in each guide.

Replay real calls

Compare latency, transcript quality, barge-in, audio format, and outcome rate on examples from your own business before moving live traffic.

Control spend before launch

Use free credits and test keys first, then add usage alerts and pick Omni API, the Agents feature, Hear, or Speak based on the job you are replacing.

Keep your code. Change your provider.

Start free with $50 in free credits - most migrations are a base URL, a key, and a model id.

Agents is live in beta. Sandbox keys have daily limits and never touch billing.