Anthropic Messages API

SMG serves the Anthropic Messages API at /v1/messages and counts input tokens at /v1/messages/count_tokens. What happens to a request depends on the backend: with gRPC workers SMG implements the API itself, with HTTP workers it forwards the request to an engine that implements the Messages API, and with the Anthropic backend it forwards the request to the Anthropic API.


Endpoints

Method Path Description
POST /v1/messages Create a message. Set "stream": true to receive Server-Sent Events.
POST /v1/messages/count_tokens Count the input tokens of a Messages request without generating.

Both endpoints go through the same authentication and admission control as the other inference endpoints.


Supported Backends

Backend Configure with /v1/messages /v1/messages/count_tokens
gRPC workers grpc:// worker URLs SMG renders, tokenizes, and parses (details) Counted by SMG itself (details)
ZMQ workers ipc:// or tcp:// worker URLs Same as gRPC workers Same as gRPC workers
HTTP workers http:// or https:// worker URLs Forwarded to the worker Forwarded to one worker
HTTP PD --pd-disaggregation with HTTP workers Prefill/decode dual dispatch Forwarded to one prefill worker
Anthropic API --backend anthropic Forwarded to the Anthropic API, with an optional SMG-run MCP tool loop 501 Not Implemented

HTTP workers must implement the Messages API themselves; SMG forwards the request without translating it.

In IGW mode (--enable-igw), SMG picks the backend per request from the workers that serve the requested model. A model served by an external Anthropic worker goes to the Anthropic API backend (see External Providers). The other external providers answer /v1/messages with 501.


Authentication

SMG's own authentication is separate from the credentials it passes to backends:

Hop Headers Behavior
Client to SMG Authorization: Bearer <key> Checked when --api-key or --tenant-api-key is set. x-api-key does not authenticate to SMG. A missing or unknown bearer token gets 401 Unauthorized.
SMG to HTTP workers Authorization The client's header is forwarded with the other allowlisted headers; x-api-key is not. A matched gateway key is removed at authentication, and the worker's own configured key, when it has one, is sent instead. See Authentication for worker API keys.
SMG to the Anthropic API x-api-key, Authorization The client's own key headers are forwarded as sent. When the client sends neither, SMG sends the worker's stored key as x-api-key, with anthropic-version: 2023-06-01 added when the client sent no version header.

Anthropic SDKs send their key in x-api-key, which the Anthropic API backend passes upstream. When gateway authentication is on, clients must also send the gateway key as Authorization: Bearer <key>. The gateway key never reaches Anthropic: it is removed from Authorization at authentication, and from x-api-key too when sent there, while the client's own Anthropic key in x-api-key passes through.


Create a Message

POST /v1/messages

Request Body

Field Type Required Description
model string Yes Model ID. Must not be empty.
messages array Yes At least one message, each with a role (user, assistant, or system) and content (a string or an array of content blocks).
max_tokens integer Yes Maximum number of tokens to generate. 0 is accepted; the response depends on the backend — see max_tokens of 0.
system string or array No System prompt, as a string or an array of text blocks.
stream boolean No Stream the response as Server-Sent Events.
temperature number No Sampling temperature.
top_p number No Nucleus sampling.
top_k integer No Sample only from the top K tokens.
stop_sequences array of strings No Sequences that stop generation.
tools array No Tool definitions; see Tool Use.
tool_choice object No {"type": "auto"}, {"type": "any"}, {"type": "tool", "name": "..."}, or {"type": "none"}. Every value except none requires tools, and tool must name one of them. auto, any, and tool also take disable_parallel_tool_use; when true, gRPC and ZMQ workers return only the first tool call of the turn.
thinking object No {"type": "enabled", "budget_tokens": N}, {"type": "adaptive"}, or {"type": "disabled"}. enabled and adaptive also take display (summarized, omitted, or updates).
output_config object No effort is read as Chat's reasoning_effort is (a string, or a number as its text; another type is refused) and rendered into the prompt on gRPC and ZMQ workers. A structured output format under output_config.format, or the top-level output_format field, is refused by gRPC and ZMQ workers with 400 (unsupported_output_format); HTTP workers and the Anthropic API receive these fields as sent.
metadata object No Request metadata (user_id).
service_tier string No auto or standard_only.
container object No Container for code execution (beta).
mcp_servers array No MCP servers for the request (beta). Required when tools has an mcp_toolset entry; see MCP Tools.
rid string No Extension: request ID passed to the backend for log correlation.

