Keep your existing OpenAI SDK
Change the base URL in your existing OpenAI SDK to the gateway and add a few headers to each call.
Use an ABTO Calling Key as the API key. Include the feature ID and your provider API keys in the headers. Also send a device ID to connect calls with user behavior and keep the same user on the same variant.
On Node.js and Python servers, the SDK adds headers such as the feature ID and device ID to each request for you.
Use the same interface across providers
The gateway receives AI calls and routes them to OpenAI, Anthropic, Gemini, DeepSeek, or Kimi. Switch models and roll back from the dashboard.
When switching to a provider you have not used before, your calling code must already send that provider's API key.
Keep your API keys and provider contracts
You retain your provider contracts and API keys. Keys are passed with each call but are not stored in the gateway's call records.
What gets recorded?
Each call records the model, token usage, cost, and response time. Prompts and raw responses are also stored by default, but you can turn off body storage at any time. Features that need stored content will then be limited.
Conversations are forwarded to the provider as your server sent them. The system prompt and model are overridden only when the routing variant specifies values. The gateway does not use the content for other purposes.