Keep the SDK you already use
Point an OpenAI-compatible client at Apertis, keep familiar request shapes, and select current model IDs from one catalog.
- OpenAI-compatible endpoints
- One API key
- Current model catalog
OpenAI-compatible. Provider-independent.
Keep your SDK and change the base URL. Route OpenAI, Anthropic, Google, DeepSeek, Qwen, Moonshot AI, and more through one governed path.
Start with one workload. Keep your provider accounts and SDK.
A gateway with operating context
Put compatible requests, access boundaries, routing decisions, and usage records in one managed path.
Point an OpenAI-compatible client at Apertis, keep familiar request shapes, and select current model IDs from one catalog.
Keep model choice visible while provider routes, fallback rules, and model policy govern where requests can run.
Issue virtual keys, set quota boundaries, and separate agent or application access without distributing provider credentials.
Inspect request, model, token, and cost records from one managed surface instead of reconciling separate provider consoles.
Low-friction migration
Validate the compatible path and its usage record before expanding your rollout.
Start with a personal key, then introduce bounded keys for separate agents, applications, or team workflows.
Keep the OpenAI-compatible client and point its base URL at api.apertis.ai/v1.
Select a current catalog ID, send the first request, then review the request and spend record in Apertis.
from openai import OpenAI
client = OpenAI(
api_key="YOUR_APERTIS_KEY",
base_url="https://api.apertis.ai/v1",
)
response = client.chat.completions.create(
model="YOUR_MODEL_ID",
messages=[{"role": "user", "content": "Hello"}],
)Before you switch
The compatible gateway is the execution surface. Apertis Control adds the managed access, routing, quota, policy, usage, and billing context needed to operate AI workloads across providers.
Yes. Use the OpenAI-compatible endpoint, replace the base URL and API key, then choose an Apertis model ID from the catalog.
No. Start with one agent or application, validate its model access and usage record, then move additional workloads when the operating path is clear.
Apertis supports Coding Plans and pay-as-you-go access. Review the current plan and model catalog before choosing the fit for your workload.
Start with one workload
Create an Apertis key, switch one base URL, and verify the first request before expanding the rollout.