Chartmetric · Rate Limits

Chartmetric Rate Limits

Chartmetric enforces per-account request-rate limits on its REST API expressed as requests per second (RPS). Entry-level Developer API access is reported at 1 request per second, with higher ceilings (up to ~25 requests per second documented) available under scaled and enterprise agreements. Access tokens are short-lived (1 hour) and must be refreshed via POST /api/token; the same access token should be reused across calls until it expires rather than minted per request. Specific per-account values are not reconciled in this artifact.

Chartmetric Rate Limits is the machine-readable rate-limit profile for Chartmetric on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and seconds.

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 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Music, Analytics, Artist Intelligence, Streaming, and Charts.

3 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
MusicAnalyticsArtist IntelligenceStreamingChartsRate LimitingQuotasThrottling

Limits

Requests Per Second (entry) account
requests
1
Reported entry-level Developer API rate; varies by plan.
Requests Per Second (scaled) account
requests
25
Documented upper rate for scaled / enterprise access; negotiated.
Access Token Lifetime account
seconds
3600
Access tokens expire after 1 hour; refresh via POST /api/token and reuse until expiry.

Policies

Tiered Limits
Request-rate ceilings increase from entry (1 RPS) to scaled / enterprise (up to ~25 RPS) under negotiated agreements.
Token Reuse
Mint one access token from the refresh token and reuse it across requests until it expires; do not request a new token per call.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses and honor any Retry-After header.

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