Rate limits

Generated OpenAPI already exposes 429 outcomes broadly, but the platform does not yet publish standard rate-limit headers or universal quotas.

Header caveat

Clients should handle 429 with backoff, but docs should not claim standard rate-limit headers until those headers are declared and tested.

Current rules

Topic	Current	Rule
429 responses	346 generated operations include 429.	Treat rate limits as expected integration control flow.
Rate-limit headers	No standard limit, remaining, reset, or retry-after headers are declared globally.	Do not promise header names until OpenAPI declares them.
Credits and quotas	Some workflows may use credits, billing entitlements, or quota errors.	Document 402 and credit dimensions only per approved endpoint.
Polling	Async polling intervals are not globally specified.	Use conservative backoff and endpoint-specific guidance.

Situation	Client behavior
429 response without Retry-After	Use exponential backoff with jitter and lower request concurrency for the affected key, tenant, route, or workflow.
429 during async polling	Slow polling instead of starting duplicate jobs. Preserve the returned job, batch, or resource ID.
Quota or credit exhaustion	Treat as an entitlement or billing control flow. Do not retry in a tight loop.
High-volume batch work	Throttle client-side and prefer endpoint-specific batch or async patterns when they are classified.
Authentication failures	Do not use retry loops to work around 401 or 403 responses. Fix key, scope, feature, or entitlement configuration.

Standard	Status
Limit header	Target only. No global header name is declared.
Remaining header	Target only. No global header name is declared.
Reset or retry-after header	Target only. Do not document a header until OpenAPI and tests prove it.
Rate-limit scope	Target only. Key, tenant, route, user, and external-vendor dimensions are not globally published.
Quota dimensions	Endpoint-specific. Credit, billing, and feature quota behavior requires route-level evidence.