Skip to main content

Overview

The LLM Gateway exposes one gateway URL, https://llm-gateway.aptible.com, and speaks several API dialects from it. Pick whichever matches how you’re already integrating:
  • OpenAI-compatible — Chat Completions, Responses, and Embeddings, in both a strict /openai namespace and as un-namespaced defaults
  • Anthropic-compatible — Messages, in a strict /anthropic namespace
  • Agent harnesses — a dedicated, never-changing base URL per supported coding assistant or agent harness, under /harness/<name>
Every request authenticates with an LLM Key and selects a model by name in the request body — see Supported Models for the current model catalog.

Authentication

Send your LLM Key as a bearer token:
Anthropic’s SDKs (and Claude Code) instead send an x-api-key header — the gateway accepts either:

OpenAI-compatible API

Use the /openai namespace for strict OpenAI compatibility: The same three endpoints are also available un-namespaced (/v1/chat/completions, /v1/responses, /v1/embeddings) as the gateway’s default dialect — use whichever your SDK or tooling expects. For full request and response documentation, see OpenAI’s API reference.

Anthropic-compatible API

Use the /anthropic namespace for Anthropic Messages: For full request and response documentation, see Anthropic’s API reference.

Agent harness support

Some coding assistants and agent harnesses need a single base URL they can be pointed at once and never have to edit again — even as the underlying API dialect they speak evolves. The LLM Gateway provides one under /harness/<name>, which resolves internally to the right compatibility endpoint: See the Claude Code guide for a full walkthrough of harness setup.
Don’t see your harness or coding assistant listed? Any tool that speaks OpenAI- or Anthropic-compatible APIs already works against the /openai or /anthropic endpoints above — a dedicated /harness route just saves you from ever having to change the base URL again. Contact us if you’d like a harness added.

Example requests

Every example below uses the model field to select a model — see Supported Models for valid IDs.

Automatic provider failover and client-side fallbacks

If a model is available from more than one provider, the gateway automatically fails over to another available provider during an outage — no client changes required. You can also specify your own fallback models in a request; see Supported Models for details on both.