What is an LLM API listing?
A listing makes a provider’s deployment available through LLM Gateway. Airside is the provider console used to verify ownership, register models, submit prices and inspect aggregate traffic. A verified domain establishes ownership; the provider claim, model checks and initial pricing still need clearance before a deployment enters service.
1. Prepare your provider identity
Use a company email and verify it. Have your API base URL and public website ready. The domain checks connect those addresses to the provider you want to claim. If your email and API domains differ, follow the website verification flow in onboarding. Existing catalogue providers can be claimed; a new provider can register a custom carrier.
Onboarding shows the applicable listing fee or invite-code option before submission. Read the provider terms before registering.
2. Match the canonical model ID
The canonical model ID identifies the model across providers. The upstream model ID is the identifier your own API accepts. If the model already exists in the catalogue, use its exact canonical ID so users can compare deployments. Airside reuses its display name, description and family. A new model needs its own identity metadata.
Check the live model catalogue before adding a model. Providers with existing mappings should use the catalogue import action in Fleet.
3. Declare and verify the deployment
Keep Carrier default selected unless this deployment needs a different upstream API format. Enter the context window, output limit and capabilities your endpoint actually supports. Choose rate limits that your infrastructure can sustain, including whether a limit covers all organizations or applies separately to each one.
Run preflight verification with your managed carrier key or a key supplied for that run. Resolve failed checks before submitting the model. Changing the verified mapping requires a new verification.
4. Submit prices for review
Enter input, output and cached-input prices per million tokens; a per-request charge uses a flat amount. For an existing canonical model, “Use catalog price” copies a selected provider’s available flat tariff for you to review. This is a starting point for your own filing. It does not bypass approval or support copying complex tiered pricing.
Estimate the effect of your rates with the token cost calculator. Initial fares and later price changes take effect only after approval.
5. Review demand and your routed traffic
The public model rankings show usage on LLM Gateway. Use them to explore demand, then compare with the aggregate requests, errors and tokens in your Airside Traffic page. Rankings describe gateway usage, not the entire inference market, and do not guarantee future traffic to a provider.
Can a provider see prompts or customer identities?
Airside’s traffic reports contain aggregate activity for the provider’s routes. They do not expose other organizations’ identities or request and response payloads. See the Airside documentation for the operating workflow.