An OpenAI-compatible API gateway for your existing SDK.

01 / WORKFLOW

Set the base URL and keep the key on your server

Install the SDK in your application and set its base_url or baseURL to the published OpenAI-compatible address. Use an Allgate key rather than a provider key. Read credentials from environment variables on your backend; a browser bundle, mobile binary or public repository is not a place to store the secret. Configure a request timeout appropriate for your workload.

02 / WORKFLOW

Choose a model ID and a request contract

Copy the exact API model ID from the current catalogue. A display name is not necessarily a request identifier. Chat Completions uses messages; Responses uses its own input and event structure. Anthropic Messages has a separate request contract and headers. Select the endpoint implemented for your workflow instead of changing the path while retaining an incompatible payload.

03 / WORKFLOW

Validate features before migrating traffic

Check the selected model for tools, structured output, vision input and streaming support. Start with a small representative request, then test the features your application actually uses. For streaming, handle events incrementally and distinguish a completed response from a broken connection. Preserve request identifiers so a failure can be investigated without logging the API key or private user content.

Request example

This example does not execute automatically. Verify the current model and parameters, then set these environment variables on your server. Replace any YOUR_* placeholders with confirmed supported values.

export ALLGATE_BASE_URL='https://api.allgate.ai/v1'
export ALLGATE_API_KEY='YOUR_API_KEY'

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["ALLGATE_API_KEY"],
    base_url=os.environ.get("ALLGATE_BASE_URL", "https://api.allgate.ai/v1"),
    max_retries=0,
)

completion = client.chat.completions.create(
    model="gemini-4-argon",
    messages=[{"role": "user", "content": "Hello, Allgate!"}],
)
print(completion.choices[0].message.content)

Check models and current availability

These entries come from the public catalogue build snapshot. A listing does not guarantee endpoint capability or continuing supply. For audio, verify synthesis or transcription support separately. Open a model to check its exact ID, settings and billing unit.

Catalogue snapshot: 2026-10-30

• Gemini 4 ArgonGoogle · Available route in snapshot
• Gemini 3.8 FlashGoogle · Available route in snapshot
• Gemini 3.5 FlashGoogle · Available route in snapshot
• Allgate FusionAllgate · Available route in snapshot
• Claude Fable 5.1Anthropic · Available route in snapshot
• Claude Haiku 5.5Anthropic · Available route in snapshot

Costs and workflow limits

Changing the SDK endpoint does not preserve a previous provider price. Review Allgate input and output token rates for the exact model, then check any applicable account quote. Balance, access controls and current route availability still apply. The SDK example below is displayed for inspection and does not execute a request.