How coding plans count usage: credits, requests, dollars, and windows

A coding plan's price is comparable; its allowance is not. What one unit counts at each vendor, which window refills it, and what the pages leave unsettled.

By Standard Thinking · Updated

A coding subscription publishes a monthly price and an allowance that refills. Across six vendors read on September 29, 2026, each in its own currency, that allowance turned out to be six things: a credit from a published token formula, a model call rather than a user turn, a dollar of list-price consumption, a percentage of a shared pool, an undisclosed bar in a console, and a multiple of another plan's session. The unit, not the price, decides how much work you get.

What one unit counts

Plan Price Unit Formula public Signup
Z.ai GLM Coding Plan — Lite/Pro/Max $18/$80/$168 Credits Yes Open
Moonshot Kimi Code — Plus/Pro/Max/Ultra $19/$39/$99/$199 Shared pool % No Open
Moonshot Kimi Code, legacy — CNY Andante/Moderato/Allegretto/Allegro ¥49/¥99/¥199/¥699 Shared pool % No Existing members
MiniMax Token Plan — Plus/Max/Ultra $22/$55/$132 Usage bar No Open
Alibaba Coding Plan — Pro ¥200 Model calls Partial Rationed, Lite closed
Alibaba Token Plan, Personal — Lite/Essential/Standard/Pro ¥60/¥120/¥180/¥600 Credits No Open
OpenCode Go — Go/Go Plus $10/$40 List-price dollars Partial Open
DeepSeek Pay per token Tokens Per-token rates Open
Anthropic Claude Pro/Max — reference grammar $20/$100/$200 Relative multiple No Open
Standard Thinking Coding Plan $50/$100/$200 Before activation Before activation Open

When the allowance comes back

Plan 5-hour Weekly Monthly Reset
Z.ai GLM Coding Plan 2,000/12,000/28,000 10,000/60,000/140,000 Not stated Rolling + fixed
Moonshot Kimi Code Named, no figure Removed Shared pool, then frozen Rolling
Moonshot Kimi Code, legacy Named, no figure Named, no figure Shared pool, then frozen Rolling + fixed
MiniMax Token Plan Named, no figure Named, no figure No carryover 5-hour rolling
Alibaba Coding Plan 6,000 requests 45,000 requests 90,000 requests Rolling + fixed
Alibaba Token Plan, Personal Not stated Removed 11,500/25,500/45,000/180,000 Fixed
OpenCode Go 20% of monthly 50% of monthly Per-model dollar limits Not stated
DeepSeek No window No window No window None
Anthropic Claude Pro/Max Named, no figure Named, no figure Not stated Rolling + fixed
Standard Thinking Coding Plan $50 tier only $50 and $100 tiers $200 has no total cap Before activation

