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.
Limits
Policies
Sources
- https://docs.myscale.com/en/cluster-management/
- https://myscale.com/pricing/
- https://github.com/myscale/MyScaleDB
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/myscale-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.