What is a credit
A credit is one cent of AI spending, and this page names every action in MaShop that consumes none of them.
Credits
A credit is one cent of spending inside MaShop. One hundred credits cost one dollar, always.
Every AI action is priced on what the model provider really charged for it. MaShop takes that real cost, multiplies it by five, then converts it at 100 credits per dollar. The result is rounded up to the nearest hundredth of a credit. The smallest possible charge is 0.01 credit, not one credit.
The multiplier is the same for every model. None of the models you can pick carries its own markup.
Where your credits come from
The number in the top bar is a total. It adds up separate buckets, and the Credits tab breaks it down.
- Plan credits. The monthly allotment of a Pro or Max subscription.
- Top up credits. What you bought with a one off payment.
- Bonus credits. Tier bonuses on larger purchases, and referral rewards.
A new account receives zero credits at signup. There is no welcome grant and no weekly refill.
Which bucket pays first
Spending drains plan credits first, then your wallet. The wallet holds top up and bonus together.
That order matters at the end of a billing period. Plan credits go before the ones you paid for separately. A month of heavy work therefore eats the subscription allotment first.
A fourth line, Weekly credits, appears only on older accounts that still hold some. Nothing refills it any more, and it is spent before everything else.
The split between Top-up credits and Bonus credits is a reconstruction, not an accounting. MaShop stores the wallet as a single number. The screen splits it by assuming bonus is spent last. The two lines can move oddly after a refund or a manual correction. Only the total is a hard fact.
What costs you nothing
Most of what you do in a day debits nothing. This is the full list.
| Action | Charged |
|---|---|
| Opening a project, reading and editing files, browsing your code | Nothing |
| Opening your repository on GitHub, or cloning it | Nothing |
| Deploying or updating what you published | Nothing in credits |
| Publishing for the first time, which creates your infrastructure | Nothing in credits, but a paid plan is required |
| Restoring an earlier version | Nothing |
| Archiving, duplicating, transferring or deleting a project | Nothing |
| Inviting a collaborator and changing their role | Nothing |
| A reply that comes back empty | Nothing, the reservation is cancelled |
| A generation you interrupt, or a connection that drops | Nothing, unless the charge was already confirmed |
| A message refused by the content policy | Nothing, the refusal happens before any reservation |
| The reply telling you GitHub or Supabase is not connected | Nothing |
The /goal command | Nothing, it is handled without calling a model |
| The difficulty classifier behind the Auto model | Nothing, its tokens never reach the credit confirmation |
| An automation stopped by its own time ceiling | Nothing |
What does cost credits is short to list: a message to the assistant, a content generation, and an automation run.
Where you see what you paid
Each assistant reply carries a badge with the credits actually debited, to two decimals. That number is the final one, after adjustment, not an estimate. It is also the only figure that settles a question about price.
The Credits tab holds a usage chart with seven windows: today, the last 7, 30 or 90 days, this month, last month, and the last twelve months. The curve is net of refunds, so a run that was refunded counts as nothing.
There is no line by line statement anywhere in the product, and nothing reaches past twelve months. If you need itemised spending for accounting, record it as you go.