AI and Agentic usage pool for user licenses, a shared monthly limit that all UiPath AI and Agentic products draw from, with top-ups and paid-unit fallback.

The AI and Agentic usage pool replaces the separate, per-product AI entitlements previously attached to each user license with a single monthly limit that all UiPath® AI and Agentic products share. Instead of tracking individual counters for each product, each licensed user has one budget, shown as a percentage of the monthly limit consumed and the date it resets.

The monthly limit is fungible: heavy use of one product and light use of another balance out against the same budget, with no separate per-product limits. When the monthly limit runs low, an administrator can grant additional usage through top-ups, and existing products can continue running on paid units through a fallback mechanism.

Previously, each user license carried its own set of AI entitlements, each measured and reset independently. For example, a user might have had a yearly allotment of Autopilot for Everyone actions, a monthly allotment of Conversational Agent messages, and separate daily limits for Agent Development and ScreenPlay Development large language model (LLM) calls.

With the AI and Agentic usage pool, these separate entitlements are consolidated into one shared monthly limit per user. The following table summarizes the change.

The new AI and Agentic usage pool is granted automatically with every eligible user license, so the change requires no action from administrators or users. Product usage continues uninterrupted. The per-product entitlements that the pool replaces are deprecated and no longer granted, and there is no planned migration of existing balances.

The following products and capabilities consume from the shared AI and Agentic usage pool:

Automation entitlements that are not AI-centric are not part of the pool and keep their existing mechanisms. These include Robot Units (Flex) and Serverless Minutes (Unified Pricing), API calls (Flex only), and Data Service Units.

Usage is drawn from a set of sources in a fixed order. Only one source is active at any time; when it is exhausted, consumption moves to the next source in the chain.

The ordered consumption chain: usage draws from the monthly limit first, then any top-up, then paid units for the existing products.

When the monthly limit resets at the start of a new billing cycle, consumption returns to the monthly limit first. Any unused top-up moves back to reserve and resumes automatically only after the new monthly limit is spent.

Every user license includes a monthly limit shared across all of the products listed above. Users see how much of the current month's limit they have used as a single percentage, together with the reset date. At the start of each billing cycle, the monthly limit refreshes and usage returns to 0%.

The monthly limit is a per-user budget: it is consumable only by the user it belongs to, and administrator top-ups are granted per user. When a user holds more than one license, the highest-tier license governs the monthly limit. Assigning additional licenses to a user does not increase the monthly limit, because only the strongest license applies.

When the monthly limit is spent before the cycle ends, an administrator can grant a top-up. On Unified Pricing, a top-up is a fixed pack of 50 Platform Units (PLTU) drawn from the organization's distribution; on Flex, a top-up is a fixed pack of 500 Agent Units (AGU).

A top-up is a separate limit shown beneath the monthly limit as its own percentage. It is drawn from only after the monthly limit is spent, and it persists across monthly resets: an unused top-up waits in reserve and is used again the next time the monthly limit runs out.

Users cannot grant their own top-ups. A user requests a top-up, and an administrator fulfils it. When a user holds multiple packs, the packs combine into a single top-up percentage rather than a separate meter per pack, so the figure always reflects the total remaining across packs that still have a balance.

Fallback is an automatic safety net for the existing products: Autopilot for Everyone, Conversational Agents, Agent Development, and ScreenPlay Development. When the monthly limit and any top-up are both spent, these products continue running by drawing directly from paid units, without interruption.

Autopilot does not fall back. When the monthly limit and any top-up are spent, it pauses until a top-up is granted or the monthly limit resets.

Fallback draws from the same purchased units that fund top-ups: Platform Units on Unified Pricing, or Agent Units on Flex. If the purchased units are themselves exhausted or expired, there is nothing left to fall back on, and all products pause until more units are added or the monthly limit resets.

Administrators monitor AI and Agentic usage across the organization from Admin > Licenses > Consumables > User usage. The dashboard shows the organization's Platform Units distribution, a paid-unit fallback banner, and a table of all users with their license, monthly usage percentage, top-ups, what each user is currently drawing from (In use), and whether they need a top-up.

From this view, an administrator can grant top-ups from any row, in bulk, or from a user's detail view, and can export the current cycle to CSV. For the full procedure, refer to Granting AI and Agentic usage top-ups.

Two roles apply: a License Administrator can view the data and grant top-ups, while a License Viewer can view the same data and export it but cannot grant top-ups. For details on licensing roles, refer to Licensing roles.

Users view their own AI and Agentic usage under Preferences > Licensing. The Usage page shows the monthly limit as a single percentage with a reset date, an optional Usage by product breakdown, and separate automation usage such as runtime minutes bundled with the license.

Users only ever see percentages, never units or amounts. When the monthly limit is reached, existing products continue on paid units silently, while Autopilot shows as paused until a top-up is granted or the monthly limit resets.