API Task license and consumption model

Learn about the API Task license and execution model

License

The API Task requires cloud-based licensing for functionality. File-based licensing is not currently supported. All the Automation 360 cloud customers receive 100 API Task executions per Control Room as their free base entitlement. The base entitlement also includes two concurrent executions, meaning you can run two API Tasks simultaneously. For higher execution limits and additional concurrency, you must purchase an Enterprise Platform license or an API Task Overage SKU. You can track your base and overage executions in the Automation Anywhere Cloud Service section of Main Group tab of the License page. For information about . The page also displays the consumption data of each Control Room.

The following table shows the details of different licensing tiers for API Tasks:

API Task License tier API Task Execution Pricing Concurrent Executions Scheduling Code Analysis Endpoint Access Other Features
Base License 100/Control Room Free 2 No No No N/A
API Task Overage SKU 50K/year Customer Success Manager (CSM) for more details 10 No No No N/A
Enterprise Platform 50K/year Customer Success Manager (CSM) for more details 10 Yes Yes Yes Enterprise Platform license features

Consumption model

API Tasks follow a time-based consumption pricing model that ensures you pay only for the exact computational resources your automation utilizes. This granular approach offers a fair and transparent billing system that aligns with your automation needs.

  • Time-Based Consumption: You are charged based on the actual time your API Task consumes, rounded up to the nearest minute.
  • Granular Accuracy: The system meticulously tracks the consumption of computational resources for each task, ensuring precise billing. You pay only for the resources your automations truly require, avoiding unnecessary costs.

The license defines the runtime threshold for an API Task execution as 60 seconds. If the runtime for an API Task is less than 60 seconds, the system considers it one execution. If the runtime exceeds 60 seconds, the system considers it two executions. For each 60-second runtime cycle, the execution increments by 1.

Examples:

  • An API Task that runs for 30 seconds is considered 1 execution.
  • An API Task that runs for 1 minute and 23 seconds is considered 2 executions.