Notes by plan

  • Z.ai. A credit is input, cached input and output tokens times per-model multipliers over 10,000 — for GLM-5.3, 6.9, 1.7 and 24. Off-peak costs half the credit rate; peak is weekdays, 14:00–18:00 Singapore time, and from September 25 to October 7, 2026 every hour is charged at the off-peak rate.
  • Kimi Code. The plans released in September keep the USD prices under new names, Moderato to Vivace becoming Plus to Ultra, sold with a subscribe button, labeled 2×, 5× and 10× Agent credits and billed $180, $372, $948 and $1,908 a year. New members have no weekly quota, only the rolling 5-hour window; the 1M-context model consumes about twice the quota of the 256K one.
  • Kimi Code, legacy. Membership features share one credit pool calculated on actual token consumption; unused quota does not roll over, and no peak policy appears. Sizing is about 30, 60, 150 and 360 Agent uses, and existing members keep a 7-day quota beside the 5-hour window.
  • MiniMax. The monthly quota shows as "a usage bar in the console" and deducts at endpoint pricing; tiers are sized as 3-4, 4-5 and 6-7 agents. No peak policy is published.
  • Alibaba Coding Plan. Quota counts model calls, not user turns: simple tasks typically use 5–10 calls, complex ones 10–30 or more. When platform load is high, or one account's use is unusually concentrated, Alibaba may queue, throttle or briefly interrupt that account's requests; slots restock daily at 09:30 Beijing time.
  • Alibaba Token Plan. A Credit is the shared billing unit across text, image, speech and video, at limited-time rates of ¥39, ¥79, ¥139 and ¥499. The weekly quota was removed on September 22, 2026 for a monthly one on a 30-day cycle from the subscription date; unused Credits expire, concurrency is listed as 1–2 to 6–8 agents, and no peak policy appears.
  • OpenCode Go. The budget is a monthly dollar limit per model rather than one pool: Kimi K3 $15, GLM-5.3 $15 and GLM-5.3-Flash $60 on Go, and $60, $120 and $180 on Go Plus. DeepSeek peak rates pass through at double the off-peak rate on DeepSeek's weekday hours, with no mention of its holiday exemption, and the limits may change with early usage.
  • DeepSeek. The expense is tokens times price, deducted from a topped-up or granted balance, at rates published per model and window. Off-peak rates are half peak, peak being 01:00–04:00 and 06:00–10:00 UTC, Monday through Friday, excluding Chinese public holidays.
  • Claude Pro / Max. No absolute unit is published; what a session allows varies with message and attachment length, conversation length, and the model or feature used. Peak is priority access for Pro "during high-traffic periods", with a reserved clause allowing other limits at Anthropic's discretion.
  • Standard Thinking. "Peak-time restrictions apply to every plan, including $200": requests may slow, queue or time out, and priority runs $200 → $100 → $50. Tiers are priced per developer; the allowance unit, its amounts and its reset rule are confirmed before activation.

One of six publishes the arithmetic

One vendor of the six publishes arithmetic a reader can run before subscribing: Z.ai's multipliers price an output token at a little over fourteen times a cached input token on GLM-5.3, and that ratio decides how long an allowance survives an agent loop. Three of the six publish no number at all — a percentage of a shared pool, a bar in a console, "five times the Pro plan's per-session usage allowance" — and five were open to new subscribers that day.

Rolling windows forgive, fixed windows schedule

A rolling window gives back what you spent five hours ago, whatever your subscription date. A fixed window is a calendar entry: Alibaba's weekly cap turns over Monday 00:00 in Beijing, Z.ai's and Moonshot's legacy one on the subscription anniversary, Anthropic's at an hour assigned to the account. In September Moonshot's new plans and Alibaba's Token Plan dropped their weekly windows, the Token Plan for a 30-day cycle from the subscription date. Alibaba's three limits apply at once, whichever is reached first taking effect, and they "are not cumulative and do not represent a guaranteed capacity distributed evenly over time".

What the source pages leave unsettled

Moonshot's help centre still says Kimi Code has "a separate limit of 5 hours per week", which reads as five clock-hours; its developer documentation describes a rolling 5-hour rate window, a rate limit rather than a time budget, plus a 7-day quota that only legacy plans keep, and the windows table follows the documentation. The legacy CNY lineup and the renamed USD one differ in tiers as well as currency, which is why both rows appear. Concurrency is nearly invisible: Z.ai publishes a principle without a number, Alibaba's Coding Plan withholds its thresholds while its Token Plan lists 1–2 to 6–8 concurrent agents, MiniMax publishes per-model rates, OpenCode none, while DeepSeek, selling no subscription, prints figures.

Reading your own usage against these units

  1. Model calls, not prompts. Count sub-agent and parallel calls apart from the main conversation; it is what Alibaba's unit charges.
  2. Input, cached and output tokens. Credit formulas and dollar budgets price the three differently; the token and workload estimator gives per-run counts.
  3. Work falling in peak hours. This moves the price at Z.ai and on DeepSeek usage, and the wait at Alibaba.

Coding Plan is available now: log in to subscribe, or ask about your coding workflow first; our allowance unit, amounts and reset rule are confirmed before activation. Flat-price APIs swap these windows for other ceilings — see what flat-rate LLM API limits actually are; both vocabularies are defined in capacity and plan terms.

