Connect to the Gateway

The Wardin gateway speaks the Anthropic Messages API format for every model it routes — Claude, GPT, Bedrock, and Gemini included. Point an Anthropic-compatible SDK at the gateway URL, swap in your virtual key, and pass whichever model name you want to reach (see Providers) — no other code changes.

Gateway URL

https://gw.wardin.ai

Authentication

The gateway accepts your virtual key in either header:

Authorization: Bearer wardin_sk_... (canonical)
x-api-key: wardin_sk_... (what the Anthropic SDK’s api_key mode sends)

Supported protocols

Protocol	Endpoint	Use for
Anthropic Messages API	`/v1/messages`	All chat models — Claude, GPT, Bedrock, Gemini, by model name
Embeddings	`/v1/embeddings`	Text embedding models

There is no OpenAI-compatible /v1/chat/completions endpoint. To reach a GPT model, send the request in Anthropic Messages format to /v1/messages with a gpt-* model name — the gateway resolves the model to its provider and translates the request/response shape.

SDK examples

curl https://gw.wardin.ai/v1/messages \
  -H "Authorization: Bearer wardin_sk_YOUR_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-opus-4-8",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Hello"}]
  }'

import anthropic

client = anthropic.Anthropic(
    api_key="wardin_sk_YOUR_KEY",
    base_url="https://gw.wardin.ai",
)

import Anthropic from '@anthropic-ai/sdk';

const client = new Anthropic({
  apiKey: 'wardin_sk_YOUR_KEY',
  baseURL: 'https://gw.wardin.ai',
});

curl https://gw.wardin.ai/v1/messages \
  -H "Authorization: Bearer wardin_sk_YOUR_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "gpt-4o",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Hello"}]
  }'

export ANTHROPIC_AUTH_TOKEN=wardin_sk_YOUR_KEY
export ANTHROPIC_BASE_URL=https://gw.wardin.ai

Streaming

Streaming works without any changes. The gateway transparently forwards server-sent events (SSE) from the provider to your client. Token usage is parsed from the final message_delta event for billing.

with client.messages.stream(
    model="claude-opus-4-8",
    max_tokens=1024,
    messages=[{"role": "user", "content": "Tell me a story"}],
) as stream:
    for text in stream.text_stream:
        print(text, end="", flush=True)

Request attribution headers

Add these optional headers to improve analytics granularity:

Header	Description
`X-Wardin-Session-Id`	Groups multiple requests into a session (e.g., one coding task)
`X-Wardin-Prompt-Id`	Links the request to a prompt in the Prompt Registry
`X-Wardin-Prompt-Version-Id`	Pins the request to a specific prompt version

If X-Wardin-Session-Id is not provided, the gateway groups requests using idle-timeout bucketing (30-minute sliding window). See Sessions. User attribution comes from the virtual key’s owner — issue one key per developer rather than sharing keys.

Response headers

Header	Description
`X-Wardin-Cache`	Present when the response was served from cache: `HIT` (L1 exact match) or `SEMANTIC` (L2 similarity match)

Health check

curl https://gw.wardin.ai/health
# {"status":"ok"}

Getting Started

Concepts

Gateway

Guides

Connect to the Gateway

Gateway URL

Authentication

Supported protocols

SDK examples

Streaming

Request attribution headers

Response headers

Health check

​Gateway URL

​Authentication

​Supported protocols

​SDK examples

​Streaming

​Request attribution headers

​Response headers

​Health check

Gateway URL

Authentication

Supported protocols

SDK examples

Streaming

Request attribution headers

Response headers

Health check