Developer levels combine sustained API usage and community participation into four stages: D0, D1, D2, and D3. Eligibility never changes billing configuration automatically. When every condition for the next level is met, the system creates a pending review. An administrator or Root must approve it before the user is moved to the special group bound to that level.
Where to check your level
After signing in, open Personal Center. The Developer level section shows:
- Your current level, current group, and next level.
- The current value, target, and result for every upgrade condition.
- The latest level review status.
- A D0-D3 comparison of effective multipliers for each billing group, including whether each value comes from a special rule or a base fallback.
Exact usage and activity values are visible only to you. Other people cannot retrieve them from your community profile.
Upgrade conditions
Every level uses an all-conditions-required rule, and progression is sequential: D0 → D1 → D2 → D3. Even if your data meets a higher level, the system reviews only the next level first.
The four configurable conditions are:
| Condition | Measurement |
|---|---|
| Cumulative API usage quota | Platform billing quota accumulated after successful settlement, not a token count; Personal Center converts it to the platform quota display unit |
| Account age | Full days elapsed since the account was created |
| Successful API requests | API requests that completed successfully and entered the existing settlement counter |
| Community active days in the last 30 days | Asia/Shanghai calendar days within the rolling 30-day window that contain at least one valid community action |
Operators can update the thresholds for each level. The current values and targets shown in Personal Center are the rules in effect and should be treated as authoritative.
How community active days are counted
The following actions can create a valid activity source:
- Sending a public user message that is neither blocked nor deleted.
- Completing the daily check-in.
- Submitting a valid poll vote.
- Completing a valid community activity participation.
Multiple valid actions on the same day still count as one active day. Agent, system, private, blocked, and deleted messages do not count. Deleting a message or invalidating an activity participation removes that source. The day remains active when another valid source still exists for that day.
What happens after you qualify
- The evaluator confirms that every condition for the next level is met.
- The system creates a pending review without changing your group.
- An administrator or Root recalculates all conditions and checks the policy version, current group, and subscription state.
- After approval, your account moves to the special group bound to the level. New requests then use that group's effective multipliers.
Changes to conditions, policies, or your current group can temporarily prevent approval. Personal Center continues to show the current review state.
Reading the D0-D3 multiplier table
The D0 column shows base billing-group multipliers. D1-D3 show the effective multipliers resolved for each level's special group. Every cell also identifies its source:
- Special rule: the level group defines a dedicated multiplier for that billing group.
- Base fallback: no dedicated value exists, so the billing group's base multiplier is used.
- Not configured: the billing group is unavailable or has not been configured for that level.
The following snapshot reflects the configuration in effect on July 29, 2026 and makes the price difference between levels directly comparable:
| Billing group | Description | D0 | D1 | D2 | D3 |
|---|---|---|---|---|---|
banana | Google Banana image models | 1.00x | 1.00x | 1.00x | 1.00x |
china | Overseas Chinese coding models | 0.60x | 0.55x | 0.50x | 0.45x |
claude | Claude backup route | 0.60x | 0.55x | 0.50x | 0.45x |
claude-aws | Claude Bedrock enterprise route | 4.20x | 4.10x | 4.00x | 4.00x |
claude-max | Claude Max stable route | 1.50x | 1.45x | 1.40x | 1.30x |
codex | OpenAI GPT standard route | 0.30x | 0.28x | 0.25x | 0.23x |
codex-cheap | OpenAI GPT limited-offer route | 0.13x | 0.13x | 0.13x | 0.13x |
codex-pro | OpenAI GPT stable route | 0.60x | 0.55x | 0.50x | 0.48x |
default | Default group | 1.00x | 1.00x | 1.00x | 1.00x |
embedding | Embedding and reranker models | 0.80x | 0.80x | 0.80x | 0.80x |
gemini | Google Gemini models | 2.40x | 2.30x | 2.20x | 2.00x |
grok | xAI Grok chat and coding models | 0.25x | 0.20x | 0.18x | 0.15x |
grok-image | xAI Grok Imagen models | 1.00x | 0.95x | 1.00x | 1.00x |
image | OpenAI image models | 1.00x | 1.00x | 1.00x | 1.00x |
image-4k | OpenAI native 4K image models | 2.25x | 2.20x | 2.18x | 2.18x |
seedance | Seedance 2.0 video models | 1.00x | 1.00x | 1.00x | 1.00x |
default and embedding currently use the base fallback at D1-D3; every other D1-D3 value comes from a special multiplier rule. Operations may change the configuration, so the live D0-D3 table in Personal Center remains authoritative.
These are group multipliers from the existing billing path, not a separately maintained discount label. Final request charges still follow the model price, selected billing group, and the complete settlement rules active for that request.
Relationship with subscriptions
Developer levels do not modify subscription plans, subscription quota, or subscription billing. While an active subscription changes the user's group:
- The subscription group takes priority, and level multipliers do not stack with subscription multipliers.
- A qualified level review can remain pending, but it cannot switch the level group while the subscription conflict exists.
- When the subscription group ends, the group saved before the subscription is restored.
Developer levels therefore represent long-term growth through API use and community participation, while subscriptions continue to operate independently under their existing rules.