Selected activity vs. always using the large model
Activity over time — energy metered vs. always-large baseline
Cache & advisory — zero-quality-risk savings, ahead of routing in the stack
Sessions — an agent run = one session
By model & tier
Provider connection
The model provider Joule calls on your behalf. Your key is verified with your provider, then stored encrypted — it is never written to logs and never sent back to your browser.
Models & region
Which models this workspace routes between, what they cost, and which electricity grid its carbon is estimated against. Leave a field on “Use deployment default” to inherit.
Prices are US dollars per million tokens, as published by your provider. Confirm them and your spend is measured at your own rates. Until you do, cost is modelled — a reference figure, not your bill. Carbon is an estimate either way: the grid intensity of your provider’s inference region × estimated energy. That region is where the electricity is actually consumed — not where you are — and unless you set it yourself it is inferred or assumed, never observed.
Instance settings
Service status
API keys
Your app authenticates with these. Rotating issues a new key and stops the old one immediately.
Plan & data
Danger zone
Permanently deletes this workspace's request history, savings totals and reports. This can't be undone, and affects only your workspace.