Skip to main content

Model Request Ratios (Legacy)

Legacy plans only: This page applies to existing subscribers on retired request-count plans (Promo, Lite, Pro, Pro+, Max, and Max+), which remain active until the end of their current billing period. New subscriptions use the Minion ($20/month) and **Boss** ($80/month) plans — see Model Costs & Usage Estimates, Minion, and Boss.

Legacy plan limits at a glance

Not every model costs the same slice of a legacy request-count plan. Each model has a ratio — how much of your allowance one call to it uses. Auto and flash models are the 1.0 floor. GLM-5.2 costs 2.0 — one call uses two requests’ worth. Your plan’s “requests per window” number is what that buys on Auto and other 1.0 models; GLM-5.2 calls consume twice as much. On Promo (30 per 5-hour window) that is 30 Auto calls or 15 GLM-5.2 calls; a very long DeepSeek-V4.1-Flash or GLM-5.3-Flash prompt costs 3.0 (down to 10 on Promo).
Note: mid-tier models sit between 1.0 and 2.0; premium chat models cost more — see the table below. Long-context surcharges on included models are separate — see Long-context surcharge. Image models use a fixed ratio per image — see Image generation ratios.
Promo plan ($1/mo, retired; existing subscribers only): Includes a 2-day trial on all models. After trial, Qwen3.8 27b and Llama 3.2 3B receive a special 0.1 request ratio (delivering 300 requests every 5 hours), and GPT-OSS-120B costs 0.5 (60 requests every 5 hours).

Ratios at a glance

Peak hours (06:00–10:00 UTC): GLM-5.3 costs more of your allowance — see Peak-hour ratios.
Use the model name exactly as shown as the model value in your request. Tables below list models on subscription plans (Promo through Max+). On-demand-only models (for example GLM-5.2) are billed per token and are not shown here. Models included only on Minion and Boss (for example DeepSeek-V4-Pro-0813, Kimi K3) are billed per token on these plans and are not shown here either.
Legacy Auto Agent plans: Existing subscribers on Auto Agent Mini, Lite, Pro, or Max keep their grandfathered allowance at the same ratios until they choose to switch plans.

How many requests you get

Per 5-hour window

Per week

Weekly caps reset Monday 00:00 UTC.

Peak-hour ratios

Some models cost more of a legacy request-count allowance during peak hours: every day from 06:00–10:00 UTC (14:00–18:00 UTC+8). Outside that window the standard ratios apply. The ratio is set when a request is received: a call received before the end of the window is charged the peak ratio even if it finishes later. It applies to your window and weekly allowances alike. Plans metered by tokens (Minion and Boss) have no ratios and are not affected.

Per 5-hour window at peak ratios

Per week at peak ratios

Image generation ratios

Each successful image counts as one call. Ratios apply per image, not per token. You do not have to spend a window on one model — costs simply add up. On Pro, 600 GLM-5.2 calls (1,200) plus 400 Auto calls (400) is 1,600 requests’ worth.

Long-context surcharge

GLM-5.3 requests whose prompt exceeds 262,144 tokens cost 20.0 instead of 10.0. DeepSeek-V4.1-Flash and GLM-5.3-Flash requests whose prompt exceeds 262,144 tokens cost 3.0 instead of 2.0. DeepSeek-V4-Flash-0731 uses 2.5 above the same threshold instead of 1.7. During peak hours (06:00–10:00 UTC) the ratios scale as described in Peak-hour ratios: GLM-5.3 costs 20.0 (40.0 above 262,144 tokens).
  • The surcharge is measured on input only. A long reply to a short prompt still costs the base ratio.
  • The threshold is measured on upstream-reported input tokens after the call completes. X-Quota-Cost on the response uses a pre-flight estimate and may read lower until settlement; the dashboard is always exact.
If you routinely work above 262k tokens, MiniMax M3 has a larger context window and carries no long-context surcharge on plan quota.

Reading the cost at runtime

You never have to hardcode this table. GET /v1/models reports the ratio on every model:
quota_context_surcharge is present only on models whose cost scales with prompt size. Models that cost more during peak hours also report quota_multiplier_peak and quota_peak_window_utc:
quota_multiplier is the standard ratio. quota_multiplier_peak applies every day from start_hour (inclusive) to end_hour (exclusive), UTC, on request-count plans. Both fields are present only on models with peak pricing. Every response also carries what that specific call used:
Note: X-Quota-Remaining is read when the request is admitted, so with several requests in flight at once it can read slightly high. The dashboard under Billing is always exact.

What still counts as one request

The ratio changes how much a call costs, not which calls count:
  • success and client_error (4xx) count.
  • Upstream provider errors and capacity-unavailable situations do not count — a failed request is refunded in full, at whatever it would have cost.
  • The per-minute burst limit is unaffected. It is a hard cap on calls per minute and is never extended by credits.