Messages
Anthropic Messages API — required by Claude Code.
Create a message (Anthropic Messages API)
Anthropic-compatible Messages API. Required by Claude Code
(ANTHROPIC_BASE_URL points here). The gateway accepts Anthropic-format
requests and translates to the upstream provider.
Headers
anthropic-versionAccepted for compatibility with Anthropic-format clients. The gateway handles the upstream translation; the header does not change routing.
Create a message (Anthropic Messages API) › Request Body
modelA model ID from the current catalog — real provider model names, all MiniMax. The core tiers are minimax-m3 (flagship), minimax-m2.7 (balanced daily driver) and minimax-m2.5 (fast); the -highspeed variants are latency-tuned versions of their standard siblings at roughly 2x the price; minimax-m2.1 and minimax-m2 are older M-series generations; minimax-m2-her is role-play/dialogue chat tuning; minimax-text-01 is the long-context text model. There are no invented aliases; any other ID returns an error. The catalog can change with notice.
max_tokensMaximum number of tokens to generate. Required by the Anthropic Messages format.
Alternating user / assistant turns, oldest first.
systemOptional system prompt — a top-level field here, not a message role.
temperatureSampling temperature, 0–1 in the Anthropic format. Lower is more deterministic.
streamSet true for a Server-Sent Events stream of message events.
stop_sequencesCustom sequences that stop generation.
Create a message (Anthropic Messages API) › Responses
An Anthropic-format message.
idtyperolemodelThe model that actually served the request. During a provider incident this may be a smaller model of the same family as the one you requested.
Content blocks — for text generation, one text block.
stop_reasonend_turn, max_tokens, or stop_sequence.
stop_sequenceWhich stop_sequences entry matched, if any.