Continue · Rate Limits

Continue Dev Rate Limits

Continue Hub IDE API (api.continue.dev) returns HTTP 429 on quota exhaustion. The free trial enforces per-user chat and autocomplete counts via /ide/free-trial-status. Inference rate limits ultimately depend on the LLM provider the user routes through — Anthropic, OpenAI, Mistral, OpenRouter, Ollama, or the Continue-managed proxy.

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

It captures 4 rate-limit definitions, measuring requests, chat-messages, autocomplete-requests, and requests / tokens.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Developer Tools, Rate Limits, Quotas, and Throttling.

4 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-25.
Written by API Evangelist on 2026-05-25 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AIDeveloper ToolsRate LimitsQuotasThrottling

Limits

Hub IDE API per-user
requests
provider-enforced
api.continue.dev /ide/* endpoints return HTTP 429 when per-user quotas are exceeded. /ide/list-assistant-full-slugs in particular is currently flagged as always returning 429 in the spec.
Free Trial Chat per-user
chat-messages
chatLimit returned by /ide/free-trial-status
Per-user cap on chat messages allowed in Continue's managed free trial.
Free Trial Autocomplete per-user
autocomplete-requests
autocompleteLimit returned by /ide/free-trial-status
Per-user cap on autocomplete requests allowed in Continue's managed free trial.
BYO LLM Provider per-provider
requests / tokens
pass-through
When users bring their own LLM provider, rate limits and concurrency are governed by that provider, not Continue.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses from api.continue.dev.
Free-Trial Polling
IDE extensions and the CLI should poll /ide/free-trial-status to surface remaining chat and autocomplete quota to the user before the cap is hit.

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