Balance and billing

We meter in CU (Compute Units), a single yardstick that maps models from different providers with different pricing structures onto one scale.

Each capability group has a published input and output CU multiplier, shown on the pricing page and in the console. CU for a call = input tokens x input multiplier + output tokens x output multiplier, rounded up to the smallest metering increment.

Every historical change to a multiplier is published. We never retroactively re-price usage already metered.

A subscription grants monthly quota subject to three simultaneous windows: a per-session ceiling, a weekly ceiling and a monthly ceiling. Hitting any one pauses service until that window resets.

The weekly window exists so capacity is distributed predictably across the month. Without it, a handful of users exhaust a month of capacity in three days, directly degrading availability for everyone else.

Your billing period is anchored to the day you subscribed (in Asia/Shanghai). If that day does not exist in a given month — the 31st in February — the period ends on the last day of that month and the next period returns to the 31st. The anchor is stored separately so one short month never permanently shifts your renewal date.

Quota does not carry over. Anything unused is cleared at the end of the period. We say so on the purchase page rather than burying it here.

Once quota is exhausted you may enable pay-as-you-go, which continues from your balance.

It is off by default. You must switch it on and set a monthly spending ceiling when you do. Charging stops at the ceiling; it will not quietly keep drawing because you weren't watching.

Pay-as-you-go draws from your balance at ¥1 = 500 CU, using the same per-model CU rates as your plan, charged on actual tokens; each key can opt out individually. Per-model rates are published in the console model catalog.

If your balance runs out, pay-as-you-go pauses. No arrears accrue, and your next subscription period restores in full. We offer no overdraft or credit of any kind.

Paid balance: what you actually paid for. Usable for pay-as-you-go and renewals, returnable under the Refund Policy, invoiceable.

Bonus balance: what we granted you through a promotion, a goodwill credit or an SLA remedy. Non-refundable and non-invoiceable, valid for 90 calendar days by default, expiring unused. The exact expiry date is stated when it is granted.

The console shows the two separately, and every deduction records which kind it came from.

Deductions take bonus balance first, then paid balance, and within bonus balance the earliest expiry first.

That order is the one that favours you: it burns down what would expire and preserves what is refundable.

Top-ups credit in real time. The payment channel receipt is the sole basis for crediting — we will not double-charge because a page showed an error, and we will not lose your payment because a callback was delayed: the system queries the channel to reconcile.

Topping up carries no surcharge of any kind. Payment channel fees are ours to absorb.

Per-transaction and account balance ceilings are shown in the console; above those, contact us about enterprise settlement.

Every movement of balance is written to an append-only, non-modifiable ledger recording time, amount, kind, reason and the associated order or call trace ID.

A scheduled job checks the balance snapshot against the ledger. When it finds a discrepancy it reports and does not repair. A program authorised to rewrite the ledger is itself a reason the ledger cannot be trusted. Discrepancies are investigated by a person and the investigation is recorded.

You can export the full ledger from the console at any time. If your records disagree with ours, whichever side can trace the entry to a specific call trace ID prevails; where neither can, we resolve it in your favour.

We do not offer withdrawals. Balance cannot be sent to a bank card or third-party payment account, transferred between users, or used to pay on behalf of anyone else.

Balance can only be returned through the original payment channel to the original account, matched entry by entry against the original top-up, capped at the unconsumed part of that top-up. Conditions are in the Refund Policy.

This is not about keeping your money. A balance that can be freely transferred out is a money transmission channel, which makes it an immediate vehicle for laundering and fraud and would place us under payments-industry compliance obligations. Returning funds the way they came is the only way to give money back without becoming one.

A subscription already purchased is locked to its price and quota terms for its period, whatever changes during it.

Subscription price changes are announced 30 calendar days ahead, apply from your next period, and you may cancel before they take effect.

A CU multiplier decrease (in your favour) applies immediately. An increase is announced 30 days ahead and never applies to a period already under way.

The money-to-CU conversion for pay-as-you-go (¥1 = 500 CU) does not float with upstream prices; per-model CU rates follow our cost, decreases apply immediately, increases are announced 30 days ahead.

Renewals are charged to your paid balance. If the charge fails, service pauses immediately, but the subscription is kept for at least 7 days; the console shows the date it is kept until. Top up within that time and service resumes automatically, with nothing to re-purchase. If it has not been restored by then, the subscription ends, we email you, and you can subscribe again at any time.

No debt builds up while service is paused, and we never charge afterwards for the paused time. Restoring is charged under the rules published at that time; the amount, and whether your billing date changes, are shown in the console before you top up, and a balance of that amount is enough to restore service.

If you pay for a subscription while you already have one that is active or awaiting renewal, we do not start a second one. That payment is refunded to the original payment method; where that is not possible, it is credited to your paid balance, and we email you what was done. Such a refund does not use up your one-time full refund on a first subscription.

Paid balance and subscription fees are invoiceable; request it in the console and we typically issue within 3 working days.

Bonus balance, SLA remedies and refunded amounts are not invoiced. Refunding an already-invoiced amount requires the invoice to be cancelled first.

Every call has a unique trace ID; the console shows its time, model, token counts, resulting CU and which balance it drew from.

If you believe a charge is wrong, send the trace ID to support@agiplan.dev. Where the error is confirmed as ours we refund the charge in full and add an equal amount of bonus balance. We typically conclude within 2 working days.

The disputed amount does not affect your ability to keep using the service while we look at it.