Token usage
Advisory model-token meter for BYOK spend estimates — dashboard, CLI, and customer MCP. Not compute credits and not fleet usage.
Model tokens vs compute usage
jurniti measures two different things that both say “usage” in casual speech:
| Surface | What it answers | Where |
|---|---|---|
| Token usage | How many model tokens your agents used, and an estimated BYOK cost | Dashboard Token usage, jurniti token-usage, MCP token_usage |
| Fleet usage | How many VMs you have and monthly plan spend (plus credits burn when relevant) | jurniti usage, MCP usage |
| Usage tiers / credits | Prepaid compute hours (On-Demand / Spot) | Usage tiers & credits, jurniti credits |
Token usage is advisory only. jurniti does not resell model tokens or charge you for them. You bring your own keys (BYOK); the meter helps you see spend transparency. Estimates use public list prices and can be partial when a model is unknown.
Not a free tier
Token usage does not unlock free compute. Agents still require a paid plan or prepaid credits — same no free trial / no free tier rule.
Dashboard
- Open Token usage (Fleet sidebar — labeled Usage / Token usage).
- Toggle Session or Week.
- Read totals, then breakdowns by provider, model, harness, and VM.
- On an agent detail page, the same meter appears scoped to that VM.
Session means “since the current run(s) started” (tied to when VMs entered running). Week is the UTC calendar week.
CLI
Requires the CLI and jurniti login (or JURNITI_API_KEY).
# Fleet-wide (default window: session)
jurniti token-usage
# This UTC week
jurniti token-usage --window week
# One owned VM
jurniti token-usage --vm <vm-id> --window week
# Raw JSON for scripts / CI
jurniti token-usage --window week --jsonHuman output ends with a reminder that estimates are not a jurniti charge
and are distinct from jurniti usage (fleet / MRR).
Full verb list: CLI reference.
MCP (your agent)
Mount the customer server (not operator MCP):
claude mcp add jurniti -- jurniti mcp| Tool | CLI equivalent | Notes |
|---|---|---|
token_usage | jurniti token-usage | Optional window: session (default) or week |
vm_token_usage | jurniti token-usage --vm | Required id (VM); same windows |
Same account and key as the CLI. Use after vm_run when you want cost
transparency without opening the browser.
See also MCP.
When data is empty
- No events yet for the window → totals stay zero /
data_availablefalse. - Not every harness reports token telemetry the same way; empty is normal until the guest meter has samples.
has_partial_costmeans some rows lack a price table entry — token counts still show; $ may be incomplete.
Related
- Dashboard — where the UI meter lives
- Usage tiers & credits — compute billing, not model tokens
- CLI reference — full verb tree
- MCP — agent tools including
token_usage
Usage tiers & credits
Pay per hour from prepaid credits instead of a flat monthly plan — On-Demand and Spot for bursty, part-time agents. Dashboard or CLI.
Swarm — many agents, one command
Fan out dozens of agent microVMs on prepaid Spot credits, dispatch a task to the whole swarm, and collect every result — setup, dispatch, collect.