Reference

Limits and quotas

Consolidated overview of every limit on the knowmind platform. Values as of 11 June 2026 — changes are tracked in the changelog.

ScopeLimitSource
Memories, Private plan2,500Plan matrix
Memories, Pro and aboveunlimitedPlan matrix
Memory soft warningfrom 80% of the plan limit (warnAt80 in stats and store responses)Quota gate
API rate limit, Private plan30 requests per minute per tokenPlan matrix
API rate limit, Pro plan60 requests per minute per tokenPlan matrix
API rate limit, Team plan120 requests per minute per tokenPlan matrix
API rate limit, Business plan120 requests per minute per tokenPlan matrix
API rate limit, Enterprise600 requests per minute per tokenPlan matrix
Maximum document size (upload)10 MBMemory service
Maximum memory size (store_memory)100 KBMemory service
Recall — number of hits (k)1 to 25MCP tool schema
Recall — graph hops0 to 3MCP tool schema
Chunk size on uploadabout 500 tokens with 50 tokens overlapRecall pipeline
Embedding dimension1024 (multilingual-e5-large)Recall pipeline
Webhook body size1 MBWebhook worker
Webhook timeout15 secondsWebhook worker
Webhook retries6 attempts (immediate, 1 min, 5 min, 30 min, 2 h, 12 h)Webhook worker
Dead-letter thresholdSubscription disabled after 20 consecutive failuresWebhook worker
Audit log retention, Private30 daysPlan matrix
Audit log retention, Pro90 daysPlan matrix
Audit log retention, Team12 months (365 days)Plan matrix
Audit log retention, Business24 months (730 days)Plan matrix
Audit log retention, Enterprise5 years (1825 days)Plan matrix
OAuth code validity10 minutesOAuth server
Magic link validity24 hoursAuth service
API token formatkmt_ + 43 base64url characters (256 bits of entropy)Token module
Maximum tokens per workspace50 active (more on request for Enterprise)Token module

Behaviour on exceedance

  • Rate limit (429): response carries a Retry-After header in seconds. Clients should wait and retry, ideally with jitter.
  • Memory limit — soft warning from 80%: knowmind_stats and the success responses of store_memory/upload_document carry the fields memoryLimit, memoriesUsed and warnAt80 plus a plain-text hint. The count covers the stored documents/memories of the workspace — NOT the auto-extracted graph nodes.
  • Memory limit reached (402): the write call is rejected; the response carries plan_upgrade_required and indicates the required plan (REST: HTTP 402; MCP: a JSON-RPC error with the same message). Existing content and all read paths (recall, export) stay fully available.
  • Document too large (413): the call is rejected. Split the content and ingest in multiple calls.
  • Webhook dead letter: the delivery is marked dead. After 20 consecutive failures the whole subscription is disabled and must be reactivated manually in the dashboard.

Related