Wasabi Rate Limits
Wasabi does not publish hard numerical rate limits for API requests. Instead, Wasabi enforces a free API request policy based on qualitative usage standards. Accounts with validated commercial use cases are generally compliant. Non-validated applications causing inefficient server loads may face restrictions. Egress-to-storage ratio enforcement acts as an implicit throughput constraint.
Wasabi Rate Limits is the machine-readable rate-limit profile for Wasabi on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions.
The profile also includes 2 backoff/retry policies defined.
Tagged areas include Cloud Storage, Object Storage, S3 Compatible, REST API, and Hot Storage.
Limits
Policies
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/wasabi-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.