Lastfm Rate Limits
Last.fm enforces rate limits at the originating IP / API key level. The documented guidance is approximately 5 requests per second per originating IP. Sustained excess yields account suspension. The API does not publish standard RFC 9239 RateLimit headers and instead returns numeric Last.fm error codes (notably code 29 — Rate limit exceeded — and code 26 — Suspended API key). Scrobble batches are hard-capped at 50 scrobbles per request.
Lastfm Rate Limits is the machine-readable rate-limit profile for Last.fm on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, across the free and commercial tiers, measuring requests_per_second, scrobbles_per_request, and bytes_total.
The profile also includes response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Music, Scrobbling, Rate Limiting, and Throttling.
Limits
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/lastfm-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.