Transactional Billing

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 available to organizations on the Unified Pricing model, and requires an entitlement that is granted with your plan. Transactions are charged against your Platform Units. For general Platform Units information, see Unified Pricing: Licensing plan framework.

资格条件

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.

备注：

Enabling or disabling Transactional Billing for a folder takes effect immediately, and controls which future runs are eligible. Solutions already deployed in the folder do not need to be upgraded or redeployed for the change to apply.

How consumption is measured

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.

Transaction sizes

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.

层级	Transaction size
小	Up to 10 AI Steps
中	11 to 30 AI Steps
大	31 to 75 AI Steps

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

AI Step conversions

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).

Product / capability	Meter	AI Step conversion (UiPath models)	BYOM Meter	AI Step conversion (BYOM)
IXP Document Understanding	每页	1 AI Step / page	每页	0.7 AI Steps / page
IXP Communications Mining	Per message	1 AI Step / message	Per message	0.7 AI Steps / message
IXP Generative Extraction	每页	1 AI Step / page	每页	0.7 AI Steps / page
Agent Execution	每次调用 LLM	1 AI Step / LLM call	Per Agent Execution	1 AI Step / Agent Execution
Coded Agents (BYOA)	每次调用 LLM	1 AI Step / LLM call	Per Agent Execution	1 AI Step / Agent Execution
GenAI Activities	Per request / activity	1 AI Step / activity	Per request / activity	0.7 AI Steps / activity
上下文锚定 (DeepRAG)	Per query	1 AI Step / query	Per query	0.7 AI Steps / query
语义 活动	Per activity	0.5 AI Steps / activity	Per activity	Free - not counted as an AI Step
ScreenPlay	Per run	1 AI Step / run (requires ScreenPlay add-on)	Per run	Free - not counted as an AI Step

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:

• Maestro process-instance, case, and decision-table execution
• Basic Context Grounding retrieval
• API Automation, up to 1,000 executed Integration Service activities per transaction. Activities beyond the cap count as 1 AI Step per 100 activities.

Billing cycle behavior

1. The first billable event in a transaction is charged at the Small tier, even if that event alone contributes 0 AI Steps.
2. Subsequent events within the same transaction accumulate AI Steps.
3. If accumulated AI Steps cross into a higher tier, only the incremental cost for that tier is charged.
4. If consumption exceeds the Large ceiling of 75 AI Steps, the transaction starts a new billing cycle at the Small tier, carrying over the accumulated AI Steps.

Retry and failure handling

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.

What's excluded from Transactional Billing

Transactional Billing does not cover:

• Robots and Users: a solution can invoke a robot, but the robot must be licensed separately
• AI Center, including AI Center model hosting
• Process Mining
• Automation Cloud Robot virtual machines (ACR-VM)
• 外部应用程序
• Autopilot for Everyone and Conversational Agents
• Healing Agent and App Test Healing Agent
• Context Grounding ingestion and BatchTransform queries (basic search and retrieval is included)

For general licensing information, see About licensing.