budget

Check Claude API rate limit headroom by probing anthropic-ratelimit-unified headers to derive 5-hour and weekly utilization. This cross-account probing returns reset times and allowed or rejected status, enabling headroom-first account rotation to reduce throttling.

Anthropic rate limit headroom is the remaining token capacity within 5-hour and weekly windows. Probe it before starting high-cost workflows or parallel agent scheduling to prevent failed requests, wasted time, and operational throttling.

Monitor cross-account Claude rate limits by using curl to probe messages endpoint headers and jq to parse the response. The process auto-discovers credentials, probes per-account with timeouts, and writes deterministic NDJSON results.

The budget probe handles expired OAuth tokens by automatically warming them via a print trick to avoid 401 failures. On network timeouts, it falls back to cached per-account probe results stored locally while marking entries as stale.

Yes, the rate limit probe targets operational decisions for parallel agent scheduling and lead dispatch timing. It outputs utilization data and allowed or rejected status to help pick accounts with sufficient headroom for token-budget-sensitive workflows.

Cross-account Claude budget probing requires standard command-line dependencies including curl, jq, flock, date, awk, sed, mktemp, and timeout. These tools enable credential discovery, header parsing, caching, and formatted table rendering.