Hexr Cloud bills by operation rather than by compute time. Every action your agent takes — invoking a tool, calling an LLM, sending an A2A message — consumes a small number of Hexr Compute Units (HCU). This page explains the cost of each operation and how to monitor your balance and usage history.Documentation Index
Fetch the complete documentation index at: https://docs.hexr.dev/llms.txt
Use this file to discover all available pages before exploring further.
HCU cost table
| Event | HCU cost | Description |
|---|---|---|
agent.invocation | 0.10 | Each time an agent is invoked |
tool.call | 0.05 | Each hexr_tool() call |
llm.call | 0.15 | Each hexr_llm() call |
a2a.message | 0.05 | Each A2A message sent |
sandbox.exec | 0.10 | Each sandbox code execution |
browser.browse | 0.10 | Each browser action |
vault.get | 0.01 | Each secret retrieval |
vault.put | 0.01 | Each secret store |
guard.scan | 0.02 | Each LLM Guard scan |
Example: estimating usage
An agent that invokes once, makes 5 tool calls, makes 3 LLM calls, and sends 2 A2A messages consumes:| Operation | Count | HCU per op | Subtotal |
|---|---|---|---|
agent.invocation | 1 | 0.10 | 0.10 |
tool.call | 5 | 0.05 | 0.25 |
llm.call | 3 | 0.15 | 0.45 |
a2a.message | 2 | 0.05 | 0.10 |
| Total | 0.90 HCU |
Check your balance
Usage history
The Dashboard gives you a detailed breakdown of HCU consumption:- Daily HCU consumption — graph of usage over time
- Per-agent breakdown — table showing which agents consumed the most HCU
- Per-event-type distribution — breakdown by operation type
- Export to CSV — download usage data for accounting or cost allocation