Skip to help content
API, MCP and webhooks

API, MCP, and webhook rate limits

Understand cost-based limits, 429 responses, Retry-After, and retry-safe clients.

Operations have different costs

Reads consume fewer cost points than uploads or mutation-heavy operations. Free accounts receive a useful baseline; paid plans receive higher limits shown in the live developer response headers or documentation.

Handle 429

  1. Stop sending parallel retries.
  2. Read Retry-After when present.
  3. Wait with jitter.
  4. Retry only an idempotent operation or use the same valid request ID.

Webhook delivery is separate

Astral webhook retries do not consume the customer's normal API budget. Endpoint, fan-out, failure, and retry controls are enforced separately to protect the service.

Related guides