Groundcover · Rate Limits

Groundcover Rate Limits

groundcover publishes a single, flat, per-client rate limit for its APIs and applies it independently to each API key. It is NOT tiered — the pricing page differentiates plans on retention, RBAC and support, not on request rate. What groundcover does not publish is the runtime signal: no rate-limit response headers and no exhaustion status code are documented anywhere, so a client cannot detect throttling from the response contract. Replaces the 2026-05-04 scaffold, which carried invented per-tier request quotas.

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

It captures 2 rate-limit definitions, across the all tier, measuring requests_per_second and requests_per_minute.

The profile also includes response codes documented for throttled and note.

Tagged areas include AIOps, Observability, and Rate Limiting.

2 Limits
AIOpsObservabilityRate Limiting

Limits

Per-second request rate api-key
requests_per_second · second
150
Per-minute request rate api-key
requests_per_minute · minute
1000

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/groundcover-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.