Billing

​

Credits consumption

The following items consume Credits when you use Qoder Cloud Agents:

​

Model calls

Model calls are converted into Credits based on actual task execution. Consumption varies by model and task complexity.

​

Typical consumption estimates

These figures are estimates for typical scenarios and are provided for reference only. They are not a basis for billing. Actual consumption varies by model, task complexity, context length, and tool usage. Refer to the Credits usage details for actual consumption. For more information, see the Qoder Task and Credits Consumption Guide.

​

Sandbox billing (charges begin August 10, 2026)

Cloud sandboxes used during task execution are billed on demand based on active Session runtime and metered by the second:

• running state: Billed
• pause / idle / terminated states: Not billed

In typical scenarios, sandbox runtime generally accounts for about 5%–10% of the total Credits consumed by a Session. This estimate is for reference only and is not a basis for billing. The actual proportion varies by task type, runtime, model calls, and tool usage. Refer to the Credits usage details for actual consumption.

​

Storage

At this stage, the following storage resources are free for a limited time and do not consume Credits:

• Conversation history and task records
• Task-generated data, such as reports, code, files, and other outputs
• Uploaded attachments and files
• Private Skill repository storage for the space
• Persistent personal user data storage

Storage billing rules may change in the future. Refer to the official product announcements and pages published at that time.

​

Deduction rules

• All charges are deducted from the Credits balance.
• If a model call fails, Credits are not deducted for that call. Model calls that complete successfully are billed based on actual consumption.

​

Settlement

• Sandbox runtime is metered by the second and its charges are settled hourly. Model calls are converted into Credits based on actual consumption.
• Charges are deducted from the Credits balance.

​

Personal mode (prepaid Credits)

​

Billing model

Personal mode uses prepaid Credits. For more information, see Credits.

• Purchase before use: Purchase and allocate a Credits pack before using the service.
• Unified deduction: All charges are deducted from the Credits balance.
• Usage-based metering: Model-call and sandbox-runtime charges are deducted from the Credits balance based on actual usage.

​

Purchase and allocation

You can combine multiple Credits packs purchased through the following international channels:

• Alibaba Cloud international website: Purchase a Credits pack
• Alibaba Cloud International Marketplace: Purchase a Credits pack

Personal mode currently uses Qoder Teams shared add-on Credits for purchase and allocation. You need an existing Qoder account and a Teams seat. After purchase, allocate the Credits to the current Qoder Cloud Agents PAT user. Before purchasing, confirm the applicable site, organization, validity period, and allocation target. Purchase and allocation rules are subject to the purchase page and the information displayed in the Qoder console.

​

Credits pack rules

• A Credits pack can be used after it is purchased and allocated. Refer to the Qoder console for its activation status.
• Multiple packs can be combined. Refer to the Qoder console for Credits balances, pack expiration dates, and deduction order.
• If the Credits balance is insufficient, a task might not start or continue. You can start a new task after Credits become available.

​

Enterprise spaces (coming soon)

After enterprise spaces become available, Qoder administrators and configuration administrators can access the Qoder Cloud Agents console for the same enterprise space and jointly configure enterprise data. Purchase options and Credits consumption details for enterprise spaces will be added to this guide after launch.

​

Qoder console shortcuts

• Member configuration
• Shared add-on Credits allocation