Gradient Labs · Rate Limits

Gradient Labs Rate Limits

Gradient Labs does not publish specific numeric rate limits for its HTTP API on its public site or in its open-source SDKs. The API documents that endpoints are idempotent and requests can be safely retried, which implies clients should implement retry-with-backoff behavior. Any account-level throttling and quotas are expected to be governed by the enterprise agreement. Webhook deliveries carry an incrementing sequence_number per conversation so consumers can order events and safely deduplicate on retry.

Gradient Labs Rate Limits is the machine-readable rate-limit profile for Gradient Labs on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and events.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Customer Support, AI Agent, Financial Services, and Rate Limiting.

2 Limits Throttle: 429
AICustomer SupportAI AgentFinancial ServicesRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
No public per-account request rate is published; governed by the enterprise agreement. Endpoints are idempotent and safe to retry.
Webhook Delivery Ordering conversation
events
ordered via sequence_number
Each webhook about a conversation includes an incrementing sequence_number to establish total event order and support safe deduplication on retry.

Policies

Idempotency and Retry
Unless stated otherwise, endpoints are idempotent and requests can be safely retried. Clients should implement exponential backoff with jitter.
Enterprise-Governed Limits
Throughput and quotas are governed by the negotiated enterprise agreement rather than a public self-serve limit.

Sources