Agent session budgets
Planned management contract. Use current Gateway guides for deployed behavior.
Planned capability
This page describes a proposed management contract, not a setup procedure. Current request behavior is documented in the Gateway API reference.
Proposed session caps
The planned contract would add spend or token ceilings for an identified agent session. A session identity and its owner would need to be established separately from a person's capture token.
Proposed refusal behavior
A future cap could refuse additional requests in that session. It would not establish that the agent process itself stops. The contract would need to define concurrent requests, in-flight usage, session boundaries, retries and how the cap combines with other applicable policies.
A session cap could bound admitted requests only when the accounting and maximum-cost requirements were met; it would not guarantee a fixed final provider bill from a captured estimate.