Admin
TextQL Pricing FAQ
Understand TextQL’s Pricing
What are Agent Compute Units (ACUs)?
Agent Compute Units (ACUs) are used to pay for the consumption of AI-powered analytics resources on TextQL. An ACU is a unit of measure that represents the computational resources, AI model usage, and business value delivered.ACU Value Proposition
Unlike traditional compute billing models that charge for infrastructure time, ACUs are designed to align costs with business outcomes:- Outcome-Based Pricing: You pay for delivered insights and completed analyses, not idle time
- Transparent Value: Each ACU represents a specific action, which can be audited later by organization administrator
- Predictable Scaling: ACU consumption scales with your analytical needs, not infrastructure complexity
ACU Usage and Consumption
Agent operations come in different complexity levels and ACUs are charged based on the complexity of the tasks performed. The ACU numbers shown below represent the cost for each complete operation.| Task Category | Operation | ACU Cost |
|---|---|---|
| Ontology | Creating a Metric | 2 |
| Creating a Dimension | 2 | |
| Documenting a Column | 2 | |
| Retrieval | Planning | 5 |
| Search | 15 | |
| Select | 50 | |
| Object Explorer Query | 50 | |
| Metric Explorer Query | 50 | |
| Load CSV | 25 | |
| Analysis | Read Tableau Dashboard | 50 |
| Cleaning (Python) | 20 | |
| Visualize (Python) | 35 | |
| ML Modeling (Python) | 125 | |
| Presentation | App Creation (Streamlit) | 250 |
| Generate Summary | 50 | |
| Generate Recommendations | 100 | |
| Create PDF Report | 250 | |
| Schedule Run | 175 |
Key billing considerations
- ACUs are only consumed when agents perform work. When no tasks are being executed, no ACUs are consumed.
- Each agent task is billed as a discrete unit based on successful completion. Complex operations like Metric Explorer Queries may involve multiple sub-tasks but are billed as a single unit.
- Current ACU allocation and consumption can be analyzed through the TextQL Usage Page, which is accessible by organization admins.
Optimizing ACUs
Excess ACU consumption is mainly caused by unnecessary dataset discovery and search within Threads; the more context you provide as to what you are looking for and what your desired output is, the less likely it is that Ana spends extra effort on your Thread or message. Below are the most effective levers our customers use for reducing ACU usage while still getting answers fast.| Optimization Lever | Why It Helps | How to Apply It |
|---|---|---|
| Reuse agent context instead of starting fresh Threads | A running Thread preserves chat history, intermediate calculations, and cached result sets. Building on that context prevents the agent from re‑discovering tables or regenerating plots it already created. |
|
| Leverage a well‑curated Ontology | Columns, metrics, and dimensions registered in your Ontology steer Ana straight to the right data and filters, cutting exploration time. |
|
| Embed known SQL snippets or table names in Playbooks | If Ana already knows where the data lives, she can skip search → sample → profile cycles. |
|
Frequently Asked Questions
Pricing and Value
Why do some tasks require more ACUs than others?
Why do some tasks require more ACUs than others?
ACU costs reflect the complexity, AI model sophistication, and business value of each operation. More complex tasks that deliver higher business value consume more ACUs.
Are there limits on seats or data sources?
Are there limits on seats or data sources?
No, TextQL provides unlimited seats and data source connections. You pay only for the insights and analyses generated, not for access or connections.
ACU Management
What happens if I run out of ACUs before my period ends?
What happens if I run out of ACUs before my period ends?
TextQL will reach out to help optimize usage and expand your plan as needed. Critical workloads can continue running while contract adjustments are made.
Do unused ACUs roll over?
Do unused ACUs roll over?
Yes, unused ACUs roll over to maximize client success and ensure you only pay for what you use.
Technical Details
Will TextQL increase my data warehouse computing costs?
Will TextQL increase my data warehouse computing costs?
No, TextQL includes built‑in guardrails to prevent excessive warehouse costs. Typically, every $1.00 of TextQL work results in only ~$0.0001 in warehouse computing costs.