Bell Credit & billing

This guide summarizes BellD's D-042 Credit model. A Bell Credit represents NT$0.01 of platform pricing value. Credit accounting uses integers. NT$100 corresponds to 10,000 Credits.

What usage costs

AI usage depends on the provider and model rate card, with separate input and output token rates. There is no universal Credits-per-thousand-tokens price. User-facing costs are shown in Bell Credits. Workspace owners and admins can inspect provider, model and token details in billing usage details.

Standard runtime (1 vCPU / 512 MiB) is 1 Credit per 10,000 ms: 360 Credits per hour. Storage is 4 Credits per GiB-day, measured from daily peak stored bytes. Per-call byte reservations are authorization units; they are not the storage billing duration measure.

Credit buckets

Subscription Credit resets each billing cycle and does not roll over. Purchased Credit does not expire. Promotional Credit can have an expiry. Spending uses expiring promotional Credit first, then subscription Credit, then purchased Credit.

Subscriptions and one-time top-ups coexist. D-042 defines NT$100 / 300 / 500 top-ups as 10,000 / 30,000 / 50,000 Credits. Plan prices, included monthly Credit and promotional offers are configurable; consult the current checkout and wallet for your workspace's offer.

Insufficient Credit

There is no overdraft, postpaid billing or automatic top-up in v0. Calls estimate, reserve, execute, settle, and release unused reservations. Insufficient balance prevents the reservation. Long-running work settles in slices and stops gracefully when the next reservation cannot be funded. Usage policy budgets can also deny a call.

BellD billing concerns the Developer's platform usage. It is separate from payments an application collects from its own customers. See Terms and refunds for the legal-review placeholder.