MaShop · Code and AI agents

Compare what the balance actually pays for.

A credit amount is useful only alongside its usage rules. Read the current billing details, examine actual consumption and keep the cost of building separate from assumptions about a finished result.

Open MaShop

Read the current credit categories

Lovable’s current documentation describes credits for building, chatting and operating supported hosted features. Consult its balance and usage details for the categories, grants, expiry and top-up rules that apply to your workspace. These rules can change; this page does not freeze a conversion table.

Measure a complete task

Record the balance before the request, after implementation and after any automatic checks or corrections. Then inspect the result. A message, a credit and a delivered application are different units; do not estimate output by dividing a balance by an assumed flat task price.

Keep MaShop’s limits distinct

MaShop separates AI credits from preview minutes and connected-provider limits. Discussion and implementation consume the available credit balance. Read the current pricing and account balance before a larger task, and check the models available to your account.

Check the recharge before paying

Review the amount and current offer in the checkout. Opening a payment link does not add credits by itself. After payment confirmation, check the credited balance and any reported payment issue before launching another task.

Common questions

How many finished applications does a credit buy?

There is no universal conversion. Scope, model usage, revisions and verification affect consumption and the delivered result.

Do these products use interchangeable credits?

No. Compare each product’s current usage rules and a measured task rather than treating their balances as the same unit.