Skip to main content
The MetrixLLM gateway provides a drop-in proxy for Anthropic’s Messages API. Use your existing Anthropic SDKs or raw HTTP requests by changing only the Base URL and API key.

Base URL

Authentication

All requests require a MetrixLLM API key. The gateway accepts both formats:
Do not use your Anthropic API key. The gateway authenticates requests using MetrixLLM keys (sk-metrix-* prefix). The gateway then uses its own provider keys (or your BYOK keys) to call Anthropic.

Internal Authentication

For backend-to-gateway communication, the gateway supports internal authentication: Internal auth skips the standard API key validation. Used by the MetrixLLM backend for playground, replay, and batch operations.

Endpoints


Request Headers

Every request supports these headers: Session Tracing Use these headers to group related requests into sessions and trace spans: Custom Properties Attach up to 10 custom metadata properties per request: Example: metrix-property-team: engineering, metrix-property-environment: production Worker-to-Gateway These headers are set by the Cloudflare Edge Worker when routing through the Durable Object balance system: IP Detection

Messages

Request Body

Send standard Anthropic Messages API requests. The gateway accepts all standard Anthropic fields plus MetrixLLM-specific extensions.

Message Format

Messages follow the standard Anthropic format with content blocks:

Examples

Response Body

Response Headers

Every successful response includes these headers: On cache HIT responses, only Content-Type and X-Metrix-Cache-Status: HIT are returned. On rate limited responses (429 Too Many Requests):

Streaming

Set "stream": true to receive Server-Sent Events (SSE) in Anthropic’s streaming format.

Thinking (Extended Thinking)

Enable extended thinking for deeper reasoning. The gateway converts between Anthropic’s thinking format and other provider formats automatically.
When using the gateway’s generic proxy (/v1/chat/completions), you can use a simplified thinking field: "low" (1000 tokens), "medium" (5000 tokens), or "high" (10000 tokens). The gateway converts these to the appropriate provider-specific format.

Tool Use

Define tools using Anthropic’s native format. The gateway automatically converts between tool formats when routing to different providers.

Tool Choice

Control tool selection with tool_choice:
Enable web search to give the model access to real-time information. Additional parameters:

Native Web Search Example


Prompt Management

Use prompt_id to reference a stored prompt template. The gateway fetches the template, renders {{variable}} placeholders with values from inputs, and sends the rendered messages to the provider.

Error Responses

Errors return a JSON body following Anthropic’s error format. The HTTP status code indicates the error type.

Error Response Format


Retry and Fallback

The gateway automatically retries failed requests and falls back to alternative providers:
  • Retry: Retries on 429, 500, 502, 503, 504 status codes with exponential backoff
  • Fallback: If the primary provider fails, the gateway tries the next configured provider in the chain
  • Circuit Breaker: Providers with repeated failures are temporarily skipped (circuit opens for 60 seconds)
  • Cerebras Fallback: If all configured providers fail on system errors, the gateway falls back to Cerebras (if enabled)
These features are transparent to your application — you receive a single successful response.

Mode Override

Control provider key selection with the mode field: