Credits, usage & BYOK
Learn what powers a build, what uses credits, and what changes when you bring your own AI key.
What are credits?
Credits are your Bump AI building allowance. The amount used can vary with the request, model, and key mode; one prompt is not a promise of one credit. Check Settings → Billing for the selected workspace’s allowance, remaining balance, and usage.
Free has 10 daily credits plus a separate welcome grant at sign-up. Paid plans have monthly allowances. See plans and pricing.
Build with the platform key
The platform-key option uses Bump AI’s available model configuration. It is the starting path when you do not want to connect your own provider account. Model availability and usage are shown in the builder and your billing settings.
Bring your own key
BYOK is available on Solo and Team. Add a supported provider key using the builder’s dedicated API key settings, choose the available model, and select your key for building.
The current key settings support Gemini, OpenCode, Ollama, and DeepSeek connections. The models you can choose depend on the provider and configuration available in the app. A provider name does not mean every model or local endpoint is supported.
How BYOK is billed
The current BYOK runtime rate is approximately 0.06667 credits per active minute, equivalent to 4 credits per active hour. At that rate, 100 credits provide up to 25 active hours.
These figures describe active BYOK runtime, not 25 guaranteed hours of completed app features. Your provider’s charges are separate, and Bump AI does not add a second model-usage charge for those provider requests.
Credit expiration and shared usage
Purchased monthly credits remain valid for two months from purchase. Review the credit breakdown and expiration dates in Billing; daily free credits follow the daily allowance rather than the paid rollover policy.
In a Team workspace, members draw from a shared allowance, with per-member limits where configured. Choose the correct workspace when reviewing a balance.
Manage your key safely
Use the dedicated key settings rather than pasting a secret into chat, source code, or a reference image. Stored provider keys are protected with envelope encryption and Google Cloud KMS.
If a key stops working, check its validity, the provider account’s usage balance, and the selected model. If a key has been exposed, replace it with the provider and update your connection.