Plandex · Rate Limits

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, conforming to the API Commons Rate Limits specification.

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.

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.

5 Limits Throttle: 429 Quota: 429
AI Coding AgentDeveloper ToolsCLILLMOpen SourceRate LimitingQuotas

Limits

Self-Hosted Default operator-controlled
requests_per_second · second
-1
The open-source Plandex server does not enforce a fixed request rate. Operators may put it behind any reverse proxy (nginx, Caddy, Cloud Run) to apply per-IP or per-token throttling. The effective ceiling is set by the upstream model provider's TPM/RPM rate limits on the configured API keys.
Streaming Connections Per Plan plan
concurrent_streams · second
1
Only one in-progress streaming run (tell/build/connect) is supported per plan branch at a time; subsequent calls reconnect to the active stream.
Plandex Cloud — BYO Trial Plans account
plans · trial
10
Historical; Plandex Cloud no longer accepts new users.
Plandex Cloud — BYO Trial Responses Per Plan plan
model_responses_per_plan · trial
20
Historical; Plandex Cloud no longer accepts new users.
Plandex Cloud — Integrated Credit Balance account
credits_usd_balance · continuous
-1
Throughput effectively gated by the user's Plandex credit balance and configured monthly budget rather than per-request quotas. Historical; Plandex Cloud no longer accepts new users.

Policies

Backoff Strategy
The Plandex CLI implements client-side retries with exponential backoff for transient upstream-provider failures and honors Retry-After when surfaced by the upstream provider. OpenRouter is used as a failover route when other configured providers error.
Streaming Reconnect
Clients reconnect to in-progress plan runs via PATCH /plans/{planId}/{branch}/connect. The server is designed to be resilient to brief client disconnects during long-running coding tasks.
Operator Throttling
Self-hosting operators are responsible for any rate-limiting they wish to enforce in front of the Plandex server (e.g., per-IP, per-token, per-org).
Concurrency Per Plan
Only one streaming run per plan branch is active at any time; CLI flags like --bg run additional plans in the background under separate streams.

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/plandex-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.