Skip to main content

Developers

05 Developer experience

Change one line: base_url.

Your existing OpenAI SDK keeps working. Point it at Allgate and auth, routing, billing and logging happen automatically — or call the native protocols directly.

Your first API request

  1. 01 Choose a model from the live catalogue.
  2. 02 Create an API key and set your environment variables.
  3. 03 Send a request, then verify its usage and cost.

Base URL

https://api.allgate.ai/v1

Public production endpoint; call it directly with your API key.

  • OpenAI-compatible
  • SSE streaming
  • tool calls
  • multimodal input
  • OpenAI SDK compatible
  • All endpoints
  • 5-minute setup
Create an account and get a key
console · code
export ALLGATE_BASE_URL='https://api.allgate.ai/v1'
export ALLGATE_API_KEY='YOUR_ALLGATE_API_KEY'

curl --fail-with-body "$ALLGATE_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $ALLGATE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{
  "model": "deepseek-flash",
  "messages": [
    {
      "role": "user",
      "content": "Hello, Allgate!"
    }
  ]
}'
ALLGATE GATEWAY · OPENAI COMPATIBLE Live

Compatible endpoints

  • POST /v1/chat/completions
  • POST /v1/messages
  • POST /v1/responses
  • POST /v1/embeddings
  • POST /v1/images/generations
  • POST /v1/audio/speech
  • POST /v1/audio/transcriptions
  • POST /v1/videos/generations
  • POST /v1/rerank
06 ILLUSTRATIVE ROUTING DEMO

A fallback path, when you configure one.

Configured standby channels let compatible requests try another route after certain upstream failures. This simulation explains the flow; it is not a live latency or uptime measurement.

Demo data illustrating the routing policy; real latency depends on upstream and network.

live path POST /v1/chat/completions

Stable · all upstreams healthy

idle

Requests

Upstream nodes

primary
OpenAI
secondary
Anthropic
tertiary
Google Gemini

weight

42%

latency

42ms

Failed requests are not billed; retries only occur on upstream failure.

Before you choose a model.

How do I connect to the Allgate API?
Create an account and API key, set your application base URL to https://api.allgate.ai/v1, and choose a currently available model ID from the public catalogue. Send the key as a Bearer token. Keep API keys on your server, outside browser code.
Does a documented endpoint guarantee model availability?
The API reference describes request formats. The live catalogue lists models and their current routing availability. An endpoint or reference index entry does not mean that every model or capability has an available route.
Where can I check request formats and costs?
The public API reference covers authentication, request shapes, streaming and errors. Model detail pages publish billing units and base rates; your console shows the applicable account price.

Catalogue snapshot: · Public model data · Models and prices · Image and video Studio · API reference