Token Plan FAQ

WOX Token Plans, subscription quota, API Keys, and request limits

A Token Plan provides an account with subscription quota that can be used during the plan's validity period. Subscription quota, wallet balance, API Key restrictions, and request rate limits are separate mechanisms and apply independently.

---

1. How Token Plans Work

After a purchase is completed, the system creates a subscription record for the account with a start time and an end time. While the subscription is active, requests can use its quota according to the account's billing preference.

A Token Plan and wallet balance can exist at the same time. Purchasing a plan does not automatically create a special API Key, and it does not automatically increase access to every model, request rate, or upstream capability. If a plan includes a user group or other additional benefits, the details shown on the purchase page apply.

---

2. How Subscription Quota Is Deducted

Each subscription record uses one general quota pool. Text, image, audio, and asynchronous tasks do not have separate fixed usage-count pools by default.

The actual cost of a request may depend on the following factors:

• The model and billing method used
• Input, output, and cached Tokens
• Image count, quality, dimensions, or other generation parameters
• Audio duration, task duration, and other task specifications
• Tool calls and additional model capabilities
• Channel multipliers, the user's group, and upstream prices

Subscription quota therefore cannot be treated as a fixed number of Tokens, requests, images, or video seconds. Final usage is based on the system's settlement records. Current model prices are shown on the Models and Pricing page.

---

3. Validity Periods and Quota Resets

Different plans can have different validity periods and reset rules. Before purchasing, confirm the following information on the plan card and checkout page:

• The plan's validity period
• Whether the quota resets and, if so, its reset schedule
• Whether purchase limits apply
• Whether wallet balance can be used after the subscription quota is exhausted
• Whether a user group or other additional benefits are included

At the reset time, the system restores the available quota for that period according to the plan configuration. Unused quota generally does not carry over to the next period. After a subscription expires, its remaining quota is not automatically transferred to the wallet or another subscription unless the purchase page explicitly states otherwise.

---

4. Billing Preferences

An account can select which quota source requests should use first on the wallet page.

When an account has no active subscription, saving the "Subscription first" preference does not create subscription quota. The system processes requests using the billing sources that are currently available.

---

5. API Keys and Token Plans

WOX users create general-purpose API Keys and do not need to create a separate key for a Token Plan. Whether a subscription participates in billing depends on the account's subscription status and billing preference.

Each API Key can still have its own settings for:

• Key quota limit
• Validity period
• Available models
• Available groups
• IP access restrictions

An API Key's own restrictions apply together with the account subscription, wallet balance, and platform request limits. Creating multiple API Keys does not increase the account's subscription quota, wallet balance, or user-level request limit.

---

6. Request Rate Limits

RPM (Requests Per Minute) is the number of requests that can be processed per minute. Request rate limits and subscription quota are separate mechanisms:

• Request rate limits control how many requests can be initiated or completed successfully within a given period
• Subscription quota controls how much available quota remains after requests are settled

The platform applies user-level request limits to applicable API routes according to the current system configuration. Some user groups may use different settings, and upstream providers may impose additional concurrency, rate, or usage limits.

A Token Plan does not include a fixed RPM commitment by default. Actual limits depend on the account's current configuration, API responses, and upstream status. When a limit is reached, the API usually returns HTTP 429. If the response includes Retry-After, wait for that period; otherwise, use exponential backoff and limit the number of retries.

---

7. Models, Images, and Task Specifications

WOX aggregates models from multiple upstream providers. Supported APIs, dimensions, aspect ratios, quality settings, durations, and response formats vary by model and may change when an upstream provider updates its service.

Therefore:

• There is no single 1K, 2K, 3K, or 4K output-size table that applies to every image model
• Whether exact dimensions are accepted, rejected, or normalized depends on the specific model and upstream channel
• Image count, audio duration, and task duration may affect billing, but this does not mean that the plan provides separate fixed generation-count pools
• Model availability, pricing, and parameter support are determined by the models page and the corresponding API responses

For production use, validate parameters, error handling, timeouts, and retry behavior against the selected model. Do not rely on the specifications of another model or upstream provider.

---

8. Purchases, Renewals, and Refunds

Before submitting an order, confirm the price, payment method, validity period, and any automatic renewal terms shown at checkout. Payment channels may offer one-time purchases or recurring subscriptions; the checkout page and payment-channel order determine which arrangement applies.

Canceling automatic renewal only affects future charges and does not refund an order that has already been paid. Unless applicable law requires otherwise or the purchase page explicitly promises otherwise, Token Plans do not support no-reason refunds. Refunds, incorrect charges, and cases in which the service can no longer be provided are handled under the User Agreement, the applicable order terms, and applicable law.

---

9. Frequently Asked Questions

Q1: Which plans and quota amounts are currently available?

See the Token Plan page. Plans are configured dynamically by the system, so this document does not maintain a fixed list of tiers, prices, or quota amounts.

---

Q2: Do I need a dedicated API Key after purchasing a plan?

No. Existing and newly created general-purpose API Keys can make requests according to the account's subscription status and billing preference. The key's own quota, model, group, and IP restrictions still apply.

---

Q3: Does creating multiple API Keys increase subscription quota or RPM?

No. Multiple API Keys can isolate applications and environments, but they do not combine or increase the account's subscription quota, wallet balance, or user-level request limit.

---

Q4: What happens after the subscription quota is exhausted?

The system uses the billing preference and the plan's balance-fallback configuration to determine whether it should continue using wallet balance. If "Subscription only" is selected or the plan does not allow fallback, requests fail when there is insufficient subscription quota.

---

Q5: How are images, audio, and other tasks billed?

Like text requests, they are converted into general quota according to the system's pricing rules. Parameters such as image count, quality, dimensions, audio duration, and task duration may affect usage. Final usage is based on the system's settlement records.

---

Q6: Does purchasing a Token Plan increase request rate limits?

Not necessarily. Only user-group access or request benefits explicitly listed on the purchase page are included in the plan. Other platform and upstream limits continue to apply.

---

Q7: Does subscription quota accumulate after a reset or expiration?

Generally, no. Quota resets on the schedule configured for the plan, and the subscription can no longer be used after it expires. The validity period and reset rules shown at the time of purchase apply.

---

10. Before You Begin

Before purchasing a plan or integrating WOX into a production system, confirm:

1. The validity period, reset rules, and purchase limits shown on the plan page
2. The target model is currently available and its pricing and parameters meet your requirements
3. The billing preference and wallet-fallback behavior meet your business requirements
4. The client handles 429 responses, upstream errors, timeouts, and retries
5. You have read the User Agreement and Privacy Policy