How credits work
Understand what uses credits, why costs vary, and how your balance is applied.
Credits measure the work Superapp performs for you. They are usage-based: a quick, targeted edit usually costs less than a request that explores a large project, reasons through a complex feature, generates substantial code, and verifies the result.
Two kinds of work use your balance
Agent usage
While building
Planning, reading project context, reasoning, writing code, and using tools such as search or media generation.
Superapp Cloud usage
After connecting Cloud
The infrastructure your app consumes, including compute, database and file storage, data transfer, functions, and realtime messages.
Both are shown in credits and deducted from your Superapp balance. Cloud usage is also broken down by project so you can see which app and resource created the cost.
How building credits are calculated
Superapp records the actual AI usage for each step, applies the rate for the selected model, and converts that provider cost into credits. The current calculation is:
building credits = underlying model and tool cost × 3The total can change from one request to another because it includes:
- Model: Smart is suited to everyday work; more capable modes generally use credits faster.
- Context: reading more project files or a longer conversation requires more input.
- Output: a broad feature usually needs more reasoning and generated code than a focused adjustment.
- Tools: searches, transcription, image work, screenshots, and other metered operations add their own usage.
- Verification: multi-step work may spend credits while checking and correcting the result.
What different requests usually mean
A small visual or text change
Usually a fraction of a credit when the target is clear and Superapp only needs to inspect and modify a small part of the project.
A complete screen or connected feature
Often costs more because Superapp must understand neighboring code, make several coordinated edits, and verify the full interaction. A substantial screen can be around one credit, but the actual total depends on the work performed.
A long autonomous or debugging task
Can cost several credits when it involves deeper exploration, repeated tool calls, complex reasoning, multiple fixes, or a higher-capability model.
A request that fails or is stopped
If no AI or tool work starts, there is no usage to record. If Superapp has already performed part of the work, that completed usage can still consume credits even when the final result fails or you stop the run.
Search and other metered tools
Web search is charged separately at 0.03 credits per search request. A single task can make more than one search. Voice transcription, images, icons, and other generated media are metered according to the service used, so they do not all have the same cost.
How Superapp Cloud credits are calculated
Cloud usage is measured from the resources your connected project actually consumes. Superapp converts the infrastructure cost into credits with this calculation:
cloud credits = underlying infrastructure cost × 4- Compute: time the cloud project is actively running.
- Database storage: information retained in database tables.
- File storage: photos, audio, documents, and other stored objects.
- Data transfer: information sent out from the project.
- Functions and realtime: backend function calls and live messages.
Open the Cloud usage view for a project to see its category breakdown. Recent Cloud activity can take up to an hour to appear, so the chart may briefly trail the balance.
How your available balance is used
The credit number in Superapp combines the active credit sources on your account. When usage is recorded, Superapp applies them in this order:
- Daily free credits
- Promotional credits
- Credits included with the current subscription
- Purchased top-up credits
Using the shortest-lived credits first protects the more flexible balance. Promotional and top-up credits show an expiration date when one applies. Purchased top-ups carry across billing cycles and are currently valid for twelve months.
Resets, renewals, and top-ups
- Daily free credits refresh on the schedule displayed beside your balance. Unused daily credits do not stack indefinitely.
- Subscription credits refresh with the billing period. The new allowance replaces the remaining subscription allowance rather than adding to it.
- Eligible paid accounts can buy a one-time top-up without moving to a larger monthly plan.
- Promo and top-up balances remain separate internally even though the main credit number shows one usable total.
Make credits go further
- Name the exact screen, behavior, and expected result.
- Use Smart for routine work and move up only when the task needs deeper reasoning.
- Group one coherent change together instead of sending many tiny follow-ups.
- Split very broad redesigns into testable milestones before implementation.
- Attach only the files and references that matter to the current request.
- Check Cloud usage by project when the balance changes between building sessions.