Sleuth Rate Limits
Sleuth's registration API applies endpoint-specific throttling. The custom metric impact registration endpoint is documented as accepting at most one value every 120 seconds per impact source, and rejects timestamps that predate the impact source's creation (no backfilling). Other registration endpoints (deploy, manual change, incident impact) and the GraphQL surface do not publish explicit numeric limits; verify any account-level limits with Sleuth during reconciliation.
Sleuth Rate Limits is the machine-readable rate-limit profile for Sleuth on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests and timestamp.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include DORA, DevOps, Deployment Tracking, Engineering Metrics, and Continuous Delivery.
Limits
Policies
Sources
- https://help.sleuth.io/sleuth-dora/sleuth-api/custom-metric-impact-registration
- https://help.sleuth.io/sleuth-dora/sleuth-api
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/sleuth-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.