Reccobeats Rate Limits
ReccoBeats enforces rate limits to ensure fair usage and prevent abuse, but the exact numeric thresholds are configured internally and are not published. When a client exceeds the limit, the API responds with HTTP 429 Too Many Requests and includes a Retry-After header indicating how long to wait before retrying. In addition, the audio-file analysis endpoint enforces hard input constraints: uploads are capped at 5 MB and only the first 30 seconds of audio are analyzed, with a recommended 44,100 Hz sampling rate.
Reccobeats Rate Limits is the machine-readable rate-limit profile for ReccoBeats on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, bytes, and seconds.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Music, Recommendations, Audio Features, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://reccobeats.com/docs/documentation/rate-limiting
- https://reccobeats.com/docs/documentation/introduction
- https://reccobeats.com/docs/documentation/Analysis/audio-features-extraction
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/reccobeats-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.