One alias in
front of Anthropic.
Your application calls a Relays alias. Relays holds the Anthropic credential, applies the route policy, and hands back the provider response in the shape your SDK expects.
- Platform
- Anthropic
- Lines
- Messages
- Credential
- ANTHROPIC_API_KEY
- Setup
- Registry route
- Base URL
- https://api.anthropic.com/v1
The route.
Relays exposes the native Messages edge, including streaming, thinking, tool payloads, and MCP configuration where the selected route can honor the request.
- Your applicationSends the Anthropic request it already sends.
- RelaysHolds the key, picks the candidate, writes the receipt.
- AnthropicReceives the call on its own base URL.
Who can cover
for Anthropic.
Messages routes can fall back only to configured Anthropic-compatible candidates that satisfy the requested capabilities. Relays does not flatten Messages into Chat Completions for cross-protocol fallback.
No other line serves Messages
Models at the edge.
Model IDs sit behind a Relays alias, so a catalogue change at Anthropic never reaches your code.
No Anthropic catalogue is published on this page. Route candidates are still set by model ID in your route configuration.
Measured,
and not yet.
Availability comes from Anthropic. Latency, error rate, and cost per successful request come from your own traffic, so Relays leaves them empty until requests run.
- Upstream status
No public feed
Anthropic does not publish a status feed Relays can read, so no availability is reported here.
- Relays measurements
No sample yet
Time to first token, error rate, and cost per successful request are read from requests that ran through Relays. This route has none, so there is nothing to plot.
Ask for an API key
Every route carries a policy.
A route is a list of candidates, a budget, and a record of what happened. You set all three before any traffic runs.
- Candidates
- Fallbacks stay inside the contract: only connections on a shared line can take the call. How a route is chosen
- Ceiling
- An alert threshold and a stop threshold for this route, checked before the call goes upstream.
- Receipt
- Every call records the alias, the candidates tried, each status, tokens in and out, and the estimated cost. Read a route receipt
One endpoint is enough to start.
Keep the client you already wrote. Bring us the workload and we will map the first Anthropic route with you.
