AI usage, credits, and team budgets

AI usage is pay as you go on every agaro plan. Growth and Scale include access to the AI Assistant capability, but they do not include a monthly dollar credit. Usage is funded by the workspace AI credit wallet and governed by workspace and member limits.

#Where to see usage

Open Account Settings → AI Usage to review usage tied to your account. Workspace administrators can open Settings → Developer and AI → Team AI Budgets for the team view and member controls.

Usage can include assistant turns, App Builder generation, automated repair, and other AI backed product functions that record spend through the shared ledger.

#Workspace credits

The subscription area contains the AI credits card. A billing administrator can review wallet balance and available top up controls. The platform records credit grants and consumption in an auditable ledger.

When the prepaid wallet is empty and the configured period ceiling has been reached, a new assistant turn can be refused before the tool loop starts. This prevents a denied budget from partially running business actions.

#Model and effort affect cost

Model providers charge different amounts for input, output, and reasoning. A longer conversation also sends more context. Higher reasoning effort and large code generation can therefore use more credit than a short lookup.

Control cost by:

• Starting a new conversation when old context is no longer relevant
• Asking one bounded question at a time
• Using lower effort for simple work
• Choosing an appropriate model rather than the largest available model by habit
• Reviewing App Builder changes in smaller increments
• Avoiding repeated retries before reading the first error

#Team budgets

Administrators can inspect team AI usage and set supported member limits from the Team AI Budgets section. A limit narrows consumption for that member; it does not expand module or record access.

Budget enforcement and prepaid credit are separate checks. A workspace can have credit remaining while a member limit blocks a request, or a generous member limit while the workspace wallet is unavailable.

#Automatic recharge

Where the billing surface offers automatic recharge, it uses the workspace's saved payment method and the configured threshold and amount. Automatic recharge spends money. Only a billing administrator should enable or change it after reviewing the values.

The credit ledger uses provider payment identifiers to prevent a successful checkout or recharge event from granting the same credit twice.

#MCP billing

MCP is a separate $8 monthly per user add on for eligible Growth and Scale workspaces. Buying an MCP seat does not add AI wallet credit. It grants the seated user's API key access to the MCP and API surface, with that user's permissions.

#Troubleshooting

#The assistant returns payment required

For in app chat, review the AI wallet and budgets. For API or MCP, confirm that the bound actor has an active MCP seat and the workspace subscription is active.

#Usage appears higher than expected

Review the model, effort, conversation length, App Builder activity, and repeated attempts during the period. Ask an administrator to inspect the team usage view before changing limits.

#A top up completed but the balance did not change

Refresh the subscription page and review the credit ledger. Keep the hosted checkout reference and contact support if the signed payment event has not reconciled. Do not repeat the purchase until its status is known.

#A user has credit but cannot use the assistant

Credit does not grant the module. Verify the workspace plan, AI Assistant capability, user app access, and subscription state.