SMG applies the public API's request rules before routing and answers 400 when one is broken:

  • Each entry of messages carries only role and content; an unknown field in a message is refused.
  • Every message needs non-empty content, and every text block non-empty text. The one exception is a final assistant message — a prefill the response continues — which may be empty but may not end in whitespace.
  • temperature and top_p take the range 0 to 1.
  • Each tool_use id must be answered by exactly one tool_result block in the next user turn, and a tool_result must answer a tool_use of the assistant turn right before it. Consecutive messages of one role count as one turn, as the public API combines them.
  • Each stop sequence must contain non-whitespace text.
  • Tool names must be unique. A custom tool's name must match ^[a-zA-Z0-9_-]{1,128}$, its input_schema must describe an object, and an unknown field in its definition is refused (the public API's own newer fields, such as strict or input_examples, pass through).
  • thinking.budget_tokens starts at 1024, and must stay under max_tokens unless the anthropic-beta header lifts that rule; see Request Headers.

These rules are skipped only for a body that the HTTP router streams through unparsed; see HTTP and PD Workers. Fields SMG does not model, such as context_management, are kept and forwarded to HTTP workers and the Anthropic API.

Content blocks in messages may be text, image, document, tool_use, tool_result, thinking, redacted_thinking, server_tool_use, search_result, web_search_tool_result, tool_search_tool_result, or tool_reference. Any other block type is rejected with 400. A system-role message inside messages is accepted, because some clients send one mid-conversation.

Example Request

curl http://localhost:30000/v1/messages \
  -H "Content-Type: application/json" \
  -H "anthropic-version: 2023-06-01" \
  -d '{
    "model": "meta-llama/Llama-3.1-8B-Instruct",
    "max_tokens": 1024,
    "system": "You are a concise assistant.",
    "messages": [
      {"role": "user", "content": "What is the meaning of life?"}
    ]
  }'
curl http://localhost:30000/v1/messages \
  -H "Content-Type: application/json" \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -d '{
    "model": "claude-sonnet-4-20250514",
    "max_tokens": 1024,
    "messages": [
      {"role": "user", "content": "What is the meaning of life?"}
    ]
  }'

Response

{
  "id": "msg_abc123",
  "type": "message",
  "role": "assistant",
  "content": [
    {"type": "text", "text": "There is no single answer..."}
  ],
  "model": "meta-llama/Llama-3.1-8B-Instruct",
  "stop_reason": "end_turn",
  "stop_sequence": null,
  "usage": {
    "input_tokens": 27,
    "output_tokens": 112,
    "cache_creation_input_tokens": 0,
    "cache_read_input_tokens": 0,
    "cache_creation": {"ephemeral_5m_input_tokens": 0, "ephemeral_1h_input_tokens": 0},
    "service_tier": "standard",
    "inference_geo": "not_available"
  }
}

With gRPC workers SMG builds this response (details). With HTTP workers and the Anthropic API it comes from the backend.

max_tokens of 0

A max_tokens of 0 passes validation. On gRPC and ZMQ workers, SMG answers the request itself without generating: an empty message with stop_reason of max_tokens, whose usage reports the prompt's token count, counted exactly as /v1/messages/count_tokens counts it. No worker takes part, and no tenant rate-limit budget is reserved, though the request still counts in the gateway's request metrics.

{
  "id": "msg_abc123",
  "type": "message",
  "role": "assistant",
  "content": [],
  "model": "meta-llama/Llama-3.1-8B-Instruct",
  "stop_reason": "max_tokens",
  "stop_sequence": null,
  "usage": {
    "input_tokens": 27,
    "output_tokens": 0,
    "cache_creation_input_tokens": 0,
    "cache_read_input_tokens": 0,
    "cache_creation": {"ephemeral_5m_input_tokens": 0, "ephemeral_1h_input_tokens": 0},
    "service_tier": "standard",
    "inference_geo": "not_available"
  }
}

