Airside for Providers

Airside is the self-serve console for the companies behind the models — the providers LLM Gateway routes to. It runs on an airport metaphor: LLM Gateway is the airport, developers are passengers, and providers are carriers. As a carrier you claim your provider, register your fleet of models, file your fares, and watch traffic arrive.

Claiming your carrier

Sign up at airside.llmgateway.io with your company email and verify it. A catalogue provider is claimable when the registrable domain of your verified email matches the registrable domain of the provider's API endpoint (or its website) — if your API is served from api.example.ai, an @example.ai address can claim it. Subdomains collapse to the registrable domain, so ops@mail.example.ai works too.

Every claim is reviewed by the LLM Gateway team before the carrier goes live; a rejected claim shows the review note so you can follow up. One company can operate several carriers — regional deployments or separate brands all live under one console.

Listing on llmgateway.io carries a one-time $2,500 listing fee per provider company, paid during onboarding. Providers we already work with receive an invite code that waives it — entered in the same onboarding step instead of paying. See the pricing summary for the full economics.

Crew

A listing covers your whole team. Under Crew, company owners invite teammates by email — up to 10 members per company, pending invites included. Invites are limited to your team's domains (the ones that prove your claims); a teammate with an existing account joins instantly, anyone else joins the first time they sign in with the invited address.

Registering a new carrier

Not in the provider catalogue yet? Register your provider as a new carrier from the onboarding page: pick a carrier id, display name, and the base URL of your OpenAI-compatible API (the gateway calls <base URL>/v1/chat/completions). The endpoint must live on your verified email's domain — the same anti-squatting rule as claiming — and registrations go through the same review. Once approved, your carrier appears on the public providers and models pages and its listings route like any other provider's.

Listing your fleet

Once your claim is active, register models under Fleet: model name, display name, description, context size, max output, capability flags (streaming, vision, audio input, tools, JSON output, reasoning), and the supported reasoning_effort tiers. A new listing is created as a draft together with an initial price filing; when the LLM Gateway team approves that filing, the model goes active. Everything except pricing stays freely editable afterward.

Carriers claiming a catalogue provider can also import their catalogue models in one click: each active catalogue model becomes a managed listing with its current price as an approved filing. Routing keeps using the catalogue entry until the LLM Gateway team retires it — from then on the Airside listing (and its filed fares) takes over. This is how a provider's models migrate from the static catalogue into carrier self-management.

Price filings

Listed prices are what developers are billed, so pricing never changes silently: it only changes through a reviewed price filing.

• The initial filing sets the launch pricing and activates the model on approval.
• Every later price change is an update filing — drafted by you, approved by the LLM Gateway team, and only then in effect.

A filing covers input, output, optional cached-input, and optional per-request prices (USD per token, decimal or exponent notation), plus a note for the reviewer. The latest approved filing is the model's effective price; pending and rejected filings are tracked under Filings.

Routing and billing

Approved listings are genuinely routable. A request for <provider>/<model> that does not match the static catalogue resolves against active Airside listings with an approved price filing, and is billed at the filed prices — no extra configuration on the developer side.

Traffic

The Traffic page shows usage of your claimed providers: requests, errors, input/output/total tokens, and billed traffic in USD, as a daily series and broken down per model.

Fares and routing

Under Fares each claimed provider has two knobs:

• Traffic discount (0–50%) — a discount you offer on routed traffic.
• Landing fee (5–50%) — the gateway margin you accept; the baseline is 20%.

Accepting more than the baseline margin or offering a discount makes your traffic effectively cheaper, which boosts you in the smart routing election; accepting less prices you up. Like price changes, fare changes are filed for review and only reach routing once the LLM Gateway team approves them. The election scores every candidate provider on weighted factors — price after your discount and margin (0.6), availability/uptime (0.5), prompt-cache support (0.2), throughput (0.05), and latency (0.025) — and the lowest score wins.

Carrier Slack channel

Every new carrier is invited to a shared cross-team Slack Connect channel with the LLM Gateway team — the fastest way to reach us about claims, filings, or routing.