Trusted by 12,000+ developers

IntelligenceDesigned To Evolve

One API key, one OpenAI-compatible endpoint, and 250+ models across 40+ providers.
Route, fail over, and see every request without changing your code.

Get API Key

Gateway at a glance

  • 42msRouting overhead, p50
  • 99.99%Platform uptime
  • 250+Models via one API key
  • 2.4MMax context across available models

Providers

Plays well with the models you already use.

Forty providers behind one endpoint. Pick model names, not SDKs and secrets.

  • OpenAI
  • Anthropic
  • Google
  • Meta
  • Mistral
  • xAI
  • Cohere
  • DeepSeek

Compatibility, not endorsement. AI Runtime routes your request to these providers — none of them are customers.

How it works

One request. Any model.

Your request arrives once. The gateway picks the route, wears the failures, and returns one response with the full story of how it was served.

Request routing through the gatewayYour client sends one request to the AI Runtime gateway. The gateway forwards it along the best of several provider routes and returns a single response.Your appone requestGatewayroute + cacheABC
  • 42msp50 routing overhead on top of the provider call
  • 40+providers reachable through one key
  • 250+models addressable without code changes
Diagram: your app sends one request to the gateway, which routes it to one of 40+ providers and returns a single response.

Quickstart

Working in about thirty seconds.

Create a key, export it, paste one snippet. The endpoint is OpenAI-compatible, so your existing SDK works unchanged.

cURL
curl https://api.airuntime.dev/v1/chat/completions \
  -H "Authorization: Bearer $AI_RUNTIME_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "auto",
    "messages": [{ "role": "user", "content": "Explain vector search in one paragraph." }]
  }'

  1. 1Create a key — no card, 1M tokens free.
  2. 2Export it as AI_RUNTIME_KEY.
  3. 3Run the snippet. First response in seconds.

Using your own provider keys instead? Attach them and the router keeps your negotiated rates. Nothing else in the request changes.

Capabilities

Built for the second request, not the first.

Four things that keep working after the demo: routing that adapts, failover that is invisible, caching that pays, and a trace for every call.

Smart routing

Each request is matched to the model that fits its cost, latency, and capability profile. No model list to maintain, no per-provider SDK to wire up.

42msrouting overhead, p50

Automatic failover

When a provider degrades, the request is retried against the next best route before your timeout budget is spent. Your users get a response, not a 529.

<80msfailover decision

Response caching

Identical prompts reuse a stored completion. Cache hits cost nothing and return in single-digit milliseconds, which is where most of the savings actually come from.

38%median cache hit rate

Per-request observability

Every call logs the route taken, tokens in and out, cache status, latency, and cost. One trace per request instead of a dashboard you have to reconcile.

1 traceper request

Pricing

Free until it earns a bill.

Usage is billed per token at the provider rate plus a routing fee. No seat pricing, no minimum, no surprise platform tier.

  • Free

    Enough to ship a side project and find out whether this fits.

    $0per month

    • 1M tokens per month
    • All 250+ models
    • Smart routing and failover
    • 7-day request logs
    Get API key
  • Scale

    For teams with committed spend and a security review to pass.

    Customannual

    • Volume pricing per token
    • Dedicated provider capacity
    • SSO and audit log export
    • 99.99% uptime SLA
    • Shared Slack channel
    Talk to us

Every plan includes smart routing, automatic failover, and per-request traces. The difference is volume, log retention, and how much of the routing decision you control.

Questions

The things developers ask before the second request.

Do I need accounts with every provider?

No. You hold one AI Runtime key and we hold the provider relationships. If you already have your own provider keys, you can attach them and keep your negotiated rates instead.

Is the API OpenAI-compatible?

Yes. Point the OpenAI SDK at our base URL and change nothing else. Model names follow the provider/model convention, so switching a model is a one-line diff and never a rewrite.

What happens when a provider goes down?

The router retries the next best route inside your timeout budget, and the response carries a header telling you which route served it. If every route fails you get one error with the full attempt list, not a silent retry loop.

Do you train on my prompts?

No. Requests are proxied to the provider you route to and are not used for training. Logs are kept for the window your plan specifies, then deleted, and paid plans can turn logging off entirely.

How is usage billed?

Per token at the provider rate plus a routing fee, both itemised per request. The free tier is 1M tokens per month with no card. Paid plans bill the included allowance first, then per token.

Can I pin a specific model instead of routing?

Yes. Send an explicit model name and the router steps aside. Routing is a default, not a cage: you can pin per request, per endpoint, or per environment.

Start here

Your first request is thirty seconds away.

Create a key, point your existing OpenAI client at the gateway, and watch the route it takes. A million tokens a month are free, no card.

No card. No sales call. Cancel a plan without emailing anyone.