Victoriametrics Rate Limits
VictoriaMetrics is self-hosted (or VictoriaMetrics Cloud as a managed service); there is no managed REST quota in OSS. Operational caps are set via flags on each component (-search.maxConcurrentRequests, -search.maxQueryDuration, -insert.maxQueueDuration, -maxConcurrentInserts, -maxLabelsPerTimeseries, etc.). Enterprise multi-tenancy adds per-tenant cardinality / ingestion / query rate limits enforced at vminsert and vmselect.
Victoriametrics Rate Limits is the machine-readable rate-limit profile for VictoriaMetrics on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring concurrent_requests, ms, concurrent_inserts, active_series, and samples_per_second.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled and busy.
Tagged areas include Database, Time-Series, Monitoring, Open Source, and Prometheus.
Limits
Policies
Sources
- https://docs.victoriametrics.com/Single-server-VictoriaMetrics.html#capacity-planning
- https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html
- https://docs.victoriametrics.com/PerTenantStatistic.html
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/victoriametrics-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.