How AI usage is charged
Each request costs what the AI models cost, with nothing added. You see the usual cost before you send and the live cost while it runs. Requests that fail or repeat the same error are not charged, and a limit per request caps any request.
Updated
On this page
One credit is one US dollar of AI usage. A request is charged exactly what the AI models cost for it. Each plan includes some usage every month: see Plans.
When Crisp charges#
- Each request is charged what the AI models cost for it, in dollars, with nothing added.
- A request you stop yourself is charged for the work done until then.
- A request that reaches your limit per request pauses there. It is charged up to the limit, never more, and keeps what it made.
Bigger requests use more. A new page with its own data costs more than changing a colour.
When Crisp does not charge#
You never pay for Crisp getting something wrong. None of these are charged:
- A request that ends with an error, takes too long, or stops because of a problem on our side.
- The part of a request where Crisp fixes errors it caused itself.
- A build that Crisp stops because it kept repeating a fix that did not work.
- The second request in a row that ends with the same error. The chat then offers Try a different approach, which looks for the cause first.
- A build that changed nothing and still ends with a step failing costs at most 5 cents.
- Fix it on an error from Crisp's last build, within 30 minutes of it: up to 3 fixes in a row and 30 a month.
- Undoing a request within 10 minutes of it finishing gives back what it cost, up to 20 times a month.
- Using the preview, the code and the data, publishing, and keeping your published apps online.
Visual edits in the preview (Edit) never use credits: they change your code directly, without AI. See Change what you see.
What Crisp does not charge has one monthly limit: $5 plus half of what you paid for usage that month. It is there so that making requests fail on purpose cannot buy free building; most people never come near it. Past it, the line under the reply says so. When the AI provider refuses a request on our side, it is always free, with no limit.
A free request is still listed on the Billing page: charged, then given back in full, so you can see what it would have cost. The line under the reply says Free, with the reason.
Examples#
| What happened | What you pay |
|---|---|
| You ask for a booking form. It works, and the AI models used $0.18. | $0.18 |
| The same request, but Crisp broke the page on the way and spent $0.05 fixing it. | $0.13. The reply says $0.05 was not charged. |
| A request ends with an error after using $0.40. | Nothing. The reply says why. |
| Crisp stops a build after $0.90 because it kept trying the same failed fix. | Nothing, and a card offers a different approach. |
| You ask twice to fix the sign-in error, and the same error comes back both times ($0.30 each). | $0.30 for the first, nothing for the second. |
| A build changes no file and the test still fails at the end, after using $0.70. | 5 cents. |
| You press Stop after $0.25. | $0.25. Undo within 10 minutes to get it back. |
| A large request reaches your $2 limit. | $2. It pauses with its work kept, and you choose whether to continue. |
When the same error keeps coming back#
Crisp watches for a request that keeps trying the same fix. Inside one request, it stops after the same error comes back three times, even after two attempts to fix it. Across requests, the second request in a row that ends with the same error is not charged. Either way, a card in the chat says what kept failing and offers Try a different approach: Crisp looks for the cause first and writes a short plan you can check before it builds. You can also go back to the last version that worked.
See what a request costs#
- Before you send: under the chat box, what requests like yours usually cost (measured from requests that worked), your balance and your limit. If your balance or your limit may stop the request, it says so before you send.
- While it runs: the balance button and the progress card show what it has used so far.
- After: the line under the reply shows the time and the cost, and why, when anything was not charged. The Billing page lists every request and every change to your balance.
The limit per request#
Every request has a spending limit. The default is $2. When a request reaches it, Crisp stops there. The changes made so far stay in your app, and nothing past the limit is charged.
A card in the chat says Paused at your limit. Press Continue to let Crisp pick up where it stopped, or Change the limit.
- Open the account menu and choose Billing.
- Under Limit per request, enter an amount in steps of 25 cents.
- Press Save. The new limit applies to every request after that.
| Plan | Highest limit per request |
|---|---|
| Free | $5 |
| Pro | $25 |
| Max | $100 |
When you run out#
When your balance is used up, you can still use everything except new AI requests: the preview, the code, the data, publishing and your published apps. The chat tells you when your usage renews, with a link to Billing.
- Your monthly usage renews every month: on the first of the month on Free, and on your billing date on a paid plan. Unused monthly usage does not carry over.
- On any plan with AI usage, Free included, buy a top-up on the Billing page: $10 adds $8, $30 adds $24, $50 adds $40. Top-ups never expire and are never automatic.
Confirm your email address first#
On the Free plan with an email account, requests wait until you confirm your email address. Open the link in the email from Crisp, or press Send the link again on your dashboard. Signing in with GitHub works too.
Related pages
Something wrong or missing on this page? Tell us. A person reads every message.
Report a problem