swarm-rate-limits-agent

You can audit API rate limits and throttling rules without modifying production code by running a read-only agent that analyzes RPCs, public routes, and external provider calls to surface misconfigurations and bottlenecks.

Race conditions in API key rate limiting are caused by non-atomic limit increments during validation processes, which a read-only audit can detect by analyzing RPCs like validate_and_increment_api_key to identify risky boundaries.

You can check outbound provider quotas for external API calls to OpenAI and Anthropic by running an audit agent that monitors external provider paths to ensure compliance and detect missing backoff strategies.

Yes, the rate limit audit works with inbound public endpoints and file uploads by sweeping these paths to identify brute-force entry points, endpoint bottlenecks, and potential 429 hotspots for remediation.

You need an audit to detect non-atomic boundaries in API throttling configurations because these hidden flaws cause race conditions and allow quota bypasses, which a read-only agent identifies by analyzing validation RPCs without disrupting system behavior.