Contents
At a glance
- Unit
- Agent Unit (Flex Licensing) or Platform Unit (Unified Pricing), per LLM call
- Flex - premium models
- 2 Agent Units per LLM call
- Flex - standard models
- 1 Agent Unit per LLM call
- Flex - basic models
- 0.8 Agent Units per LLM call
- Unified - premium / standard / basic
- 0.4 / 0.2 / 0.16 Platform Units per LLM call
- Conversion
- 1 Agent Unit = 0.2 Platform Units, consistently at every tier
- Customer-managed models
- 1 Agent Unit or 0.2 Platform Units per agent run, not per call
- Tier spread
- 2.5x from basic to premium within either scheme
- Price per unit
- Not published by UiPath (checked September 2026)
Two units for the same action
UiPath meters agentic automations in one of two currencies depending on which licensing model your contract uses. Under Unified Pricing the currency is Platform Units. Under Flex Licensing it is Agent Units. The work being metered is identical - a call to an LLM by an agent - but the number attached to it is not.
This is the single most confusing thing about UiPath agent costs, and it is the reason a figure quoted by one team is meaningless to another without the licensing model attached. Everything below exists to make the conversion explicit.
The rate tables
From UiPath's agent licensing documentation, verified September 2026.
Unified Pricing - Platform Units per LLM call. Premium models: 0.4 Platform Units (the Agent Rate times two). Standard models: 0.2 Platform Units, which UiPath calls the Agent Rate. Basic models: 0.16 Platform Units (Agent Rate times 0.8). Customer-managed models: 0.2 Platform Units per run.
Flex Licensing - Agent Units per LLM call. Premium models: 2 Agent Units. Standard models: 1 Agent Unit. Basic models: 0.8 Agent Units. Customer-managed models: 1 Agent Unit per run.
The reconciliation nobody publishes
Line the two tables up and the relationship is exact and constant: 1 Agent Unit corresponds to 0.2 Platform Units for the same action. Equivalently, one Platform Unit covers five Agent Units of work.
Check it at every tier. Premium is 2 Agent Units against 0.4 Platform Units - a factor of five. Standard is 1 against 0.2 - five. Basic is 0.8 against 0.16 - five. Customer-managed is 1 against 0.2 - five. The ratio holds everywhere, which means the two schemes are the same meter denominated differently, like quoting a price in dollars or in twenty-cent tokens.
Knowing that ratio is what lets you compare a Flex quote against a Unified quote, or read a colleague's estimate that was built under the other model. Without it, an Agent Unit figure looks five times worse than the Platform Unit figure for identical work, and people conclude that one licensing model is dramatically more expensive when the difference may be entirely in the denomination. It may of course also be in the price per unit - which brings us to the thing that is missing.
The model tier is the real cost lever
Within either scheme, the spread across model tiers is 2.5x from basic to premium: 0.8 to 2 Agent Units, or 0.16 to 0.4 Platform Units. Every call, every time.
So model selection is not a quality decision with a cost footnote - it is the primary cost control on an agentic workload. An agent that routes routine classification to a basic model and reserves a premium model for the genuinely hard turns costs a fraction of one that sends everything to the top tier. This is the same discipline as picking a model per task rather than per project; see tool calling for why an agent that reaches for tools cleanly needs fewer premium-model turns in the first place.
The second lever is call count. Both schemes charge per LLM call, not per agent run - with one exception. Customer-managed models are charged once per agent run regardless of how many LLM calls that run makes, because you are supplying and paying for the model yourself. That exception is structurally important: it converts a variable, unbounded meter into a flat one. A chatty agent that makes fifteen calls per run costs fifteen units on a UiPath-hosted model and one on a customer-managed model. If you already have model capacity, that is a large arbitrage, offset by the token bill moving onto your own provider account.
UiPath also documents that input tokens are measured in 64k increments for hosted models, so very large contexts are not free within a single call. Context management is a cost discipline here, not only a quality one - see context window.
What is not published
No dollar price. Not for an Agent Unit, not for a Platform Unit. UiPath documents the consumption rates precisely and the monetary rate not at all, exactly as it does with the Robot Unit. Both are sold inside platform agreements.
The upside of that pattern is that your consumption model is fully computable from public documentation. Estimate LLM calls per agent run, multiply by the tier rate, multiply by runs per month, and you have your unit demand exactly. Only the last multiplication - units to dollars - needs a sales conversation.
What to ask
Which licensing model are we on, Unified or Flex, and what is the effective price per unit under it. If we switched, does the price per unit move in proportion to the 5:1 denomination difference or not - because that is the only way to tell whether a switch is a real saving or a relabelling. How are Agent Units and Robot Units drawn from the same or separate entitlements. What counts as a premium versus standard versus basic model, and can that classification change under us mid-contract. And what happens at overage.
That last classification question deserves weight. The tier a given model sits in determines a 2.5x cost swing, and a model moving tiers is a price change delivered without a contract amendment. Get the current classification in writing and ask how changes are notified. See vendor lock-in for why a meter you cannot independently verify is a structural risk, and total cost of ownership for what sits outside it.
UiPath Agent Unit FAQ
What is a UiPath Agent Unit?
The consumption unit for agentic automations under UiPath's Flex Licensing model, charged per LLM call: 2 units for premium models, 1 for standard, 0.8 for basic, and 1 per run for customer-managed models.
What is the difference between Agent Units and Platform Units?
They are the same meter in different denominations. Flex Licensing charges in Agent Units, Unified Pricing charges in Platform Units, and one Agent Unit corresponds to 0.2 Platform Units for identical work. The ratio is exactly five to one at every model tier, so an Agent Unit figure looks five times larger than the Platform Unit figure for the same action.
Why does the same UiPath agent action show a different unit cost for different customers?
Because they are on different licensing models. A standard-model LLM call is 1 Agent Unit under Flex Licensing and 0.2 Platform Units under Unified Pricing. Neither figure is comparable to the other until you attach the licensing model, which is why quoted UiPath agent costs are so often misread.
Are UiPath agents billed per run or per LLM call?
Per LLM call for UiPath-hosted models, so a chatty agent making fifteen calls in one run consumes fifteen times the per-call rate. Customer-managed models are the exception and are charged once per agent run regardless of call count, because you are supplying the model yourself.
How much does a UiPath Agent Unit cost?
UiPath does not publish a dollar price for Agent Units or Platform Units. The consumption rates are fully documented, so you can compute your unit demand exactly from public information, but converting that to a bill requires your account agreement.
How do I reduce UiPath agent consumption?
Route to the cheapest model tier that does the job, since basic to premium is a 2.5x spread on every call. Reduce the number of LLM calls per run by giving the agent better tools and clearer instructions. And if you already run your own model capacity, consider a customer-managed model, which is charged once per run rather than per call.
Primary source
UiPath - agents licensing and consumption rates
Checked September 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what uipath agent unit means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
