Segments.ai · Rate Limits

Segments Ai Rate Limits

The Segments.ai REST API is authenticated with an account API key sent in the Authorization header (APIKey scheme). Segments.ai does not publish explicit numeric per-key rate limits for the REST API; the platform is sold on annual labeling-hour usage rather than per-request quotas. Clients should still expect throttling on bursty traffic and handle HTTP 429 responses. The Python SDK paginates large list operations (samples, releases, workunits) rather than returning unbounded result sets. Specific request-per-minute values are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests, results, and uploads.

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

Tagged areas include Data Labeling, Computer Vision, Point Cloud, Annotation, and Machine Learning.

3 Limits Throttle: 429
Data LabelingComputer VisionPoint CloudAnnotationMachine LearningRate LimitingQuotasThrottling

Limits

REST Requests api-key
requests
see provider documentation
No public numeric per-key request rate limit is documented; expect throttling on bursty traffic.
Sample / Release Pagination api-key
results
paginated
List endpoints (samples, releases, workunits) are paginated; iterate pages rather than expecting unbounded responses.
Asset Upload api-key
uploads
see provider documentation
Asset uploads go to Segments.ai-managed storage; large or bulk uploads may be throttled.

Policies

Usage-Based Subscription
Platform usage is governed by the annual labeling-hour subscription tier rather than per-request API quotas.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources