LLM Client Integrations

Client entry point

Use the gateway URL where tools expect an OpenAI or Anthropic endpoint.

AI Model Gateway keeps upstream provider keys in the gateway config. Local tools and SDKs receive a gateway client key and send traffic to the data-plane listener.

OpenAI-compatible SDKs

Set OPENAI_BASE_URL to the gateway origin plus /v1, then use the gateway client key.

Codex

Use aigw clients print or aigw clients apply to target the local Codex config.

Claude Code

Route Anthropic Messages-style clients through the gateway with ANTHROPIC_BASE_URL.

OpenClaw

Add AI Model Gateway as a provider and keep provider-specific secrets out of the tool config.

Base URL

One local endpoint for client traffic.

For a default local runtime, OpenAI-compatible clients use the gateway origin plus /v1. The same gateway origin is also used for Anthropic Messages-style client base URL settings.

export OPENAI_BASE_URL="http://127.0.0.1:18080/v1"
export OPENAI_API_KEY="$GATEWAY_API_KEY"

export ANTHROPIC_BASE_URL="http://127.0.0.1:18080/v1"
export ANTHROPIC_AUTH_TOKEN="$GATEWAY_API_KEY"

Open client integration details

AI Model Gateway overview workspace after routing client traffic

Safe update flow

Preview local tool config changes before writing them.

The CLI can print snippets or apply config updates for supported tools. Start with a dry run and keep backups enabled unless another system already owns those files.

Start runtime. Run the packaged release, Docker Compose path, or source build.
Print snippets. Inspect generated client settings before changing local files.
Dry run. Use aigw clients apply -dry-run for Codex, Claude Code, or OpenClaw.
Smoke test. Send one request and inspect gateway logs, provider health, and telemetry.

Client integration guide CLI guide Codex CLI gateway page Messages endpoint OpenAI-compatible upstreams Troubleshooting

Review evidence

Check installability, quality, and security before adopting it.

Release archive install

Try the packaged v1.4.4 runtime with checksum verification, local config, runtime directories, and supervised startup commands.

Open release install path

Quality evidence

Review CI gates, local reproduction commands, runtime smoke checks, feature proof points, and current capability boundaries.

Open quality evidence

Security and trust model

Inspect admin auth, same-origin browser writes, provider-key handling, SSRF defenses, telemetry sensitivity, and update trust.

Open security model

Next step

Connect one client, then decide whether the gateway earns a star.

Start with a local gateway and one non-production request. If the project fits your client-routing workflow, starring the repository helps other operators find it.

Star on GitHub Leave feedback