Bounded Vast.ai API Traffic

Overview

Prefer the CLI's built-in 429 retry for ordinary commands and add one orchestration-level call budget around it. For direct REST clients, implement capped backoff because the API does not return standard rate-limit headers.

Prerequisites

• Endpoint and HTTP-method inventory with expected call volume
• Single owner for retry count, polling interval, deadline, and concurrency
• Metrics for calls, 429s, latency, cached hits, and abandoned work

Instructions

Step 1: Map the identity boundary

Group calls by endpoint, method, bearer token, session user, query key, and client IP because each can contribute to the enforced identity.

Step 2: Choose one retry layer