Sources and verification

Sources used for this resource. Verification dates describe our source checks, not provider effective dates.

Z.ai GLM Coding Plan documentation, Overview

The credit unit and every window figure in the Z.ai rows. Verbatim: "Model credit usage = (Input tokens × Input multiplier + Cached Input tokens × Cached Input multiplier + Output tokens × Output multiplier) / 10,000"; the multiplier table (GLM-5.3 input 6.9, cached input 1.7, output 24; GLM-5.3-Flash 2.3, 0.56, 8), which is where the fourteen-times ratio between an output token and a cached input token is read; "Each plan is subject to both a 5-hour usage limit and a weekly usage limit" with Lite 2,000 / 10,000, Pro 12,000 / 60,000 and Max 28,000 / 140,000 credits; "5-hour credits: Dynamically refreshed; credit quota resets 5 hours after consumption"; "Weekly credits: Activated upon subscription; resets every 7 days"; and "During off-peak hours, model usage is charged at 50% of the standard credit rate. Peak hours: Monday to Friday, 14:00–18:00 Singapore Standard Time (UTC+8)." On 2026-09-29 the page also read "From September 25 to October 7, 2026, all-day usage will be charged at the off-peak rate", which the Z.ai note quotes with its dates.

Checked

Z.ai GLM Coding Plan pricing

The monthly prices in the Z.ai row — Lite $18, Pro $80, Max $168 — read in a browser because the page is JavaScript-rendered; on 2026-09-29 it opened on yearly billing at 30% off, showing $12.6, $56 and $117.6 a month beside those monthly prices. Subscribe controls were live on both reads, which is the basis for recording the plan as open to new subscribers. The same page carries the concurrency FAQ answer that rate limits are tied to the plan tier "with the general principle being Max > Pro > Lite", with no numeric figure anywhere.

Checked

Kimi Help Center, membership billing and plans

The CNY lineup row: Andante ¥49, Moderato ¥99, Allegretto ¥199 and Allegro ¥699 per month, with sizing of about 30, 60, 150 and 360 Agent uses. The unit wording is verbatim: "All Kimi membership features share one credit pool and are calculated based on actual token consumption"; "You can view your current credit balance as a percentage"; and the shared-pool consequence that if one feature uses up the credits, other features are affected. This page also carries the ambiguous sentence quoted in the unsettled section: "Kimi Code also has a separate limit of 5 hours per week, which applies only to Kimi Code and does not affect other membership features." No signup-availability statement appears on it, which is what that cell records. The page read the same on 2026-09-29, while Kimi's developer documentation now calls this lineup the legacy plans that existing members keep, which is what the signup cell records.

Checked

Kimi membership pricing, plans released in September

The row for the plans released in September, read in a browser on 2026-09-29: Plus $19, Pro $39, Max $99 and Ultra $199 per month, with annual totals of $180, $372, $948 and $1,908, and relative allowance labels rather than numbers ("2 倍", "5 倍", "10 倍 Agent 额度"). Every tier's call to action reads "订阅" (subscribe) under a banner that the new membership plans are now available, which is the basis for the open cell. On 2026-09-12 the same prices carried the names Moderato, Allegretto, Allegro and Vivace and a "预约订阅" (reserve a subscription) button.

Checked

Kimi Code documentation, membership benefits

The windows rows for Kimi Code and the developer-documentation half of the contradiction. Verbatim on 2026-09-29: "The new Kimi membership plans are now available, with pricing unchanged"; "For new members, the weekly quota limit is removed, and only the rolling 5-hour rate window remains"; "Existing subscribers on legacy plans are not affected: the tier name, quota rules, and auto-renewal all remain as they are"; and the 5-hour window as a rate limit: "too many requests in a short time trigger rate limiting, which recovers automatically once the window rolls over". Both groups share the membership's monthly total: "if the monthly total is reached, Kimi Code quota is frozen until the monthly quota resets or you upgrade." On 2026-09-12 the page described one 7-day quota and the 5-hour window, with no new or legacy split.

Checked

Kimi Code documentation, overview