With "stream": true, the answer is a three-event stream: message_start with the empty message — its usage already carries the prompt's token count — then message_delta with the stop reason and the usage counts, and message_stop.

A request whose prompt cannot be counted is refused as /v1/messages/count_tokens refuses it — an unknown model gets 404, a request that does not render gets 400, and the other refusals under Backend Support apply unchanged. When the model's workers advertise a context window, a prompt with more tokens than the smallest advertised window is refused with 400 context_length_exceeded, as a generating request would be.

On HTTP and PD workers, SMG refuses max_tokens: 0 with 400 (code max_tokens_zero_not_relayed) before any worker sees the request: the relay forwards a Messages request as sent and renders no prompt, so it cannot build the empty message. As with the other request rules, a body the HTTP router streams through unparsed reaches the worker unvalidated.

The Anthropic API backend forwards the request like any other and relays the upstream response.

In IGW mode, a max_tokens: 0 request for a model served over both gRPC and HTTP always goes to a gRPC router, so it gets the empty message; a model only HTTP workers serve gets the relay's 400.

Tool Use

Define each tool with a JSON Schema input_schema:

{
  "tools": [
    {
      "name": "get_weather",
      "description": "Get the current weather for a city",
      "input_schema": {
        "type": "object",
        "properties": {"city": {"type": "string"}},
        "required": ["city"]
      }
    }
  ],
  "tool_choice": {"type": "auto"}
}

A tool call comes back as a tool_use block, with stop_reason set to tool_use:

{
  "content": [
    {
      "type": "tool_use",
      "id": "toolu_0b7e5f1c9a2d4e6f8a1b3c5d",
      "name": "get_weather",
      "input": {"city": "Paris"}
    }
  ],
  "stop_reason": "tool_use"
}

Return the result in the next user message as a tool_result block whose tool_use_id is the id of the call.


Streaming

Set "stream": true to receive the response as Server-Sent Events. Each event has an event: line naming its type and a data: line with the JSON payload. The stream ends with message_stop; there is no data: [DONE] line.

Event Payload
message_start The message, with empty content
content_block_start A new content block at index: thinking, text, or tool_use
content_block_delta A text_delta, thinking_delta, or input_json_delta (a fragment of the tool input JSON) for the block at index
content_block_stop The block at index is complete
message_delta stop_reason, stop_sequence, and the final usage
message_stop End of the message
ping Keep-alive. SMG writes one itself after 15 seconds of upstream silence on any open Messages stream, whatever the backend (--sse-keepalive-secs; 0 sends none); nothing is sent while events flow. Upstream ping events are relayed
error A failure after the stream started; see Errors

HTTP workers and the Anthropic API produce their own events, which SMG relays; the Anthropic API can send block and delta types beyond this table. A gRPC worker's stream for a short text answer looks like this:

event: message_start
data: {"type":"message_start","message":{"id":"msg_abc123","type":"message","role":"assistant","content":[],"model":"meta-llama/Llama-3.1-8B-Instruct","stop_reason":null,"stop_sequence":null,"usage":{"input_tokens":0,"output_tokens":0,"cache_creation_input_tokens":0,"cache_read_input_tokens":0,"cache_creation":{"ephemeral_5m_input_tokens":0,"ephemeral_1h_input_tokens":0},"service_tier":"standard","inference_geo":"not_available"}}}

event: content_block_start
data: {"type":"content_block_start","index":0,"content_block":{"type":"text","text":""}}

event: content_block_delta
data: {"type":"content_block_delta","index":0,"delta":{"type":"text_delta","text":"There is no single answer"}}

event: content_block_stop
data: {"type":"content_block_stop","index":0}

event: message_delta
data: {"type":"message_delta","delta":{"stop_reason":"end_turn"},"usage":{"output_tokens":112,"input_tokens":27,"cache_creation_input_tokens":0,"cache_read_input_tokens":0}}

event: message_stop
data: {"type":"message_stop"}

Count Tokens

POST /v1/messages/count_tokens

Returns the number of input tokens a Messages request would use, without generating. Who counts depends on the backend: on gRPC and ZMQ workers, SMG counts the tokens itself from the model's tokenizer; on HTTP workers, it forwards the request to a worker that implements the endpoint and relays the worker's response. See Backend Support.

