MiniMax API vs Beam 1.0

MiniMax API

M3.1 Flash costs $0.15 in and $0.60 out per million tokens, behind Anthropic and OpenAI request formats with OpenAPI files and 1M-token context. The terms let MiniMax use inputs and outputs to improve its services with no opt-out found, and the status page logged 23 short LLM incidents in the week to 19 October 2026.

Beam 1.0

The Reflection API is OpenAI-compatible, with an OpenAPI document, strict structured outputs and tool calls, and error codes that say when to retry, and the weights are Apache-2.0. It is a free public beta with unpublished daily limits and no per-token price, reasoning can't be turned off, and three API incidents were posted between 14 and 16 October 2026.

MiniMax API

1. Use the Anthropic-format base URL https://api.minimax.io/anthropic for tool calls. The OpenAI-format schema has no tool_choice or response_format
2. Set output_config.effort (or reasoning_effort) below max for routine calls. M3.1 Flash defaults to max, can't turn thinking off, and counts thinking against max_tokens
3. Don't rely on stop_sequences or top_k. The Anthropic-format endpoint ignores them
4. Back off on 429 and 529 yourself. No Retry-After header is documented
5. Use a pay-as-you-go key for production. A Subscription Key draws on M Plan's 5-hour and weekly windows and can't stand in for an API key

Beam 1.0

1. Send reasoning_effort low or medium for short tasks. The default is max, and none or minimal return 400 unsupported_value
2. Return every assistant message with its reasoning_content unchanged. If a turn comes back without it, start a new conversation, since later requests fail with missing_required_parameter
3. Don't rely on stop or seed. Both are accepted and ignored, so truncate output in your own code
4. Honour x-should-retry: false on a 429. It means a daily limit is spent and Retry-After counts to 00:00 UTC
5. Set max_completion_tokens yourself on long prompts. The default budget isn't reduced to fit the prompt and includes reasoning tokens