Transactional Billing, a charging model that packages an agentic solution run into a tiered transaction cost as an alternative to per-component pricing.

Transactional Billing is a platform charging model for solutions that you or your partners build. As an alternative to being billed for each component your solution uses, such as each page processed through IXP, each LLM call performed by agents, or each executed GenAI activity, you can now choose Transactional Billing for a single, tiered charge per transaction: a fully loaded transaction (FLT). Component-based pricing remains available in parallel: a solution runs under either Transactional Billing or component pricing, never both at the same time.

Transactional Billing applies to agentic solutions orchestrated by Maestro. It prices the work that a whole solution run consumes across products, rather than metering Maestro itself.

Transactional Billing is enabled per folder, from the tenant that contains the folder. Enablement is available to organization administrators and license administrators, in organizations on the Unified Pricing licensing plan with Platform Units available. For the procedure, see Enabling Transactional Billing for a folder.

Because eligibility is a folder setting, the same solution can run under Transactional Billing in one folder and under component pricing in another, so consumption can differ by folder even for identical automations.

Eligibility is inherited. If any folder in a folder's parent chain has Transactional Billing enabled, runs in that folder are eligible. When a solution starts a process in one folder and chains into another, the folder of the originating process determines how the whole transaction is charged.

Transactional Billing measures consumption using a universal unit called an AI Step. Each transaction is billed at a tier, determined automatically by how many AI Steps the run consumes.

Agentic transactions come in three sizes. The tier is assigned automatically from the AI Steps the transaction accumulates, so you do not select a size when you build or deploy a solution.

Transactions that consume more than 75 AI Steps start a new billing cycle, as described in Billing cycle behavior.

How many AI Steps an activity consumes depends on its meter, and on whether it runs on a UiPath model or on a model you supply yourself, known as bring your own model (BYOM).

Child rates follow the same behavior as their parent rate. IXP Helix Classifier, for example, is a child of IXP Document Understanding at a fifth of its rate, so it counts as 0.2 AI Steps. For full details on parent and child rates, see licensing.uipath.com.

The following are included at no additional AI Steps:

If a solution run fails and resumes, execution continues from where it stopped. Transactional Billing does not refund AI Steps already consumed. AI Steps consumed during a retry count against the original transaction's tier window, which can move the transaction into a higher tier. A retry does not restart the transaction: it keeps the AI Steps already accumulated, and the entry-level tier is not charged a second time.

When an Industry and Department Solution runs inside a Transactional Billing context, its own billing takes priority for that span of execution. The Transactional Billing meter pauses while that solution runs and resumes once it completes.

Transactional Billing applies to agentic Maestro processes. Robotic process automation (RPA) jobs invoked within an eligible solution folder do not bill under Transactional Billing, even when the folder is enabled for it.

Transactional Billing does not cover:

For general licensing information, see About licensing.