Request Body

Field Type Required Description
model string Yes Model ID; selects the worker (HTTP) or the tokenizer (gRPC/ZMQ).
messages array Yes Conversation, in the same format as /v1/messages.
system string or array No System prompt.
tools array No Tool definitions.
tool_choice object No Tool selection.
thinking object No Thinking configuration.
output_config object No effort renders into the counted prompt as it renders on /v1/messages.

There is no max_tokens. Any other field, such as context_management or mcp_servers, is forwarded unchanged to HTTP workers; on gRPC and ZMQ backends such fields are accepted but take no part in the count, which uses only the fields above.

Example

curl http://localhost:30000/v1/messages/count_tokens \
  -H "Content-Type: application/json" \
  -H "anthropic-version: 2023-06-01" \
  -d '{
    "model": "meta-llama/Llama-3.1-8B-Instruct",
    "system": "You are a concise assistant.",
    "messages": [
      {"role": "user", "content": "What is the meaning of life?"}
    ]
  }'
{
  "input_tokens": 27
}

Backend Support

Deployment Behavior
HTTP workers Routed like any other request (routing policy, retries, circuit breaker, load tracking) to one worker's /v1/messages/count_tokens. 404 (model_not_found) when no worker serves the model.
HTTP PD Sent to one prefill worker. No decode worker is involved and no bootstrap fields are added. 503 (no_prefill_servers) when no prefill worker is available.
gRPC or ZMQ workers Answered by SMG itself from the model's tokenizer; no worker takes part, so regular, PD (--pd-disaggregation), and EPD (--epd-disaggregation) deployments all serve it. See below.
Anthropic API backend 501 Not Implemented
IGW mode A model with an external worker goes to that provider's backend (501). Otherwise any of the model's self-hosted pools answers — gRPC, ZMQ, HTTP, and PD alike, a disaggregated pool qualifying by its prefill workers alone. A model no pool serves, including an unknown model, gets 404 (model_not_found).

On gRPC and ZMQ backends, SMG renders the request through the model's chat template exactly as /v1/messages renders it — the same tool filtering by tool_choice and the same media placeholders — and returns the rendered prompt's token count. Media is not fetched: an image counts as the placeholder the template writes for it, and a document counts as its text (a document source with no text is refused, as /v1/messages refuses it).

That path refuses a request the way /v1/messages would. An unknown model gets 404 (model_not_found), even when a removed worker's tokenizer is still registered.

A served model whose tokenizer the gateway is still loading gets 503 (tokenizer_not_ready) with a Retry-After: 1 header. A served model whose tokenizer will not load on its own — no path to load it from, the load failed, or the tokenizer was removed — gets 503 (tokenizer_load_failed) with no Retry-After and a message naming the reason. Retrying changes nothing until a tokenizer registers for the model, either by a worker re-registering with a usable path or by POST /v1/tokenizers. Under --disable-tokenizer-autoload, a served model with no tokenizer and no such load failure gets 500 (tokenizer_not_found).

A request that does not render gets 400 (process_messages_failed), and a rendered prompt that fails to encode gets 500 (tokenization_failed).


Request Headers

Headers specific to the Messages API:

Header Effect
X-SMG-MCP enabled makes SMG run the MCP tool loop itself for a request whose tools include an mcp_toolset entry, on the Anthropic API backend. See MCP Tools and MCP. Other backends ignore it, and SMG does not forward it.
anthropic-version Checked on /v1/messages and /v1/messages/count_tokens before routing: the value must be a real calendar date of 2023 or later, written YYYY-MM-DD. Anything else, including an impossible date such as 2023-02-30, is refused with 400 (invalid_anthropic_version). A request without the header is served, and a valid value does not change how SMG handles the request. Forwarded to HTTP and PD workers and to the Anthropic API.
anthropic-beta Read on /v1/messages for one rule: an entry starting with interleaved-thinking lets thinking.budget_tokens be at or above max_tokens; without it, such a budget is refused with 400 (thinking_budget_exceeds_max_tokens). Forwarded to HTTP and PD workers and to the Anthropic API.
x-api-key Not used to authenticate to SMG. Forwarded only to the Anthropic API; a gateway key sent there is removed at authentication. See Authentication.

