Portkey · Rate Limits

Portkey Rate Limits

Portkey is an LLM gateway whose runtime quotas are dominated by the upstream provider being proxied (OpenAI, Anthropic, Bedrock, etc.); Portkey itself exposes plan-bound caps on recorded logs (10k/month on Developer, 100k/month on Production with overage to 3M, 10M+ on Enterprise) rather than per-second request throttling. Enterprise customers can configure granular budget and rate limits per virtual key and workspace. Concrete numeric request-per-second ceilings are not published on the public docs site at the time of writing.

Portkey Rate Limits is the machine-readable rate-limit profile for Portkey on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests_per_month and varies.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include AI Gateways, Governance, Observability, and Rate Limiting.

5 Limits Throttle: 429 Quota: 429
AI GatewaysGovernanceObservabilityRate Limiting

Limits

Developer plan recorded logs account
requests_per_month · month
10000
Logs beyond cap are not recorded but requests still pass through.
Production plan recorded logs (included) account
requests_per_month · month
100000
$9 per additional 100k requests up to 3M then contact sales.
Production plan upper ceiling account
requests_per_month · month
3000000
Beyond 3M requests, account is moved to Enterprise discussion.
Enterprise per-virtual-key rate limit virtual-key
varies
configurable per contract
Enterprise admins can configure granular rate limits and budgets per virtual key, workspace, or service account.
Upstream provider throttling upstream
varies
governed by the proxied LLM provider (OpenAI, Anthropic, Bedrock, etc.)
Portkey passes through 429 responses from upstream LLM providers along with their Retry-After signaling.

Policies

Cap-and-drop logging
When recorded log quota is exceeded on Developer or Production tiers, requests still succeed but log records beyond the cap are dropped.
Pass-through throttling
When the upstream LLM provider throttles, Portkey returns the upstream 429 with whatever Retry-After header the provider supplied.
Granular enterprise limits
Enterprise tenants can scope budget and rate limits per virtual key, workspace, or environment for chargeback and blast-radius control.
Backoff
Clients should implement exponential backoff with jitter on 429 and 5xx responses.

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/portkey-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 email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.