Kili Technology · Rate Limits

Kili Technology Rate Limits

The Kili Technology GraphQL API governs load primarily through query complexity rather than published per-minute request quotas. Each response carries an x-complexity header reflecting the cost of the executed operation, and large result sets must be paginated using the first (PageSize) and skip arguments. The Python SDK auto-paginates and throttles accordingly. Specific numeric thresholds are not publicly documented and are not reconciled here.

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

It captures 3 rate-limit definitions, measuring complexity, records, and requests.

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

Tagged areas include AI, Data Labeling, Training Data, Annotation, and GraphQL.

3 Limits Throttle: 429
AIData LabelingTraining DataAnnotationGraphQLRate LimitingQuotasThrottling

Limits

Query Complexity request
complexity
see provider documentation
Each GraphQL response returns an x-complexity header; expensive queries may be rejected. Reduce field selection or page size to lower cost.
Page Size (first) request
records
see provider documentation
Queries (projects, assets, labels, issues, users) page with first (PageSize) and skip; very large pages raise complexity.
Account Requests account
requests
see provider documentation
Per-account request limits are not publicly documented; enterprise and self-managed limits are negotiated.

Policies

Pagination
Use first/skip to page large result sets; the Python SDK paginates automatically to stay under complexity limits.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After when present.

Sources