Wasmer · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, measuring requests, gigabytes, hours, and minutes.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include WebAssembly, Wasm, Registry, Edge, and Runtime.

5 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
WebAssemblyWasmRegistryEdgeRuntimeRate LimitingQuotasThrottling

Limits

GraphQL Requests account
requests
see provider documentation
No explicit numeric ceiling documented for the public GraphQL endpoint; abuse protection applies.
Edge Requests (Plan Quota) account
requests
100000 (Hobby) / 1000000 (Pro) per month, then metered
Monthly Edge request allotment per plan; overages billed on Pro, capped on Hobby.
Bandwidth (Plan Quota) account
gigabytes
150 (Hobby) / 1000 (Pro) per month, then metered
Monthly Edge bandwidth allotment per plan.
Active CPU Hours (Plan Quota) account
hours
50 (Hobby) / 200 (Pro) per month, then metered
Monthly Edge compute allotment per plan.
Build Minutes (Plan Quota) account
minutes
500 (Hobby) / 5000 (Pro) per month, then metered
Monthly CI/build allotment per plan.

Policies

Plan-Based Quotas
Effective limits are driven by per-plan Edge resource quotas; Pro overages are billed, Hobby is capped.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor 429 responses on the GraphQL endpoint.

Sources

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/wasmer-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.