Spreaker Rate Limits
The Spreaker API enforces rate limiting but does not publish exact numeric request-per-minute thresholds. The developer overview states that excessive requests result in temporary IP blacklisting and a 429 Too Many Requests response. Read (GET) requests are generally public and do not require authentication unless documented; all writes (PUT, POST, DELETE) require an OAuth2 Bearer token. List endpoints are paginated - the default page size is 50 items, adjustable up to 100 via the limit parameter, with a next_url property linking to the following page.
Spreaker Rate Limits is the machine-readable rate-limit profile for Spreaker on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and items.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Podcasting, Podcast Hosting, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://developers.spreaker.com/guides/overview/
- https://developers.spreaker.com/guides/authentication/
- https://developers.spreaker.com/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/spreaker-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.