CAST AI Request-Budget Control

Overview

Treat rate capacity as an endpoint-specific runtime signal, not a single invented requests-per-second number. Bound concurrency, retries, polling, and total work while preserving correct authentication and organization scope.

Prerequisites

• Client path, CAST AI region, organization scope, endpoints, and workload volume
• Current API specification and observed response headers
• Idempotency classification and business deadline for every operation

Instructions

Step 1: Inventory request producers

Use Read and Grep to identify direct API calls, Terraform operations, polling loops, scheduled jobs, retries, pagination, and per-cluster fan-out. Calculate worst-case attempts, not only successful requests.

Step 2: Classify operations