MyScale · Rate Limits

Myscale Rate Limits

MyScale does not expose token-based per-second API rate limits like a typical REST API. Because the interface is SQL executed over the ClickHouse HTTP interface against a provisioned cluster, throughput is bounded by the cluster pod size, replica count, and ClickHouse engine settings (concurrent queries, memory, and connection limits) rather than by a published RPM/TPM quota. The free Development tier additionally caps capacity (~5M 768-dim vectors, single cluster) and terminates the cluster after inactivity. Specific concurrency and quota values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring queries, vectors, and idle_time.

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

Tagged areas include Vector Database, SQL, ClickHouse, Vector Search, and Rate Limiting.

4 Limits Throttle: 429
Vector DatabaseSQLClickHouseVector SearchRate LimitingQuotasThrottling

Limits

Cluster Concurrent Queries cluster
queries
see provider documentation
Bounded by ClickHouse max_concurrent_queries and pod size; not a published per-second quota.
Cluster Throughput cluster
queries
scales with pod size / replicas
Effective QPS depends on provisioned pod size and replica count rather than a fixed limit.
Development Tier Vector Capacity account
vectors
~5,000,000 768-dim vectors
Free Development tier capacity ceiling; one cluster only.
Development Tier Inactivity account
idle_time
terminated after inactivity period
Free Development cluster is terminated (data deleted) after a documented inactivity window.

Policies

Capacity Scaling
Raise throughput and capacity by increasing pod size, adding replicas, or upgrading from Development to Standard / Enterprise.
Backoff Strategy
Clients should implement exponential backoff with jitter on transient errors and honor any Retry-After signal.

Sources