Wasmer Rate Limits
Wasmer does not publish explicit numeric rate limits for the public Registry GraphQL API at registry.wasmer.io/graphql. Practical limits are governed by plan quotas - apps, requests, bandwidth, active CPU hours, provisioned memory, storage, build minutes - enforced per account on Wasmer Edge. The GraphQL endpoint applies standard abuse protection; specific per-account request ceilings are not documented and are not reconciled in this artifact.
Wasmer Rate Limits is the machine-readable rate-limit profile for Wasmer on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, gigabytes, hours, and minutes.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include WebAssembly, Wasm, Registry, Edge, and Runtime.
Limits
Policies
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.