Sleuth · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, measuring requests and timestamp.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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.

5 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
DORADevOpsDeployment TrackingEngineering MetricsContinuous DeliveryRate LimitingQuotasThrottling

Limits

Custom Metric Impact Cadence impact_source
requests
1 per 120 seconds
At most one metric value may be registered every 120 seconds per impact source.
Impact Backfill Restriction impact_source
timestamp
no dates before impact source creation
Registered dates may not predate the creation of the impact source.
Deploy Registration account
requests
see provider documentation
No explicit numeric limit published for deploy registration.
Manual Change Registration account
requests
see provider documentation
No explicit numeric limit published for manual change registration.
GraphQL API account
requests
see provider documentation
GraphQL surface is under active development; limits not published.

Policies

Per-Source Throttle
Custom metric impact values are capped to one every 120 seconds per source.
Backoff Strategy
Clients should honor 429 responses and implement exponential backoff with jitter.

Sources

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/sleuth-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.