Skip to content

Verament credits

Verament credits pay for VAIF Verament. Every Verament request spends credits in proportion to the AI work it takes: the tokens in the prompt and in the response. The Credit rates card on the Credits page shows the rates. Your database, auth, storage, realtime and functions don’t use Verament credits; they have their own plan limits.

A Verament build is charged in two parts, and you see the first before the second starts:

  1. Planning is charged when it runs. The plan card shows that charge, the files Verament will write, the most the whole build can cost (planning included) and your balance.
  2. The build is charged only after you confirm the plan, for the batches that actually run, and never above the maximum the card showed.

Canceling a plan, or letting it expire, costs nothing beyond the planning. A request your plan doesn’t include is refused without a charge, and the question Verament asks when a request is unclear is free. API and SDK callers can send autoConfirm: { maxCredits } to build in one call when the maximum fits that ceiling.

Choosing a deeper effort or a higher engine uses more credits; see Tiers and effort.

Every plan includes credits each month:

PlanVerament credits
Free250
Starter1.5K
Pro6K
Agency20K
Studio+40K
EnterpriseCustom

On Free, the credits are unlocked by a free card check: someone in the organization saves a card from the card-check banner in the console, and nothing is charged. A card that has already unlocked another organization’s free credits can be refused. Until the check is done, Verament requests are refused with 402 AI_CARD_CHECK_REQUIRED and a link to the check. Paid plans don’t need it.

On the Credits page, Buy Verament credits offers credit packs, paid by card. Owners, admins and members with the billing role can buy them.

On paid plans, Auto top-up buys a pack for you when your credits run out, up to a monthly cap you set. Choose the pack and the cap on the Credits page.

Your plan’s monthly credits reset at the start of each billing period; unused plan credits don’t carry over. Credits you buy (packs and auto top-ups) do carry over from month to month for as long as your organization exists. Each request spends your plan’s credits first and bought credits after them.

Verament pauses once the period’s plan credits and bought credits are used up, and starts again when you buy a pack, auto top-up buys one, or the next period starts. Running out never affects the rest of your project: data, auth, storage, realtime and functions keep working. The exact rule for each plan is under Limits and overages.

  • Credits shows the credits left and used this period, and every credit transaction (plan credits, purchases, auto top-ups and adjustments), filtered by type and period.
  • Usage & limits shows Verament usage by tier.

With a console access token:

Terminal window
# Usage for the current period
curl https://api.vaif.studio/billing/org/$ORG_ID/usage \
-H "Authorization: Bearer $VAIF_ACCESS_TOKEN"
# Credit transactions
curl https://api.vaif.studio/billing/org/$ORG_ID/credits/transactions \
-H "Authorization: Bearer $VAIF_ACCESS_TOKEN"

To be told before you run low, set a usage alert on the Alerts page; see Plan and payments.