Logique de mesure et de facturation (Régime Flex)

Lorsque vous utilisez des projets modernes UiPath® Document Understanding^TM , il est essentiel de bien comprendre la consommation des AI Units.

Astuce :

• Pour plus d’informations sur les régimes de licence pour les projets classiques, consultez la page Logique de mesure et de facturation du Guide de l’utilisateur Document Understanding pour les projets classiques.
• Pour suivre votre consommation d’AI Units au niveau de l’organisation et du locataire, consultez les pages du tableau de bord Vue d’ensemble de la consommation d’AI Units.
• Pour suivre la consommation d'AI Units pour les projets Document Understanding et AI Center, vérifiez la page du Tableau de bord de la consommation d'AI Units d'Extraction et traitement intelligents (IXP).

How charging works for modern projects

For Document Understanding modern projects, only one single AI unit is charged per page, regardless of the operations performed at runtime or the number of modern projects extracting data from the same page. The single per-page charge covers:

• Digitization, including OCR
• Extraction
• Classification

This applies to both robotic process automation (RPA) and REST API operations. For full REST API pricing — including how classic-project API calls are charged — see Metering and Charging in the API guide.

Through Document Understanding activity packages

For both DocumentUnderstanding.Activities and IntelligentOCR.Activities, one AI unit is charged per page, regardless of the operations performed (digitization, extraction, or classification).

The one AI unit per-page rule applies only when:

• For DocumentUnderstanding.Activities: a pre-defined generative or modern project classifier or extractor is in use.
• For IntelligentOCR.Activities: a modern project classifier or extractor is in use.

If you use any other classifier or extractor, the respective consumption logic from classic projects is added to the one AI unit per page. For more information, see Mixed projects.

Generative features — Activities 24.12-preview and above

This consumption applies in the following situations:

• Utilisation des activités version 24.12-preview et versions ultérieures avec des projets PredefinedGenerative.
• Utilisation de l’API Document Understanding v1.1 avec les projets PredefinedGenerative.

There are no additional AI units consumed when using Generative Classification and Generative Extraction. Only one single AI unit is charged per page, regardless of the operations performed, including Generative Classification and Generative Extraction.

Remarque :

Using Generative Validation consumes an additional one AI unit for each processed page. This brings the total to two AI units consumed per page when generative validation runs.

Generative features — Activities up to 24.12-preview

This consumption applies in the following situations:

• Utiliser la version d’activités jusqu’à 24.12-aperçu avec le projet Predefined.
• Utiliser l’API Document Understanding v1.0 avec le Predefinedprojet.

In these versions, generative features incur specific charges per operation, as described in the following table.

Table 1. Generative features AI units consumption for activities versions up to 24.12-preview

Fonctionnalité générative	AI Unit consommées
Classifieur génératif	0,2 par opération
Extraction générative	1,2 par opération
Validation générative	1 par opération

Entraînement de modèle

There are no AI units charged when training and serving models. You can train models freely to improve performance, develop new capabilities, and experiment without incurring additional AI units charges.

Mixed projects (modern + classic)

When a project uses both classic and modern experiences, both pricing models apply based on their respective consumption.

The pricing model for classic projects applies in the following circumstances:

• Extraction and classification done using classic projects, regardless of the activity package used (IntelligentOCR or DocumentUnderstanding.Activities).
• Extraction and classification done using the out-of-the-box models included with the pre-defined project, regardless of the activity package used.
• REST API calls against classic-project models — classic per-capability rates apply, not the 1 AI unit per-page rule.

For full classic-project metering — including activity-based rates per OCR engine, classifier, and extractor — see the Document Understanding User Guide for Classic Experience. For classic-project REST API rates specifically, see Metering and Charging in the API guide.