Dify Rate Limits
Dify's published limits. Two independent mechanisms exist and they behave differently: a workspace-wide Knowledge Request rate limit measured per minute, and a plan-level API request quota measured per month on the free tier only. Neither is signalled with RateLimit-* response headers — Dify documents no rate-limit headers at all, so a client can only discover exhaustion from the status code and error code. This file replaces a 2026-05-04 scaffold whose headers and numbers were invented.
Dify Rate Limits is the machine-readable rate-limit profile for Dify on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, across the Sandbox, Professional, Team, and Professional, Team tiers, measuring knowledge_requests and api_requests.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled, quotaExceeded, and planLimitOnKnowledgeWrites.
Tagged areas include Artificial Intelligence, LLMOps, Backend-as-a-Service, Agents, and Workflows.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.