Usage and Budgets

Track Managed Research spend, budget caps, and hard-stop behavior.

Managed Research exposes usage and budget state through MCP, Python, and the UI.

Usage reads

Use usage reads to inspect month-to-date totals, recent totals, per-run spend, and budget state.

MCP tools:

• smr_get_usage
• smr_get_project_status
• smr_list_runs

Budget controls

Budgets can stop the current run or block new runs.

Limit	Behavior
run_usd_cents	Stops the current run and marks the stop reason as budget exhausted.
monthly_usd_cents	Blocks additional run triggers after the cap is reached.
timebox_seconds	Stops a run on timeout even if budget remains.

Provider usage

Provider bindings and model choices influence usage. Public examples use:

providers=[{"provider": "openrouter"}]

Backend preflight remains authoritative for provider availability, credentials, and budget blockers.

Cost visibility

Evidence and usage should be read together. A useful run handoff includes:

• final state and stop reason
• task and actor counts
• artifact manifest
• report or PR summary
• provider/model choices
• usage and budget status