Credits and usage

Credits help you understand and control how much AI-assisted work you are running in RIB Creative.

What credits represent

Credits are a usage unit. They may be consumed when the platform performs AI-heavy work such as planning, generating, editing, analyzing, or verifying project changes.

The exact cost can depend on the size of the request, the amount of context needed, the files involved, and the type of task. A small copy edit should generally be lighter than a broad request to rebuild an entire application.

Why usage can vary

AI work is not always the same size. Usage may increase when you ask the agent to:

• Read or reason over many files.
• Generate large amounts of UI or code.
• Make broad changes across multiple areas.
• Analyze screenshots or visual feedback.
• Run verification or debugging workflows.
• Repeat unclear work because the original prompt was too vague.

How to reduce unnecessary usage

Use focused requests. Smaller, clearer prompts are usually easier to review and less wasteful.

Do:

• Ask for one clear change at a time.
• Describe the exact page, component, or behavior.
• Include acceptance criteria.
• Ask the agent to plan before major changes.
• Review the preview before continuing.

Do not:

• Ask for many unrelated changes in one prompt.
• Say "make it better" without explaining what better means.
• Re-run the same vague request repeatedly.
• Ask the agent to inspect unrelated files when the task is narrow.

Prompt example

Update the pricing page hero.

Goal: make the value proposition clearer for founders.
Change only the hero copy and primary CTA.
Keep the existing layout, colors, and navigation unchanged.
After editing, summarize what changed and what I should review.

Usage checklist

Before a large build:

• Confirm you are in the correct workspace.
• Check your current plan and available credits.
• Break the work into phases.
• Use Plan mode when the request is broad.
• Review the result before asking for another large change.

FAQ

Does every action use credits?

Not necessarily. The product UI should be treated as the source of truth for which actions consume credits and how usage is shown.

Why did a simple request use more than expected?

The agent may have needed more context than the prompt suggested. If a page, file, or behavior is ambiguous, the system may need to inspect more project information.

How do I avoid surprise usage?

Start with a plan, keep prompts narrow, and review progress after each step. See Prompting best practices.

Next steps

• Write better prompts: Prompting best practices
• Learn the project flow: Quick start
• Review plans: Subscription plans