Route with conditions
Use conditional routing to choose a path based on your gateway configuration.
AI gateway
Use a unified API with conditional routing, provider and model fallbacks, caching and guardrails.
Sources reviewed . Documentation review; not a performance benchmark or runtime test.
Use conditional routing to choose a path based on your gateway configuration.
Combine fallbacks and load balancing with request controls.
Review caching and guardrails alongside routing, rather than evaluating the gateway only on model choice.
Review the configuration and deployment options that apply to your team's governance requirements.
Compare successful responses, latency and the total bill, including retries and fallbacks. Verify streaming, tool calls and structured output on the routes you plan to use. These are evaluation steps, not claims that every feature is supported.
Check model-provider incidents →Model rates, platform fees, credits and eligibility can change. Check the publisher’s current terms before choosing a route. Our calculator estimates model token costs; it does not quote a negotiated Portkey bill.
Check Portkey documentation ↗Downloads include automated installs and repeat downloads. They do not measure unique users, hosted requests or market share.
npm · Client SDK
745,816 downloads in 28 days
2026-09-29 to 2026-10-26
+7.1% versus the previous 28 days
Previous: 696,586 downloads, 2026-09-01 to 2026-09-28.
Retrieved 2026-10-27. This is a saved snapshot, not a live count.
Selected by product type and shared routing capabilities.
Access models through one API and control which inference providers serve a request. Provider preferences and fallbacks help manage availability.
Run a proxy or use a Python router to distribute requests across model deployments, with load balancing, retries, cooldowns and fallbacks.
Route requests across providers and fallback models with visibility into routing attempts, latency, token usage and cost.