Request limits and retries

Requests are authenticated and rate-limited. A 429 response means the client should back off; follow the returned retry guidance when present. Limits may depend on the account and service configuration, so do not build against a promised fixed quota from the retired docs.

Prepare cohort history once, then reuse its pinned snapshot for comparison refinements. The prepare tool waits briefly for a cold build and returns the snapshot or retryable guidance; it never returns a job id, and no status polling is required. Replaying captured chart data does not require repeatedly fetching the same history.

A 503 access-check failure is temporary service unavailability, not evidence that a subscription has expired. Without current access, the connection and listings still load and a data request returns a neutral in-conversation explanation — not a purchase prompt. See troubleshooting.