Automation Anywhere credits and volume licences are the consumption side of Automation 360 licensing. Besides user licences, Automation Anywhere sells “volume-based” licences “in bulk depending on your organizational requirements”, split into consumable licences that are used up (pages processed, API calls, recommendations) and limit licences that cap a capability, such as API Task concurrency.[10] On top of these sit Automation credits, “a flexible, volume-based licensing option” for consuming services “at fixed conversion rates without having to buy separate license types for each service”.[1]
Editions
There are two credit types: Automation AI Credits, “For AI Agents and Automation Anywhere provided models”, and Document Automation Credits, “For processing and extracting documents in Automation Anywhere Cloud”. “They are not interchangeable, and each type applies only to its designated services.”[1] Both balances can fall in the same workflow if an AI Agent calls document processing.[1] Catalog proof: AI Credits and Document Automation Credits are separate pools.
Several capabilities need a feature licence before consumption licences can be used. Enterprise Platform is required for conversational automation and AI Guardrails, is one of two routes to higher API Task volumes, and lists AI Agents and AI Evaluations as needing “Automation AI Credits to be purchased”.[7] Automator AI Base covers generative AI tools for developers and “is available only as part of our Cloud-deployed software as a service (SaaS) offering”.[11]
Metrics
Automation AI Credits
Automation AI Credits “are consumption units that measure the licensing usage for Automation Anywhere’s AI-powered services. … When you run out of AI Credits, you can no longer perform those operations until additional credits are purchased, or your grace period applies.”[1]
| Product | Metric | Standard rate (AI Credits) |
|---|---|---|
| Goal-Oriented AI Agent | Per execution | 20 |
| Automation Anywhere hosted AI model | Per 2 interactions | 1 |
| AI Agent Evaluations | Per 1,000 input / output tokens | 0.12 / 0.48 |
| AI Skill Evaluations | Per 1,000 input / output tokens | 0.03 / 0.12 |
Source: Using Automation credits.[1]
AI Agent metering. An AI Agent execution is metered on total GenAI tokens. “A single AI Agent execution includes up to 50,000 tokens. When an execution exceeds this ceiling, additional AI Agent units are charged”: 32,500 tokens is one unit, 52,450 two and 128,900 three. The ceiling applies only to Automation Anywhere provided models outside the AI Agent editor; tokens used by tools the agent calls are excluded, and agents built on BYOL models are not subject to it.[2] Catalog proof: An AI Agent execution includes up to 50,000 tokens; larger runs are charged extra units.
Where credits are charged. In the private workspace, agents on BYOL models consume no AI Credits for execution, while calls to Automation Anywhere provided models consume credits. In the public workspace, “All executions (BYOL or Automation Anywhere provided models) consume Automation AI Credits.” Executions of public agents, including when another process or agent calls them, are charged; test-UI runs, private agents, system-cancelled runs and runs that fail or are cancelled by the user are not.[2] An Enterprise Platform licence “includes a base entitlement of Automation AI credits”.[2] Catalog proof: Private-workspace AI Agents with BYOL models consume no credits; public-workspace runs do.
Document Automation
Document Automation Credits are consumed at 2.5 credits per page for Cloud DA pages through the Cloud Extraction Service and 1 credit per page for Cloud Standard Forms pages.[1] Customers can also buy page or document volumes per engine.[3]
| Licence | Unit | Use |
|---|---|---|
| Document Automation | Pages a year | Automation Anywhere pre-trained models and User-defined document types |
| Standard Forms for Document Automation | Pages a year | Fixed or structured forms |
| Google Document AI for Document Automation | Documents a year (10 pages = 1 document) | Invoices, utility bills, receipts on Google Document AI |
| Document Workspace | Pages | Customers using their own Google Document AI or Standard Forms keys (BYOK) |
| Document Classifier | Pages a year | Classify action decrements per page; training consumes none |
Since v.34, “After the license is consumed or expired, extraction will fail”. Document Automation uses Cloud licensing, so On-Premises deployments need connectivity to the license server.[3] Catalog proof: Document Automation extraction fails once its licence is consumed or expired.
API Task executions
API Tasks need Cloud licensing. “All the Automation 360 cloud customers receive 100 API Task executions per Control Room per year as their free base entitlement”, with two concurrent executions. The API Task Overage SKU and Enterprise Platform each give 50K executions per year and 10 concurrent executions; only Enterprise Platform adds scheduling, code analysis and endpoint access.[4] Executions are counted by runtime: “The license defines the runtime threshold for an API Task execution as 20 seconds.” A 25-second task counts as two executions and a 61-second task as four.[4] The licenses overview adds that when the over-consumption limit is reached, users are notified and “the exhausted licenses will expire within 24 hours”.[10] Catalog proof: API Task executions are counted per 20-second runtime cycle; Every cloud customer gets 100 free API Task executions per Control Room per year.
Conversational automation and guardrails
The Conversational Automation Interactions licence “counts each time someone interacts with the Conversational Automation interface as a billable unit”, deducted from a bundle shared by the whole organization; each user also needs a Conversational Automation Co-Pilot User licence, and Enterprise Platform and v.38 or later are prerequisites.[6] Knowledge bases above the configured 200 MB need additional Conversational Automation Index Memory.[8] AI Guardrails need a consumption SKU counting LLM prompts executed, which “includes both LLM prompts and model responses”.[8] Catalog proof: Conversational automation needs a per-user licence plus a shared interaction bundle.
Process Discovery Data Days
Process Discovery is licensed in Data Days under the Process Discovery Terms. A Data Day is one Active Day of data from one Observer, “the unique combination of machine and username”; “one (1) Data Day is debited for any Active Day in which 200 or more events are collected”. Order Forms may call them Credits. “Data Days must be used within the then-existing subscription term and, if unused, shall expire at the end of such subscription term.”[9] Catalog proof: Process Discovery Data Days count Observer days with 200 or more events and expire at term end.
Counting / floors
Grace. Volume licences (documents, pages, API calls, recommendations) get a grace volume of 10% of the purchased count, configurable through sales, and a grace period of 15 days once the purchase is used up; “The service is terminated when the grace volume is consumed or the grace period ends, whichever comes first.”[5] The same policy applies to credits: “10% more credits and 15 days to consume the 10% grace volume”.[1] Administrators are notified on grace entry, daily for the last seven days and at grace expiry.[5] Catalog proof: Volume licences get 10% grace volume and 15 grace days.
Overage billing. Contractually, use above a volume in the Order Form or Purchase Agreement may be billed “at AAI’s then-current applicable list prices”.[12] Catalog proof: Usage above the ordered volume may be billed at list price.
Visibility. The Licenses page shows credits purchased, used in this and other Control Rooms, remaining and grace usage, with a consumption breakdown by service.[1] Document Automation sends notifications at 80%, 90%, 95%, 99% and 100% consumption.[3]
Virtualization & partitioning
Consumption licences are metered by operations, pages, tokens and execution time, so infrastructure size does not change them. Process Discovery is the exception that counts per machine-and-username Observer.[9]
Cloud / BYOL
Credits and volumes are pooled across a customer’s Control Rooms and shown per Control Room.[1] BYOL applies in two places: customer LLM licences for AI Agents (which avoid AI Credits in the private workspace) and customer keys for Google Document AI or Standard Forms (counted as Document Workspace pages).[2][3] Third-party LLM provider costs still apply to all executions.[2] Several metered features, including AI Agents, API Tasks and Automator AI, are not available On-Premises.[8]
Programs
The License grace policy applies to every volume licence and credit pool. AI features are also subject to the AI Terms in the Product-Specific Terms, under which Automation Anywhere may use Inputs and Outputs to train AI Features only if they are de-identified and aggregated.[9]
Out of scope
IQ Bot page licences, Bot Insight and recommendation volumes for Automator AI are mentioned but not analysed here.