# MiniMax (/docs/providers/minimax)

The MiniMax account answers with the visitor's MiniMax account. The wallet lists it as MiniMax under "With your plan", with the id `minimax`.

## What the visitor needs [#what-the-visitor-needs]

A MiniMax account with a plan. The wallet shows the account as paid from the plan.

## Sign in [#sign-in]

1. In the wallet, the visitor picks MiniMax under "With your plan".
2. The wallet asks MiniMax for a user code at `https://api.minimax.io/oauth/code`, bound to a PKCE challenge, and shows the code in the side panel.
3. It opens a window on the verification page MiniMax returns.
4. The visitor signs in and approves the code.
5. The wallet asks `https://api.minimax.io/oauth/token` each time a page finishes loading in the window, when the window closes, and when the visitor presses "I approved it". MiniMax reports the sign in as pending until the visitor approves, and an error status ends it.
6. MiniMax returns the tokens, and the account is connected.

The code lasts until the expiry MiniMax gives, and at least one minute. The wallet renews the access token with the refresh token from one minute before it expires.

## Models [#models]

The wallet has no model list for MiniMax. The account answers with `MiniMax-M3`, and the side panel shows no model buttons for its sites.

## Usage and limits [#usage-and-limits]

The wallet reads no usage header specific to MiniMax. It reads `x-ratelimit-remaining-tokens` and `x-ratelimit-limit-tokens` on any answer that carries them, as it does for every account. Without them, the card keeps saying "Usage shows after the first answer", and Auto ranks the account among the accounts with no reading.

## Calls [#calls]

Answers come from `https://api.minimax.io/anthropic/v1/messages` in Anthropic's Messages protocol, which MiniMax answers from the browser. That protocol requires an output limit on every call, and the wallet asks for 4096 tokens when your site sets no `maxTokens`. All four request options reach MiniMax.