emem · Rate Limits

Emem Dev Rate Limits

Published limits for the hosted responder. Reads are throttled per IP; writes per attester key. The two provider documents disagree on the per-IP read figure: SECURITY.md (2026-08-24) states 600 req/min sustained with a 120 burst, the older terms of service (2026-07-31) state 60 req/min with a 120 burst; both are recorded with their source. Exhaustion returns HTTP 429 with a Retry-After header and the emem.error.v1 body code rate_limited (details.retry_after_s; MCP JSON-RPC error -23). No RateLimit-* / X-RateLimit-* headers were observed on successful responses (probed GET /v1/grid_info and POST /v1/locate, 2026-09-19); the runtime signal is the 429 itself plus Retry-After.

Emem Dev Rate Limits is the machine-readable rate-limit profile for emem on the APIs.io network, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, measuring requests_per_minute, function_calls, and requests.

Limit state is signalled in the retryAfter, requestId, receipt, and rateLimit response headers, and an exhausted limit returns HTTP 429.

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

Tagged areas include Rate Limiting and Agent Memory.

5 Limits Exhausted: HTTP 429 retryAfterrequestIdreceiptrateLimit
Transcribed from the provider's documentation on 2026-09-19 — github.com/Vortx-AI/emem/blob/main/SECURITY.md.
View Source
Rate LimitingAgent Memory

Limits

Read requests per IP (SECURITY.md) ip
requests_per_minute · minute
600
Retry-After: 1 on exhaustion; tunable on self-hosted nodes via EMEM_RATE_LIMIT_RPS / EMEM_RATE_LIMIT_BURST.
Read requests per IP (terms of service) ip
requests_per_minute · minute
60
Older figure from terms section 3; SECURITY.md is dated later and is the hardening table the provider maintains.
Write requests per attester key attester
requests_per_minute · minute
240
HTTP 429 code=rate_limited with details.retry_after_s; the write is only slowed, never lost. Described by the provider as a backstop, not a quota.
Compute quota per attester (derivation functions) attester
function_calls · unspecified
Exhaustion surfaces as compute_quota_exceeded (MCP -22); the figure is not published.
Backfill fetches per IP ip
requests · unspecified
emem_backfill is rate-limited per IP to protect upstream open-data providers; the figure is not published. Bulk historical processing is directed to a self-hosted responder.

Policies

Slow, never drop
The write limiter delays rather than discards; the provider states normal agent use never reaches it.
Self-host for bulk
Production and bulk-historical workloads are directed to a self-hosted responder; the hosted instance carries no SLA.

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/emem-dev-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.