Plandex Rate Limits
Machine-readable rate-limit definitions for the Plandex server REST API and the Plandex Cloud commercial surface. The open-source Plandex server does not document fixed HTTP rate limits — operators control throttling by their own deployment configuration. Practical limits are imposed by the upstream model providers (OpenAI, Anthropic, OpenRouter, Google, etc.) used by the configured model pack. The historical Plandex Cloud trial tier capped plans and model responses per plan rather than per-request rates. The hosted service is winding down as of 2025-10-03.
Plandex Rate Limits is the machine-readable rate-limit profile for Plandex on the APIs.io network, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, across the self-hosted, cloud-byo, and cloud-integrated tiers, measuring requests_per_second, concurrent_streams, plans, model_responses_per_plan, and credits_usd_balance.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and 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 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include AI Coding Agent, Developer Tools, CLI, LLM, and Open Source.
limitremainingresetretryAfter
generated, dated 2026-05-29.
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.