Account usage and limits

Golem reports account usage by UTC calendar month. Enabled monthly compute, memory, durable-storage, and ephemeral-storage amounts are hard caps by default. Exhaustion stops applicable execution until capacity returns. Eligible account owners can explicitly enable paid overage to continue beyond those amounts. Per-agent memory and storage limits constrain allocations independently of monthly policy and billing metering.

Current and monthly usage

Show the current UTC month:

golem account usage show

Show a particular month in YYYY-MM form:

golem account usage show --period 2026-09

The response includes an as-of timestamp and four dimensions:

Storage uses byte-seconds divided by 1024³ × 730 × 3600. Both storage fields come from the shared filesystem meter, separated by durable and ephemeral agent usage. Memory measures allocated linear memory, not process RSS or host memory.

Each dimension also reports whether metering was enabled, disabled, or unknown. A zero with metering enabled means no usage was measured. unknown means no usage producer has reported that meter’s state for the period.

Closed-period history

golem account usage history
golem account usage history --last 12

History returns closed UTC months newest first and defaults to six periods. It is sparse: months without a stored usage record are omitted. Historical rows use the same units and metering states, but do not snapshot historical plan or limit metadata.

Use --account <email> or --account-id <uuid> on usage commands when authorized to inspect another account.

Effective limits and overrides

Show monthly mode, overage eligibility, the four monthly dimensions, and per-agent limits:

golem account limits show

Each enabled monthly dimension shows its plan amount, active administrator grant, resolved monthly amount, usage, remaining capacity, unit, and behavior. In hardLimit mode, its amount is a hard cap. In allowOverage mode, it is an included allowance. Disabled dimensions are labeled disabled rather than reported as ordinary zero usage or unlimited limits.

Mode changes can take up to five minutes to reach running agents. Usage remains eligible for excess billing under an applied allowOverage policy until hardLimit applies. During overlapping refreshes, Registry allocates the included amount by policy revision rather than exact cross-executor consumption order. Changing modes does not reset monthly usage. The UTC month resets usage, but the account’s selected mode persists. Monthly amounts and mode are read-only in the CLI.

The two self-service override dimensions are maximum memory per agent and maximum storage per agent, both in bytes. Maximum storage is disabled when managed filesystem quota enforcement is unavailable. The CLI does not display an internal unlimited storage sentinel as a byte limit.

Set one override per command:

golem account limits set --max-storage-per-agent 10737418240
golem account limits set --max-memory-per-agent 536870912

Use an explicit named flag for each write. Choose values after inspecting limits show: self-service values must be between the plan default and self-service ceiling, inclusive. The service rejects writes for non-configurable dimensions and rejects storage writes when managed quota enforcement is unavailable.

Clear one override per command:

golem account limits unset --max-storage-per-agent
golem account limits unset --max-memory-per-agent

Clearing a self-service override uses the larger of the current plan default and the active administrator grant, when present.

The CLI creates non-expiring self-service overrides. Administrator grants use a separate administrator-token API and can have an expiry. A grant can increase the permitted amount, but never reduce it. Monthly allowances use the larger of the plan amount and the active grant. For per-agent limits, first resolve the valid self-service setting or plan default. Then use the larger of that normal limit and the active grant. For example, a plan allowance of 5 with a grant of 8 permits 8, not 13. Upgrading the plan to 10 permits 10 even while the grant remains active. A temporary grant does not overwrite a persistent self-service choice, and an expired grant becomes inactive before cleanup removes its row. Grants do not create paid-overage consent or enable a disabled resource feature.

Usage, quotas, and operator metering

These concepts are independent:

• Account usage is the monthly, user-facing billing measurement shown by golem account usage.
• Resource limits include monthly hard caps or included overage allowances and the independent per-agent memory and storage limits shown by golem account limits.
• Application quotas are capability-style concurrency or resource controls used by agents. See Quotas.
• Operator metering switches enable monthly accounting, caps, and billing for the matching dimensions. They do not control per-agent memory safety or managed filesystem quotas. See Resource metering.

Self-hosted operators can enforce per-agent memory limits and managed filesystem quotas while all billing meters are disabled. Compute, memory, and filesystem billing meters are independent opt-ins. Filesystem metering enables the two separate monthly storage dimensions. When every billing meter is disabled, monthly policy has no runtime effect.