Models charge by image, video, second, or token, depending on the model and settings. Review the available quote or estimate before submission; token-priced tasks settle on actual usage. Web generation and API calls both debit the current workspace wallet, and API calls only spend purchased credit packs.

Web and API use the same wallet in the current workspace. Web spends monthly subscription credits first; API spends purchased credits only, excluding monthly and promotional credits. Personal and team balances stay separate.

Purchased credits never expire for personal or team workspaces and require no subscription. Team subscription credits expire each period. Buying credits does not upgrade plan permissions.

Active keys are encrypted at rest and can be viewed and copied from their details. If an older key can't be recovered or may have leaked, rotate it on this page; the old secret stops working immediately and a new one is issued.

When creating or editing a key, open Advanced settings to set webhook_url, webhook_secret, and task.succeeded / task.failed / task.canceled events. Each key has its own callback config so test and production stay separate.

Generation endpoints return HTTP 402 with insufficient_credits and may include X-Aibubu-Balance. Top up the active team wallet with a permanent credit pack, then retry.

Use at least one key for test and one for production. Split further by customer or product line when needed, and give each environment its own webhook_secret.

Yes. China and Global regions use different site domains and region config. Use the base URL for the workspace region you are in, and send Authorization: Bearer <API key>.

Yes. Personal workspace owners can create and manage their own API keys, which spend only credit packs purchased in that personal workspace. Team owners and admins manage team keys. Keys are never visible across workspaces.

A refund on team permanent credit packs may be requested within 7 days only when none of the credits have been used.