Ac API Limit Operations

Operating an application on metered or rate-limited third-party AI APIs without being broken by them: the provider's limit contract and which dimension binds, client-side request budgeting and queues, the degradation ladder that keeps serving when the API cannot, fallback chains across providers, key pools for deployments entitled to them, and metering reconciled against the bill. It treats the provider's limit as a system input to be engineered around; it never recommends a provider and never abuses a limit regime. Use when asking "429 handling", "rate limit strategy", "API quota management", "fallback provider chain", "API key rotation", "degradation ladder", "backpressure to callers", "throttle my own callers". Not for prompt packing to reduce request count (ac-single-request-value), not for retry budgets and circuit breakers across generic dependencies (ac-resilience-budgets), not for provider SDK mechanics like auth and streaming (ac-llm-api-integration).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit c885b48e25

Frequently asked questions

npx get-skill add jiayaoqijia/ac-api-limit-operations