Cherre · Rate Limits

Cherre Rate Limits

Cherre's GraphQL API is access-controlled per licensed customer. Usage is governed by the customer's contract - licensed datasets, query volume, row / record egress, and GraphQL query complexity (depth, joins, aggregations, and spatial operations). Specific numeric request, row, and complexity limits are not publicly documented and are set per engagement; they are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring requests, rows, complexity, connections, and records.

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

Tagged areas include Real Estate, Property Intelligence, Data Integration, GraphQL, and Rate Limiting.

5 Limits Throttle: 429
Real EstateProperty IntelligenceData IntegrationGraphQLRate LimitingQuotasThrottling

Limits

Requests Per Interval account
requests
see provider contract
Per-customer request limits set by the licensing agreement.
Rows Per Query query
rows
see provider contract
GraphQL responses are paginated; large extracts use warehouse egress.
Query Complexity query
complexity
see provider contract
Depth, joins, aggregations, and PostGIS spatial operations contribute to cost.
Concurrent Queries account
connections
see provider contract
Concurrency caps may apply per customer/token.
Data Egress account
records
see provider contract
Egress to Snowflake, BigQuery, AWS, or Azure is governed by licensed volume.

Policies

Per-Contract Limits
Limits derive from the customer's dataset license, geography, and volume tier.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 Retry-After responses.
Warehouse Egress for Bulk
Use Cherre's warehouse egress (BigQuery / Snowflake) for large-scale extracts rather than deep paginated GraphQL queries.

Sources