Gleap Rate Limits
Gleap enforces rate limits on its REST API to ensure fair usage and platform stability. The identify and track endpoints share a project-level rate limit of 1,000 requests per 60-second window. Exceeding this limit returns an HTTP 429 Too Many Requests response.
Gleap Rate Limits is the machine-readable rate-limit profile for Gleap on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition.
Tagged areas include Customer Feedback, Bug Reporting, In-App Support, Feature Requests, and Roadmaps.
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/gleap-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.