The model multiplier quoted in the section on why the unit matters: "k3 (1M) consumes about twice as much quota as k3-256k". The same page gates models by tier (k3 from Moderato or Plus up, the up-to-1M context window from Allegretto or Pro up), which is why a tier's price does not by itself say which models it reaches.

Checked

MiniMax Token Plan pricing

The MiniMax row: Plus $22, Max $55 and Ultra $132 per month, each listing "Quota windows: 5-hour rolling and weekly windows" and an "Agent usage" sizing of 3-4, 4-5 and 6-7 agents. The unit wording is verbatim: "Token Plan subscriptions provide a monthly usage quota and access to eligible resources through the Subscription Key. Usage is shown as a usage bar in the console." A live subscribe control was present, which is the basis for recording signup as open. No numeric allowance is published anywhere on the page.

Checked

MiniMax Token Plan overview

The consumption rule and the monthly cell in the windows table: usage "deducts from the included Token Plan quota according to the corresponding endpoint pricing", and "unused subscription quota does not carry over to the next billing cycle". No reset behaviour is stated for the weekly or monthly window on the pages read, which is what that cell records rather than inferring one.

Checked

Alibaba Cloud Model Studio, Coding plan overview

The single source for both Alibaba Coding Plan rows; the page stated "Updated at: 2026-09-11" on the first read, and the figures below read the same on 2026-09-29. Verbatim: price "¥ 200/month"; the unit definition "Each query consumes quota based on the number of model calls. Simple tasks typically use 5–10 calls, while complex tasks may use 10–30 or more."; the quotas "Up to 6,000 requests per 5 hours / Up to 45,000 requests per week / Up to 90,000 requests per month"; the stacking rule "The three limits above apply simultaneously as caps, and whichever is reached first takes effect" together with "The limits are not cumulative and do not represent a guaranteed capacity distributed evenly over time"; the resets ("Usage from 5 hours ago is restored", "Resets every Monday at 00:00:00 (UTC+08:00)", and a monthly reset on the subscription renewal date); the throttling clause "When overall platform load is high, or when a single account consumes an unusually concentrated amount of resources within a short period, we may temporarily queue, throttle, or briefly interrupt requests from that account"; the rationing sentence "Slots are limited and available on a first-come, first-served basis. New slots are restocked daily at 09:30:00 (UTC+08:00)" with the Lite tier closed to new subscriptions as of March 2026; and the withheld concurrency thresholds, which are "part of platform security and stability policies".

Checked

Alibaba Cloud Model Studio, Token Plan (Personal Edition)

The Token Plan rows, re-read on 2026-09-29: Lite, Essential, Standard and Pro at "Original price 60 CNY/month Limited-time 39 CNY/month", 120 and 79, 180 and 139, and 600 and 499 CNY, with monthly quotas of 11,500, 25,500, 45,000 and 180,000 Credits and 1–2, 2–3, 3–4 and 6–8 concurrent agents. The weekly quota ended on September 22, 2026 ("When the weekly quota was removed on September 22, 2026, the remaining quota … was reset once"), and "A 30-day subscription cycle starts from the subscription date"; on 2026-09-12 the page gave 2,500, 10,000 and 40,000 Credits per 7-day window timed from first use, and no Essential tier. Unused Credits do not carry forward, and no 5-hour window or peak-time policy appears. This is a general Model Studio subscription rather than a coding-specific plan; it appears here because the vendor's coding tooling documents it as a billing option.

Checked

OpenCode Go documentation

The OpenCode Go rows; the page states it was last updated 2026-09-28 (2026-09-10 on the first read). Verbatim in English: "Usage limits are defined as monthly dollar amounts."; "Each model has the following usage limits: 5-hour — 20% of the monthly limit; weekly — 50%; and monthly — 100%."; and the DeepSeek pass-through "Peak hours are 01:00-04:00 and 06:00-10:00 UTC, Monday through Friday; all other hours, including weekends, are Off-Peak", where peak token rates are double the off-peak rates. The per-model monthly limits quoted (Kimi K3 $15, GLM-5.3 $15 and GLM-5.3-Flash $60 on Go; $60, $120 and $180 on Go Plus, a $40 tier added since the first read with the same token prices) come from the same table, which budgets each model separately rather than pooling them. The page states that the limits may change based on early usage and feedback, and it publishes no reset behaviour for the three windows. It was served in Korean localisation on first read; the English sentences were retrieved separately from the same URL.