Like the request-body rules, the anthropic-version and anthropic-beta checks are skipped for a /v1/messages request whose body the HTTP router streams through unparsed (see HTTP and PD Workers). A /v1/messages/count_tokens body is always buffered, so its anthropic-version check always runs.

Forwarded Headers

For HTTP and PD workers, SMG forwards only these request headers (it sets Content-Type itself):

Header Purpose
Authorization Credentials for the worker; see Authentication
anthropic-version, anthropic-beta API version and beta features for engines that serve /v1/messages
x-request-id, x-correlation-id, and any header starting with x-request-id- Request correlation
traceparent, tracestate W3C trace context
x-smg-routing-key SMG routing hint
x-override-priority SGLang's request priority, read by an engine started with SGLANG_ENABLE_REQUEST_HEADER_OVERRIDES=true and not by SMG

Every other request header, including x-api-key, is dropped. The Anthropic API backend forwards a different set — Authorization, x-api-key, anthropic-version, and anthropic-beta — and nothing else. When the request carries neither Authorization nor x-api-key (a gateway key is removed at authentication), SMG adds the worker's stored key as x-api-key, with anthropic-version: 2023-06-01 when that header is absent. gRPC and ZMQ workers receive a tokenized request, not HTTP headers.


gRPC and ZMQ Workers

With gRPC workers (SGLang, vLLM, TensorRT-LLM, TokenSpeed, or MLX), and ZMQ workers that use the same pipeline, SMG implements the Messages API itself. It renders the conversation with the model's chat template, tokenizes it, sends token IDs to the engine, and builds the Anthropic response from the generated tokens. The pipeline serves regular, PD (--pd-disaggregation), and EPD (--epd-disaggregation) deployments. SMG needs the model's tokenizer (--model-path); see gRPC Workers.

Request field Handling
system, messages Rendered with the chat template. Text and image blocks in user turns, tool_use and thinking blocks in assistant turns, and tool_result blocks are converted. A system-role message inside messages keeps its position; a renderer whose template only takes a leading system prompt renders one sent later as a user turn at its position. Images go through SMG's multimodal pipeline.
max_tokens, temperature, top_p, top_k Sent to the engine as sampling parameters. A max_tokens of 0 never reaches the engine; see max_tokens of 0.
stop_sequences Sent as stop strings to vLLM, TensorRT-LLM, and TokenSpeed gRPC workers. For SGLang gRPC workers and ZMQ workers, SMG matches them itself and sends only single-token stops to the engine, as stop token IDs.
tools Custom tools (those with an input_schema) are passed to the chat template and the tool parser; with a tool_choice of tool, only that tool is passed to the chat template. Other tool types, such as mcp_toolset, bash, text editor, web search, and tool search, are dropped.
tool_choice Mapped to Chat Completions semantics: auto to auto, any to required, tool to that function, none to none. SMG enforces any and tool with constrained decoding.
thinking enabled and adaptive turn on the chat template's thinking mode and run the model's reasoning parser. disabled turns thinking mode off. Without thinking, the template default applies, and an output_config.effort can switch thinking on through the model's provider profile. A display of omitted returns the thinking blocks with their text emptied — the blocks, their signature, and the thinking tokens in usage still arrive; summarized and updates return the reasoning as the engine wrote it. budget_tokens is not sent to the engine.
output_config effort is rendered as the chat template's reasoning_effort. A structured output format under output_config.format or output_format is refused with 400 (unsupported_output_format): the gateway cannot constrain a Messages answer to a format.
metadata, service_tier, container, mcp_servers, extra fields such as context_management Not sent to the engine.

MLX workers answer 400 to a request with images, with stop_sequences, or with a tool_choice of any or tool.

