What a credit is
A credit is Piye's unit for AI work. Every time Piye's AI works for you, it is metered at what that work really cost, and the credits come out of one wallet shared by Visual and Code.
- In Code, 1 credit is $0.01 of AI cost. A reply shows the credits it used under it, for example "26 credits".
- In Visual, each change and build shows the credits it used when it finishes.
Bigger models cost more per answer than smaller ones, and long conversations cost more than short ones, because the AI rereads the conversation each time. The model menus say what each model uses, so you can choose.
What uses credits
- Building and changing apps in Visual, including the pictures Piye makes for them.
- The Code agent's replies and work, in Code and in Piye Studio.
- Tab suggestions in the editor (a few hundredths of a credit each).
- Writing a Handoff brief, when you ask Piye to write it.
What doesn't use Piye credits:
- Anything on your own API key: your provider bills you, and the reply shows "$0.42 on your key" instead.
- Local models through Ollama.
- Everything that isn't AI: the editor, the terminal, previews, simulators, Git, publishing, Operations.
Where to see your credits
- In the app: Settings, Account shows credits left, this period's credits, what carried over, Starter credits and when they end, and bought credits. The account menu at the top right shows the last 14 days of use.
- On the web: Usage shows model calls, tokens and use per day, and Billing shows your credits, plan and invoices.
When credits come and go
| Credits | When they come | When they end |
|---|---|---|
| Free credits | When you claim them, and again every 6 months | 30 days after each claim |
| Monthly (paid plans) | Each billing date, once Stripe confirms the payment | After one more period, if unused |
| Bought (pay as you go) | As soon as Stripe confirms the payment | Never |
Piye uses the credits that end soonest first.
Pay as you go
On a paid plan, once its monthly credits run out:
- Buy by hand in Billing: 720 credits for every €10 + VAT, up to 10 blocks at a time.
- Auto top-up buys a block for you when your credits fall below 100, so a build never stops halfway. You set a monthly limit in euros, and auto top-up never goes past it. When it reaches the limit, it pauses for the rest of the month and emails you; raise the limit in Billing to carry on.
If your bank asks you to confirm a top-up (3-D Secure), Piye emails you and Billing shows the payment to confirm. Until you confirm it, Piye pauses when your credits run out.
When credits run out
The step that is running finishes. Then:
- Visual and Code say you're out of credits and offer Billing, where you can pay as you go or move to a bigger plan.
- Piye never moves your work to your own API key without asking: that would spend your money with your provider.
- If you have your own API keys or Ollama set up, Code keeps working with them. See Your own API keys and local models.
When you are nearly out, Piye runs one thing at a time, so the last credits go to the work you are watching.
Limits that protect your credits
- The daily pause. On paid plans, if one day uses half of a month's credits, Piye pauses and asks before going on. Choose Keep going today to continue; the pause resets at midnight (UTC). It guards against a runaway task, and Starter has none (its credits are its limit).
- One request at most. A single AI request can't cost more than 500 credits.
- The monthly limit of auto top-up, which you set.
Tips to make credits go further
- Start a new chat for a new task. Long chats cost more per reply, because the AI rereads them.
- Pick the model for the job: the model menu says what each one uses. Use the biggest models for the hardest work.
- In Code, the Effort control next to the model sets how much the model thinks before answering. Lower effort uses fewer credits.
- In Visual, Fast is the quickest way to build. See New project options.