Budgets

Budgets define how much compute, token spend, and API cost an entity in matic can consume within a time window. They provide the control surface for preventing resource exhaustion, enforcing cost accountability, and keeping shared capacity available across orgs, projects, teams, and individual agents. This section explains the budget model from top-level allocation rules through estimation, enforcement, live metering, and historical accounting.

Budget Hierarchy

How budgets cascade from org → project → team → agent, and why the most-restrictive scope in the chain always wins. Read more.

Budget Gates

Enforcement checkpoints at dispatch and activation that decide whether work proceeds, gets queued, or triggers human review based on pre-execution cost estimates. Read more.

Bandwidth

An agent's effective remaining capacity for new work, calculated from its budget allocation minus active commitments and upstream constraints. Read more.

Cost Estimation

How matic predicts resource consumption before execution using Work Contract floor and ceiling obligations together with the Agent Runtime Adapter interface. Read more.

Meter

The real-time consumption tracker that records every inference call, tool invocation, and compute event against the applicable scope hierarchy. Read more.

Ledger

The immutable, append-only historical record of all resource consumption: the authoritative source for billing, audit, and capacity planning. Read more.

Period Windows

Configurable time boundaries such as daily, weekly, and monthly windows that define when budget allocations reset and meter state rolls over. Read more.