AI credits
AI credits are required to use AI-powered features in Uniform, including Scout, AI Quick edits, and MCP Server create/search operations. Understanding how credits work helps you manage your team's AI usage effectively.
Overview#
AI credits are allocated monthly at the team level and shared across all projects and users within your team. The allocation is based on the team's active production projects or the credits defined in your team's subscription.
How AI credits work#
AI Credit allocation#
- Credits are assigned monthly to your team and expire at the end of each month—unused credits do not carry over.
- When your team's credits are exhausted, AI capabilities will be disabled until the next monthly allocation or a manual top-up.
Monitoring your balance#
You can monitor your team's current monthly usage and remaining credits on your team's subscription page or on the team dashboard.

Click the icon next to the credit count to see when credits reset, open a usage breakdown, or request more credits.

View usage breakdown opens a monthly usage report. The chart shows up to six months of actual usage. When there is enough history, it also predicts usage for the remainder of the current month and next month. Select a past or current month to see credits used by user — including automations that consume AI credits — and by project.

Predicted usage#
If there is sufficient usage history, the chart estimates how many credits your team is likely to use for the rest of this month and for next month:
- Solid bars are credits already used.
- Hatched segments are predicted usage.
- Trend shows a recency-weighted average of actual monthly usage. The legend indicates the trend direction.
- Limit is your team's current monthly allocation. It may not be visible in the chart, but you can hover over the legend to see your current allocation.
The user and project lists always show actual usage.
Predictions are for planning only
Predicted usage does not change your credit balance or monthly allocation. Estimates are based on recent usage and may be incorrect.
How predicted usage is calculated
- Trendline: A recency-weighted average of monthly totals.
- Trend direction: A linear regression of the trendline
- Predictions: The recency-weighted averages are applied to the number of days left in the current month and number of days in the next month.
Credit usage#
Credits are consumed whenever you use Uniform features powered by AI, including:
- Scout chats: Chats with Scout use the most credits because Scout processes your project's context and Uniform concepts. To save credits, keep your chats short and focused. The amount of credits used depends on the length and complexity of the chat.
- AI Quick edits: Quick edits are made at the parameter level (for components) or field level (for entries), and usually use a small number of credits. More complex edits, like those involving advanced parameter types or larger changes, may use more credits.
- MCP Server operations: Create, edit, and search operations for compositions, entries, and patterns performed through the MCP Server require a similar amount of AI credits as content edits through AI Quick edits.
- Automations that use AI: A Scout automation run consumes credits at the same rate as a Scout chat, and so does a code automation that calls Scout. Because automations run unattended, use trigger filters so they only run when they are needed.
Out of credits?
When your team's credits are exhausted, AI capabilities will be disabled until the next monthly allocation or a manual top-up. Plan accordingly to maintain access to AI features.
Requesting additional credits#
If needed, credits can be manually replenished by Uniform to ensure uninterrupted access to AI features. Reach out to your Account Representative from Uniform to request additional credits, or use this form. Get more credits in the credits popover on the team dashboard opens the same form.