Skip to main content

How Credits Work

Kite uses credits to pay for the work it does. Every conversation you have with Kite and every task it runs draws from your credits. One credit is one US dollar of usage. This page explains what uses credits and how to make yours go further.

What uses credits​

  • Conversations in Slack, by email, or in the editor use credits each time Kite responds.
  • Tasks use credits: research, drafting a page or an email, building or editing your website, running a Growth Grader report, restoring an earlier version of your site.
  • Complex work (a full initiative, a multi-page build, a large rewrite) uses more than a small change.
  • Retries use credits too. If Kite has to try something again or fix an error, that is additional work.
info

Reading Kite's posts in Slack, viewing your site preview, and publishing do not use credits. It is the research, drafting, and building that draws them down.

The three kinds of credits, and the order they are spent​

  • Signup credits. A one-time grant of $15 per team on the Free plan. These never reset.
  • Monthly credits. $100 each month on Growth. They expire at the end of the billing cycle and do not roll over.
  • Purchased credits. Credit packs you buy on a paid plan. They do not expire.

Kite spends signup credits first, then monthly credits, then purchased credits, so purchased credits are kept in reserve until you need them. See Buy More Credits.

When credits run out​

Kite pauses new work and tells you: "Your team is out of Kite credits. Upgrade or add credits to keep going." Your live website, hosting, analytics, and leads keep working. Upgrade or buy a pack and Kite picks up where it left off.

Tips to use credits efficiently​

  1. Give Kite context early. Correcting its research in the first week saves credits on every plan that builds on it.
  2. Be clear and specific. "Change the pricing page headline to 'Scheduling that saves your front desk an hour a day'" works better than "make the top nicer." Specific requests get the right result the first time.
  3. Make one change at a time. Smaller, focused requests are easier for Kite to get right and easier for you to review.
  4. Describe the outcome you want, not the steps.
  5. Review before you re-request. If a draft looks close, ask for a specific revision rather than a full do-over.

When Kite loops or repeats failed actions​

Occasionally Kite gets stuck: retrying the same action, failing repeatedly, or looping. Because retries use credits, a loop can quietly burn through them.

  1. Stop it. In the editor, press Stop to cancel the running turn. In Slack, do not keep sending the same request.
  2. Rephrase. Describe the work differently, or break it into smaller pieces.
  3. Restore if needed. If the loop left your site in a messy state, restore a working version. See Version History.
  4. Contact support. If Kite keeps looping no matter how you phrase the request, open Chat with us in Kite. Repeated, unproductive loops are not something you should have to pay for.

Common questions​

Why did a small-sounding change use a lot of credits? "Small" to you can be large for Kite. Changes that touch many parts of a page, or that required retries, use more.

I ran out of credits mid-project. What now? On Growth or Business, buy a credit pack. On Free, upgrade to Growth. See Buy More Credits.

Credits got used up by a loop that was not my fault. Can that be fixed? Open Chat with us and explain what happened.