Skip to content

UiPath AI Units usage

UiPath contributes AI Units consumption rows by tenant, Orchestrator folder, and automation. The consumption reads need an access token for a dedicated UiPath user, and UiPath documents no request that issues that token; see Consumption API token.

Onboarding scope

This guide covers the read-only uipath connector in the Venturi platform connector package. It reads AI Units consumption and Orchestrator inventory and never starts, stops, or changes robots, jobs, queues, or packages.

Required access

The names below are Venturi capability identifiers, not UiPath OAuth scopes:

Venturi capability Purpose
Insights.Read Read AI Units consumption.
Orchestrator.Tenant.Read Read tenant context.
Orchestrator.Folder.Read Read folder context.
Projects.Read Read automation (process) context.

Do not grant robot, job, queue, package, license allocation, or quota permissions. You never paste the Venturi capability names into UiPath.

Venturi uses two UiPath authorizations, both read-only:

  • AI Units consumption. UiPath publishes consumption through its Consumption API: POST {accessURL}/lease_/api/usage/{organizationId}/tenants/consumption-by-folder, .../consumption-by-process, and .../daily-consumption-by-service. The folder and daily requests take the AI Units consumable code AIU, and the process breakdown returns a quantity for each unit code, from which the connector keeps the AIU quantities. UiPath documents these calls for a user rather than an external-application scope: the by-process breakdown needs only license viewing permission on the tenant, and the organization-wide summary needs an Organization Administrator. Venturi reads the tenant-level breakdowns as a dedicated UiPath user that holds only the read-only License Viewer role at each tenant it monitors, and never calls the organization summary.
  • Orchestrator tenant and folder inventory. A UiPath confidential external application for Venturi, assigned roles with View permissions only at the tenant and folder levels it needs, requests the OR.Default scope so its access follows those roles. The same application can hold the PM.License.Read scope, which reads the organization license summary, including licensed, allocated, and used AI Units. See UiPath’s fine-grained access guide for confidential apps.

Consumption API token

The consumption calls run as the dedicated user, so they need an access token issued to that user. UiPath’s Consumption API reference says to obtain it through Resource Owner Password Credentials (ROPC). The authentication methods guide that the reference links for that step documents Personal Access Tokens, external applications, and API keys but describes no ROPC request. UiPath publishes no Personal Access Token or external-application scope for the Consumption API. UiPath therefore documents no request that issues this token for Venturi to store. Without it, the consumption reads fail open: the connector returns no AI Units consumption rows, the readiness record labels UiPath consumption as a degraded source, and Orchestrator inventory reads continue through the external application.

Consumption granularity

UiPath reports AI Units consumption at the organization, tenant, Orchestrator folder, and automation level (process name or API app ID), and by product, such as Document Understanding, IXP, AI Center, and GenAI Activities. UiPath refreshes AI Units licensing data every four hours and the tenant-level dashboard every 24 hours, so the latest rows can trail real consumption by up to a day. Folder and process attribution starts from mid-April 2026, and some services report consumption at the tenant level only. See UiPath’s AI Units consumption overview and Consumables Center.

Setup

Inventory setup and the consumption prerequisite are separate. Inventory setup connects UiPath through the external application, and its reads do not depend on the consumption token. The consumption prerequisite stays unresolved while UiPath documents no request that issues that token.

Inventory setup

  1. Create a dedicated confidential external application for Venturi with the OR.Default and PM.License.Read application scopes, and assign it view-only roles at the tenant and folder levels above.
  2. Store the application secret as an encrypted credential reference in Settings / Admin / Credentials.
  3. In Venturi, go to Integrations / UiPath and run Test connection.

Consumption prerequisite (unresolved)

The consumption reads need an access token for a dedicated UiPath user, and UiPath documents no request that issues it; see Consumption API token. Until a token for that user is stored, the readiness record labels UiPath consumption as a degraded source and the connector returns no AI Units consumption rows. Inventory setup does not complete this prerequisite. The user and its role are the access that UiPath’s Consumption API reference names for the tenant breakdowns:

  1. Create a dedicated UiPath user for Venturi. As an Org Admin, assign it the License Viewer role at each tenant Venturi monitors, through Manage Access in the Admin Console, and no other role.
  2. The default consumption lookback is 30 days; set VENTURI_UIPATH_LOOKBACK_DAYS to change it. See sync windows and failure behavior.

Verification

For inventory setup:

  • Test connection passes the read-only boundary check: inventory reads succeed, and the application holds no robot, job, queue, or package mutation permission.
  • The connector inventory marks UiPath as read-only.

For the consumption prerequisite:

  • In the UiPath Admin Console, Manage Access shows the dedicated user with only the License Viewer role at each monitored tenant.
  • AI Units consumption rows appear for the expected tenants, folders, and automations only when a consumption token for the dedicated user is stored. Without one, the readiness record labels UiPath consumption as a degraded source.
  • Usage rows carry the source label uipath_insights_api.

Rotation and offboarding

Rotate the application secret through UiPath administration, then update the credential reference in Settings / Admin / Credentials. To offboard, remove the License Viewer role from the dedicated user and delete the external application. Removing the connector stops new UiPath AI Units syncs.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: UiPath AI Units usage
Page: https://docs.venturi.systems/connectors/uipath/