Checked

OpenCode Go product page

The $10 per month price in USD and the live subscribe control that is the basis for recording signup as open. The $40 Go Plus tier was read on the documentation page on 2026-09-29.

Checked

DeepSeek API documentation, Models & Pricing

The DeepSeek row, read in a browser. Confirms there is no subscription of any kind and that billing is balance deduction: "The expense = number of tokens × price. The corresponding fees will be directly deducted from your topped-up balance or granted balance". The peak policy is verbatim: "Off-peak rates are half of the peak rates. Peak hours are 01:00 - 04:00 and 06:00 - 10:00 UTC, Monday through Friday, excluding Chinese public holidays. All other hours are off-peak, including weekends and Chinese public holidays in full." The holiday clause was not on the page on 2026-09-12. The same page publishes per-model concurrency limits (2500 for deepseek-flash, 500 for deepseek-v4-pro), which is the basis for the sentence that DeepSeek is the one vendor here printing concurrency figures.

Checked

Claude Help Center, what is the Max plan?

The reference-grammar row, from an article marked "Updated this week" on 2026-09-29 (dated August 8, 2026 on the first read). Verbatim: "Max 5x includes five times the Pro plan's per-session usage allowance"; "Your session-based usage limit will reset every five hours. Max plans also have a weekly usage limit that applies across all models. The weekly limit resets at a fixed time each week that is assigned to your account. Your reset day and time stay the same regardless of when you start using Claude or when your subscription begins"; and the reserved clause "we may limit your usage in other ways, such as weekly and monthly caps or model and feature usage, at our discretion". This article's "Priority access" benefit is early access to new models and features, so the peak sentence cites the Pro article. Prices confirmed at $100 and $200 per month.

Checked

Claude Help Center, what is the Pro plan?

The $20 per month price in the same row, from an article marked "Updated this week" on 2026-09-29, and the confirmation that no absolute unit is published for it either: "The Pro plan offers more usage per session than the Free plan" ("at least five times" on the first read), and "The number of messages you can send will vary based on message length, including the length of files you attach, the length of your current conversation, and the model or feature you use", with a weekly limit that "applies across all models". Its benefits list carries the peak sentence: "Priority access to Claude during high-traffic periods".

Checked

Standard Thinking Coding Plan

Our own row. The page publishes three tiers at $50, $100 and $200 per developer per month, described as a smaller allowance with 5-hour and weekly limits, a larger allowance with a weekly limit only, and no 5-hour or weekly limits and "no total usage cap"; the three included models Kimi K3, GLM-5.3 and DeepSeek V4.1 Flash; and the sentence "Peak-time restrictions apply to every plan: requests may slow, queue, or time out. Priority is $200 → $100 → $50." No allowance unit, no allowance amount and no reset rule appears anywhere on the page, which is why those cells say the terms are confirmed before activation.

Checked

Standard Thinking documentation, Coding Plan limits and peak-time priority

The limits table in our documentation repeats the three tiers and adds "Peak-time restrictions apply to every plan, including $200. Requests may slow, queue, or time out. Priority is $200 → $100 → $50. An uncapped usage allowance does not guarantee processing speed or concurrency." It then states the condition this page reports rather than filling in: "Exact allowances and request and concurrency limits are confirmed before activation."

Checked

Standard Thinking pricing

The Coding Plan section of our pricing page, which carries the same three tiers and the sentence "Allowance amounts, supported tools, renewal dates, and cancellation terms are confirmed before activation", plus the note that priority "is not a latency or availability guarantee". Its FAQ supplies the signup cell in our row: "Account creation, product access, and plan activation are separate steps."

Checked

View all resources