Understand routes, prices and available balance
Read public prices as a catalogue, confirm account-specific access, and separate a temporary reservation from a settled charge.
Technical review:
A route name is not an access grant
MaxAPI documents official, official-cheap, mix, pro, x and a routing tiers, but a given model does not necessarily expose all six. Access also depends on the account and API key. In particular, restricted tiers require permission; choosing one in a request does not unlock it. Check the model API documentation and the account’s enabled routes before integrating, rather than copying another model’s route list.
Check API-key routing before request routing
A route pinned to the API key takes precedence over a request-level selection. When the key is not pinned, an explicit supported request route is considered before the model default. JSON image requests use route_mode; Gemini-native requests use X-MaxAPI-Route-Mode. This is why changing the request field alone may not change the effective tier. Do not assume that an unavailable selected tier silently falls back to every other price tier.
Compare like-for-like billing units
Public pricing and pricing.json are catalogue snapshots, not a live quote for your account. Use the current pricing page while signed in to inspect available routes and account-specific prices. A per-image price, per-call price and token-based image price are not interchangeable. Resolution, quality and the applicable pricing rule can matter. One credit corresponds to one USD in MaxAPI’s published accounting convention; reconcile actual consumption using your billing records rather than the lowest number shown on a model card.
Available balance is not the whole wallet state
GET /v1/account/balance reports the account wallet shared by its keys. In-flight tasks may reserve credit, so available credit can decrease before a final charge is settled. A request timeout does not tell you whether a reservation exists or whether the job succeeded. Use the task’s final state and billing history; GET /v1/account/billing/usage is scoped to the calling API key. Key budgets and model permissions can still prevent a request even if the account has funds. Do not interpret an estimated task charge as the final settled amount.
GET https://api.maxapi.dev/v1/account/balance
Authorization: Bearer $MAXAPI_KEY
GET https://api.maxapi.dev/v1/account/billing/usage
Authorization: Bearer $MAXAPI_KEYModel-specific parameters
Public configuration snapshot; not live availability. Follow each model page for its parameters, supported routes and reference limits.
- Gemini 3.1 Flash Lite Image
google/gemini-3.1-flash-lite-image - Gemini 3.1 Flash Image Preview
google/gemini-3.1-flash-image-preview - Nanobanana Pro
google/gemini-3-pro-image-preview - GPT Image 2
openai/gpt-image-2