Anthropic messages

POST /v1/messages accepts Anthropic message format. messages must be non-empty and max_tokens must be a positive number.

curl https://api.strixgate.dev/v1/messages \
  -H "x-api-key: $STRIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "strix-coding",
    "max_tokens": 512,
    "system": "Be concise.",
    "messages": [{"role": "user", "content": "Review this function."}]
  }'

Strix converts the request into its shared completion pipeline so authentication, routing, and caching behavior are aligned with chat completions. String or text-block system prompts, text messages, tool definitions, tool choice, stop sequences, temperature, and streaming are supported by the adapter.

Non-streaming responses use an Anthropic-style message envelope. Streaming responses are translated into Anthropic SSE events without buffering the whole upstream response.

POST /v1/messages accepts Anthropic message format. messages must be non-empty and max_tokens must be a positive number.

curl https://api.strixgate.dev/v1/messages \
  -H "x-api-key: $STRIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "strix-coding",
    "max_tokens": 512,
    "system": "Be concise.",
    "messages": [{"role": "user", "content": "Review this function."}]
  }'

Non-streaming responses use an Anthropic-style message envelope. Streaming responses are translated into Anthropic SSE events without buffering the whole upstream response.