Migrating from OpenAI
Since OmniaKey is fully compatible with the OpenAI API, migration requires just two changes:- Base URL: Change to
https://api.omniakey.com/v1 - API Key: Use your OmniaKey API key
Before (OpenAI)
After (OmniaKey)
Migrating from Azure OpenAI
Azure OpenAI uses a different URL format and API version. Here’s how to switch:Before (Azure)
After (OmniaKey)
Migrating from Direct Provider APIs
If you’re calling Anthropic, Google, or other providers directly, OmniaKey gives you a unified interface:Before (Multiple SDKs)
After (Single SDK)
What’s Compatible
| Feature | Status |
|---|---|
| Chat Completions | Fully compatible |
| Streaming (SSE) | Fully compatible |
| Function/Tool Calling | Fully compatible |
| Image Generation | Fully compatible |
| Video Generation | Extended API |
| Response Format (JSON Mode) | Fully compatible |
| Embeddings | Coming soon |
| Audio/TTS | Coming soon |
Migration Checklist
Get your OmniaKey API key
Sign up at omniakey.com and generate an API key from the Console.
Update base URL and API key
Change your client initialization to use
https://api.omniakey.com/v1 as the base URL and your OmniaKey API key.Verify model names
Most model names work as-is. Check the Supported Models page if you encounter any issues.
Test your integration
Run your existing test suite. Since the API is fully compatible, everything should work without changes.
Monitor in the Console
Use the Console to monitor usage, latency, and costs in real-time.
Need Help?
If you run into any issues during migration, reach out to us:- Email: [email protected]
- Check the FAQ for common questions