How the response is built:

  • Tool calls and reasoning are extracted by SMG's tool and reasoning parsers, which SMG picks for the model: a worker's per-model parser override is read first, then Symphony's registry under the default --parser symphony, and the --tool-call-parser and --reasoning-parser flags read only the models the registry does not know; see Parser Selection. A thinking block comes first, then text, then tool_use blocks. Thinking blocks carry an empty signature.
  • tool_use ids use Anthropic's toolu_ prefix: a parser id of the form call_<suffix> is returned as toolu_<suffix>, the same in streaming and non-streaming responses. Model-specific id formats are returned unchanged.
  • stop_reason is tool_use when the output has tool calls, stop_sequence when one of stop_sequences ended generation (the matched string is in stop_sequence), max_tokens when the token limit was reached, and end_turn otherwise.
  • usage reports cache_creation_input_tokens and cache_read_input_tokens as 0, never null, with a zeroed cache_creation breakdown, service_tier as standard, and inference_geo as not_available. A turn that ran with thinking adds output_tokens_details.thinking_tokens. In a stream, message_start carries zero counters, and the final message_delta carries output_tokens and, once the engine has reported it, input_tokens.
  • Context window: when the selected worker advertises its context length, SMG rejects a prompt with more tokens than the window with 400 context_length_exceeded before dispatch. In PD mode the smaller of the prefill and decode windows applies. Whether the prompt plus max_tokens must fit is left to the engine.
  • Tenant rate limiting, when enabled, covers this endpoint; see Tenant Rate Limiting.

HTTP and PD Workers

With HTTP workers, SMG forwards /v1/messages to the selected worker. It normally buffers the request, validates it, and re-serializes it: fields SMG does not model are kept, a --model-alias name is replaced by the canonical model ID, and numbers keep the values the client sent. When the HTTP router instead streams the body through (see Request Streaming), it forwards the raw body and leaves validation to the worker. Either way, only the allowlisted headers are forwarded. The worker's successful responses, SSE streams included, are relayed unchanged; a worker's error response keeps its status and message but leaves in the Messages error envelope (see Errors).

With --pd-disaggregation and HTTP workers, /v1/messages uses the same prefill/decode dual dispatch as chat completions: SMG selects a prefill and decode pair and dispatches the request to both. See PD Disaggregation.

On both deployments, a parsed body with max_tokens: 0 is refused with 400 before a worker is selected; see max_tokens of 0.


Anthropic API Backend

Point SMG at the Anthropic API:

smg launch --backend anthropic --worker-urls https://api.anthropic.com

Clients then call SMG as in the Anthropic API example.

  • SMG sends each request to <worker URL>/v1/messages, so the worker URL is the API origin without /v1. The request carries the client's x-api-key, Authorization, anthropic-version, and anthropic-beta headers; when it arrives with neither key header, SMG adds the worker's stored key as x-api-key (see Authentication).
  • Streaming responses are relayed as they arrive. Non-streaming responses are parsed into SMG's Messages schema and re-serialized; a body that does not parse returns 502 with code parse_error.
  • An upstream error is returned with its status and body, minus the organization and project identifiers in the body's error.message (see Provider Error Responses). An error Anthropic answers as an SSE stream is relayed as it arrives.
  • /v1/messages/count_tokens returns 501.

MCP Tools

SMG can run MCP tools for Messages requests on the Anthropic API backend. gRPC workers drop mcp_toolset tools, and HTTP workers receive them in the request body.

SMG runs the tool loop itself when the request has the X-SMG-MCP: enabled header and tools contains at least one mcp_toolset entry. Without the header, mcp_servers and the mcp_toolset entries are forwarded to Anthropic, together with the client's anthropic-beta header, and Anthropic's MCP connector runs the tools.

curl http://localhost:30000/v1/messages \
  -H "Content-Type: application/json" \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "X-SMG-MCP: enabled" \
  -d '{
    "model": "claude-sonnet-4-20250514",
    "max_tokens": 1024,
    "messages": [
      {"role": "user", "content": "Search the web for SMG and summarize the top result."}
    ],
    "mcp_servers": [
      {"type": "url", "name": "search", "url": "https://mcp.example.com/mcp"}
    ],
    "tools": [
      {"type": "mcp_toolset", "mcp_server_name": "search"}
    ]
  }'
