How AI credits work

Understand the counting unit

A credit belongs to a successful command whose result is saved. It is not a charge per word, per click or per minute spent reviewing your website. Distinguish submitting an AI request from directly changing an existing page. A shorter prompt does not automatically cost fewer credits. The content of your request still matters: a specific task makes it easier to decide whether the saved result meets your needs and which details require further attention.

Prepare the facts before sending

Gather accurate information before you submit a command. Describe the audience, page objective and change you need. Identify the parts that should remain intact. Do not fill gaps with invented prices, credentials or customer reviews. If the structure works and only two sentences need correcting, edit those sentences directly. A tightly defined task makes the output easier to check, but it does not guarantee that every business detail will be right in the first version.

• Verify contact details and the exact offer.
• Describe one main problem and the intended outcome.
• Identify facts that must remain unchanged.

Plan your trial allocation

You can use up to three trial credits within the applicable limits. This is an upper limit, not a promise that every request will be available at every moment. Plan one initial generation and keep some room for a focused revision after reviewing the design. Avoid repeatedly submitting the same vague request just to compare variations. Instead, identify what is missing and decide whether a manual change will solve it. This keeps the trial focused on a useful website.

Read the final status after an error

A credit may be reserved while a command is processing. If that command fails, the reservation is returned. Check the final status and saved result before submitting the same request again. Avoid sharing sensitive information from an error message with another person. Record the time, the action and a safe description of what happened instead. An unsatisfactory result that was successfully saved is different from a technically failed command. That distinction matters when you review your usage.

• Wait for a clear final status.
• Check whether a new result was saved.
• Do not automatically repeat a request that is still processing.

Separate a test from a real purchase

The checkout for extra credits and Signature designs currently operates in test mode. This does not establish that real payments or commercial delivery are active. The 108 included designs are separate from the six Signature designs, which have a licence per website. A design licence and AI credits serve different purposes. For any future purchase, check the price, contents and terms on the actual checkout screen rather than relying on an old screenshot or this guide.

• Identify whether the environment is in test mode.
• Keep design licensing separate from AI usage.
• Do not make a real payment during verification.