Guide updated
Updated 2026-10-19. A user reconciled PAYG available_amount with the USD effective balance in the international console. This is not independent verification of all API units, component meanings, key permissions or subscription behavior; these remain pending. No supplier login or paid call was performed.
- Required credentials
- PAYG API key / plan Subscription Key
- Monitoring unit
- PAYG: USD display from console reconciliation; component units unverified; plan: base % and separate weekly multiplier
- What is monitored
- PAYG effective balance / shared plan windows
- PAYG uses only fixed GET https://api.minimax.io/account/query_balance; subscription uses only fixed GET https://www.minimax.io/v1/token_plan/remains. Both use Bearer authentication without body, cache, redirects or fallback. PAYG retains available_amount, cash_balance, voucher_balance, credit_balance and owed_amount as exact decimal strings: minimaxPayg.unit=unverified and currency=null. Plan minimaxQuota.groups keeps base percentages and separate weekly_boost_permille (1500‰=1.5×). Money, scalar percentageRemaining, providerAvailable and runwayDays stay null in both modes; XXX means no confirmed currency.
Use the official console without hosting a key
- Use the same international account: Billing > Balance for PAYG; Billing > M Plan and Usage for subscription.
- The documented older Balance link may redirect to Recharge records. Use the console's Balance menu; do not guess endpoints or units from a redirect.
- Compare the PAYG main value with the same team’s USD Effective balance; open the info icon for original components and confirm their units and signs separately. For plans, compare base percentages, boosts and windows; inspect Credit packs separately.
- Keep unknowns unknown and consult official support; no top-up, model call or permission change is required.
Connect MiniMax · international to Quota Monitor
Confirm the international account and desired mode
Use your existing account on platform.minimax.io. Choose PAYG for ordinary metered API usage or Subscription for an existing M Plan / Token Plan. These are two options inside one MiniMax provider, not separate providers.
Plan Details below identifies existing subscription resources and its Subscription Key. Do not purchase, upgrade or change renewal for monitoring. China-site credentials are separate.
Obtain the key for your chosen mode
PAYG: open the official API Keys entry below and use Create new secret key under your existing access; privately save the complete sk-api- secret. Subscription: use Billing > M Plan / Plan Details to find the Subscription Key.
Copy only the secret, not its ID, Bearer header, OAuth session or Cookie. Actual signed-in controls and privileges await user verification. If existing access is unavailable, use manual checks or official support instead of elevating roles.
Review credential exposure
Neither credential has a documented quota-only permission template. Both can authorize paid model activity even though this monitor sends only GET requests. No invented read-only policy is provided.
Use only credentials whose hosting risk you accept. A separate monitoring key is preferable where already supported. Do not disable IP protection, revoke application keys or expand privileges to pass a test.
Select PAYG or Subscription inside MiniMax
Open your Quota Monitor project, add a connection, select MiniMax International, then choose PAYG or Subscription. Secure credential links expose the same choice. Give the connection a recognizable name; never send secrets in chat.
Existing connections remain subscriptions; they are not switched automatically. No project/key ID, region, currency or monetary budget is required. A Quota Monitor project organizes monitoring, not upstream account funds.
Save the matching secret in the masked field
The PAYG field accepts a standard sk-api- key; the subscription field accepts a Subscription Key. Switching mode clears an unsaved key, so enter the matching secret again before saving. Mismatched formats are rejected before transport.
Secrets are encrypted; other views show only the last four characters. The help drawer does not read or submit input. Never include secrets in screenshots, logs or tickets. Saved mode is fixed; credential rotation cannot change it.
Verify a fresh successful snapshot
PAYG shows Effective balance · USD using the same dollar format as other cards: available_amount="12.3400" displays $12.3400, without rounding or division by 100. Open the info icon beside the label for cash_balance, voucher_balance, credit_balance, owed_amount and verification limits. Missing or non-string data fails rather than becoming zero.
Subscription shows each group's base remaining percentage, weekly multiplier and UTC windows. Base 80% and weekly_boost_permille=1500 stay separate, not tokens or cash. Missing percentages stay unknown; usage_count is never used to infer them.
Reconcile in the same official account
For PAYG, open Billing > Balance in the same team and compare Effective balance with the main card value. A user confirmed a one-to-one USD match, not a universal API unit contract. The documented Balance link may redirect to Recharge records; select Balance in the console menu if needed. Confirm each component separately with MiniMax; do not infer its currency from the main amount.
For subscription, open Usage below and compare base percentage, boost and independent reset dates. The console may show their product rather than the base field. Video has no 5-hour window; legacy Token Plan follows the actual response.
Troubleshoot without changing old connections
For 401/403, verify site, mode, complete secret, expiry/revocation and existing access. Wait before retrying 429. We do not try another endpoint or China, buy resources or elevate permissions. Failed sync keeps the old successful snapshot/time.
Rotate only to a key of the same mode. To monitor PAYG while retaining an old subscription connection, add PAYG through the same MiniMax entry; you decide whether to remove the old one. The reported effective-balance match does not verify other accounts, components, key permissions or subscription behavior.
What Quota Monitor reads from MiniMax · international
- PAYG fields belong to the authenticated account. The effective balance uses a user-reconciled USD display convention; the public response still does not define currency, scale or component relationships. Components remain raw in the info popup. No derived net balance, total-balance inclusion or monetary alerts. Multiple keys/projects may share an account.
- Plan groups, tools and keys can share overlapping allowance: never sum them. International and China sites remain separate; no region probing, reseller gateway, Cookie or private endpoint.
- Modern M Plan has independent first-use 5-hour and 7-day windows for non-video resources; video is weekly-only. Legacy Token Plan can retain unlimited or 150% benefits. Only returned epoch-millisecond dates are shown; zero or absent dates stay unknown.
- Plan baseRemainingPercent uses only *_remaining_percent, not ambiguous *_usage_count. Weekly boost remains separate. Both zero totals and both statuses=3 means not in plan, not unlimited. Credit packs and rate limits are separate and allowance does not guarantee model access.
- Existing connections without a mode remain subscriptions, with credentials and snapshots preserved. Mode is fixed after creation; rotation only accepts the same key type. Changing mode in a new form clears its unsaved key. Failed reads preserve the last successful snapshot/time, without trying the other mode.
- PAYG cards show the effective balance in USD using a user-reconciled console display convention; the info popup contains raw components and verification limits. REST/MCP retain unverified raw units. Failed refreshes preserve old values and time; neither mode contributes to total balance or monetary alerts.
MiniMax · international FAQ and troubleshooting
- Why is my ordinary API key still rejected?
- Select PAYG. Standard sk-api- and Subscription Keys are not interchangeable. Old connections default to subscription, and rotation cannot change their mode. Add the appropriate mode through the same MiniMax provider without rewriting old connections.
- Why does PAYG show USD but stay outside total balance?
- USD is a display convention based on a user-reconciled effective balance, not a claim that all raw API fields have documented currency or scale. The four components and explanation are behind the info icon. REST/MCP keep unit=unverified and currency=null; total balance, monetary alerts and runway calculations still exclude PAYG values.
- What do unknown, 150% and unlimited plan values mean?
- Missing *_remaining_percent remains unknown, not inferred from usage_count. Legacy Token Plan can retain historical benefits; base percentage and weekly_boost_permille are separate. Both zero totals and both statuses=3 means not in plan, not unlimited.
- Why can calls fail with allowance, or work after exhaustion?
- RPM/TPM and model permissions are independent, and eligible Credit packs can cover overflow. Subscription mode does not read purchased-pack balance. Raw PAYG values are not plan allowance or a guarantee of model access.
- Why is reset different from the monthly invoice?
- Modern M Plan starts independent 5-hour and 7-day windows on first use. We show only returned epoch-millisecond dates. PAYG has no confirmed reset field, so no reset date is invented.
- Will this log in, switch mode or change billing?
- No. Only the selected mode's fixed international GET endpoint is read, without model calls, login, Cookies, payments, key management, permission writes or credential-bearing redirects. Errors preserve old snapshots; real-account acceptance remains with the user.
Official MiniMax · international references
- Official reference · platform.minimax.io/docs/m-plan/faq(opens in a new tab)
- Official reference · platform.minimax.io/docs/m-plan/usage-rules(opens in a new tab)
- Official reference · platform.minimax.io/docs/m-plan/token-plan-notice(opens in a new tab)
- Official reference · github.com/MiniMax-AI/cli/blob/v1.0.28/src/types/api.ts(opens in a new tab)
- Official reference · github.com/MiniMax-AI/cli/blob/v1.0.28/src/output/quota-table.ts(opens in a new tab)
- Official reference · github.com/MiniMax-AI/cli/blob/v1.0.28/src/utils/quota.ts(opens in a new tab)
- Official reference · platform.minimax.io/docs/guides/quickstart-preparation(opens in a new tab)
- Official reference · github.com/MiniMax-AI/cli/blob/v1.0.28/src/client/endpoints.ts(opens in a new tab)
- Official reference · github.com/MiniMax-AI/cli/blob/v1.0.28/src/output/balance.ts(opens in a new tab)
Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.