Field Description
mcp_servers[].name Server name that mcp_toolset entries refer to.
mcp_servers[].url http:// or https:// URL. SMG connects over Streamable HTTP. A URL containing /sse selects the legacy SSE transport, which SMG can no longer connect to.
mcp_servers[].authorization_token Sent to the MCP server as Authorization: Bearer <token>.
mcp_toolset.mcp_server_name The server whose tools the model may call.
mcp_toolset.default_config.enabled Whether the server's tools are enabled (default true).
mcp_toolset.configs Per-tool settings keyed by tool name. When present, only the tools listed here are exposed, each if its enabled is true (or unset, falling back to default_config.enabled).
defer_loading in default_config or configs Copied onto the tools SMG passes to the model.

What SMG does:

  1. Connects to the servers in mcp_servers. If none connects, it returns 502 with code mcp_connection_failed.
  2. Replaces mcp_servers and the mcp_toolset entries with the enabled MCP tools as regular tools, and sets tool_choice to auto if the request had none.
  3. Runs each tool the model calls, sends the results back to the model, and repeats until the model stops calling tools, for at most 10 rounds of tool calls. If the model still calls tools after the 10th round, a non-streaming request fails with 502 (mcp_max_iterations). A stream ends with an error event right after the 10th round, without calling the model again.
  4. Returns each call as an mcp_tool_use block (id prefixed mcptoolu_) followed by its mcp_tool_result block, then the model's final content:
{
  "content": [
    {
      "type": "mcp_tool_use",
      "id": "mcptoolu_01AbCdEf",
      "name": "web_search",
      "server_name": "search",
      "input": {"query": "SMG"}
    },
    {
      "type": "mcp_tool_result",
      "tool_use_id": "mcptoolu_01AbCdEf",
      "content": [{"type": "text", "text": "..."}],
      "is_error": null
    },
    {"type": "text", "text": "The top result describes..."}
  ],
  "stop_reason": "end_turn"
}

In a stream, SMG forwards the upstream events, emits the model's tool calls as mcp_tool_use blocks and each result as an mcp_tool_result block, and ends with a single message_delta and message_stop. SMG does not accept mcp_tool_use or mcp_tool_result blocks in messages (see the accepted block types under Request Body).

Tool calls use policy-only approval: SMG never pauses the request to ask the client. Each call is checked against the policy rules of the MCP configuration file; without such rules, the default policy allows every tool. See MCP for server configuration.


Errors

Every error answered on /v1/messages and /v1/messages/count_tokens leaves in Anthropic's error envelope — the shape the Anthropic SDKs decode — whatever produced it inside: body parsing and validation, authentication, admission, the gRPC pipeline, the MCP tool loop, or a worker's error response:

{
  "type": "error",
  "error": {
    "type": "invalid_request_error",
    "message": "This model's maximum context length is 32768 tokens. However, your request has 40210 input tokens. Please reduce the length of the input."
  },
  "request_id": "..."
}
  • error.type follows the status: invalid_request_error for a 400 (and any other 4xx not named here), authentication_error (401), permission_error (403), not_found_error (404), request_too_large (413), rate_limit_error (429), overloaded_error (503 and 529), timeout_error (504), and api_error for another 5xx.
  • error.message keeps the inner error's message: for an HTTP or PD worker, the message of the upstream body under the upstream status; for the Anthropic API, the same minus the organization and project identifiers (see Anthropic API Backend); SMG's own words otherwise. An upstream body already in the envelope keeps its error and gains the request_id it lacks.
  • request_id is the id echoed in the x-request-id response header.
  • The machine-readable codes this page names in parentheses, such as context_length_exceeded or model_not_found, travel in the X-SMG-Error-Code response header; the body does not carry a code. A refusal of the request body itself names the broken rule in error.message alone. Headers such as Retry-After and WWW-Authenticate stay.

The envelope also covers a request over the gateway's payload limit (413) and, when the request carries the anthropic-version header the Anthropic SDKs send, a model lookup under /v1/models and a request to an unknown URL.

Errors that SMG detects before the stream starts are returned as ordinary HTTP error responses, not as a stream, even when stream is true. After the stream has started, the gRPC path and SMG's MCP tool loop report a failure as an Anthropic error event and end the stream. The MCP tool loop starts its stream before it first calls the model, so even an upstream error on that first call arrives this way:

event: error
data: {"type":"error","error":{"type":"api_error","message":"..."}}

HTTP workers and the Anthropic API stream their own error events, which SMG relays.