Back to AI News
MarkTechPost

Perplexity Launches Orchestrator API for Failover and Model Routing

Perplexity launched the Orchestrator API, a single endpoint serving frontier and open-weight models from multiple providers with automatic same-model failover across deployments. It accepts OpenAI Chat Completions, OpenAI Responses and Anthropic Messages request formats, so most teams only change the API key and base URL. A preview perplexity/auto routing feature uses plain-language route descriptions and falls back to a default model when no route matches or the decision model fails. Requests are billed at the answering model's published rate, and Perplexity says there is no additional platform fee on top of credits.

AI Brief

It gives developers a concrete new option for multi-provider model access, automatic failover and prompt-based routing through one billed endpoint.

Perplexity has launched the Perplexity Orchestrator API, a single endpoint for frontier and open-weight models. It picks a serving provider by availability, capacity and latency, and bills everything through 1 account. Developers get fewer integrations and 1 invoice.

What is the Perplexity Orchestrator API?

The Perplexity Orchestrator API is a hosted inference gateway that serves many models behind 1 base URL. It covers frontier models from OpenAI, Anthropic, Google and xAI. It also serves open-weight models such as GLM, Kimi and DeepSeek, hosted by Perplexity or inference partners.

It accepts OpenAI Chat Completions, OpenAI Responses and Anthropic Messages requests. Most teams only change the API key and base URL. The OpenAI base URL is https://api.perplexity.ai/orchestrator/v1. Anthropic SDK users point at https://api.perplexity.ai/orchestrator, without /v1.

Perplexity runs the same layer internally, across 85+ models and more than a dozen providers.

How does provider failover work?

Failover keeps the model fixed and swaps the deployment. A Claude request that fails on Anthropic can be served by AWS Bedrock instead. The reliability docs set these rules:

  • Triggers are provider errors, rate limits and timeouts.
  • Each attempt has a time-to-first-token limit and a total-duration limit. The values are not published.
  • Invalid or over-context requests return HTTP 400 and are not retried.
  • If every deployment fails, the API returns HTTP 429 with Retry-After.
  • Requests that fail before producing output are not billed.

You cannot pick a deployment yourself.

What do the reliability and speed numbers show?

Perplexity measured production traffic from October 4 to November 2, 2026. Claude and GPT requests through Perplexity succeeded more often than requests to any single provider measured. Daily success rates also varied less during provider incidents. The post gives no percentage success rates.

Speed varied by provider too. For Claude Opus 5.5, Anthropic was fastest on 15 of 30 days, AWS Bedrock on 15. Azure’s median output speed for GPT-5.6 Sol was 27% higher than OpenAI’s. Speed-aware routing is still in progress.

How does automatic routing with perplexity/auto work?

Routing is in preview. You set model to perplexity/auto and pass a routing object. It holds a default_model and 1 to 5 routes, each with a name, description and model.

A decision model reads the conversation and route descriptions. It never sees route names or model IDs. If nothing matches, or the decision model fails or times out, the default model answers. So do media inputs.

Response headers report the result: x-perplexity-autoroute-outcome, -route and -confidence. The default policy sends traffic to GPT-6.1 Sol, with simple requests going to GPT-6 Luna. Perplexity also lists built-in Lower cost, Balanced and Higher quality profiles, plus an Auto effort preview.

Perplexity · Orchestrator API

How 1 API routes, fails over and bills

Interactive explainer. All figures from Perplexity's Nov 17, 2026 posts and docs.
Your appOpenAI or Anthropic SDK
model: anthropic/claude-opus-5-5
Orchestratorapi.perplexity.ai/orchestrator/v1
health · capacity · latency
Anthropicdeployment 1
AWS Bedrockdeployment 2
> Request served by Anthropic. Same model, published rate.

Failover triggers: provider error, rate limit or timeout. Each attempt has TTFT and total-duration limits (values not published). If every deployment fails: HTTP 429 with Retry-After. Requests that fail before output are not billed.

Customer support example. Click a turn to see where the decision model sends it.
Turn 1
General question
Turn 2
Billing dispute
Turn 3
Technical issue
Turn 4
Follow-up
default_model
GLM-5.3 Flash
route: billing_dispute
Claude Opus 5.5
route: technical_issue
GPT-6.1 Sol

  

model: "perplexity/auto" with 1 to 5 routes. The decision model reads route descriptions, never names or model IDs. No match, a decision failure or media input falls back to default_model. Each model keeps its own prompt cache. Preview feature.

Terminal-Bench 4.1, 63-task subset, in Claude Code. Routes: security biology after_refusal
Claude Fable 5.2 alone38/63
Fable + routes to GPT-6.1 Sol41/63
Fable + routes to GPT-6 Astra41/63

Self-reported, adjusted comparison. +3 tasks at a higher estimated cost per task. Results vary by workload.

Claude Opus 5.5, fastest provider per day (30 days)
■ Anthropic 15 days   ■ AWS Bedrock 15 days
Day order illustrative; only the 15/15 split is published.
GPT-5.6 Sol median output speed
0%
higher on Azure than on OpenAI

Window: Oct 4 to Nov 2, 2026. Speed-aware routing is still in progress. Model names as written in Perplexity's post.

Tier 0
$0
Google, xAI and open-weight models. Default perplexity/auto policy unavailable; use custom routes.
Tier 1
$50
Cumulative credit purchases. Unlocks OpenAI and most Anthropic models.
Tier 2
$250
Cumulative credit purchases. Unlocks Claude Opus 5, Opus 5.5 and the Fable models.
perplexity/glm-5.3 input$1.4 / 1M
perplexity/glm-5.3 output$4.4 / 1M
perplexity/glm-5.3 cache read$0.26 / 1M
Platform fee on creditsNone stated
Bring your own keyNot supported

Billed at the answering model's published rate, whichever provider serves it. Click a tier to expand.

Sources: perplexity.ai/hub/blog · docs.perplexity.ai© Marktechpost

Can routing work around refusals?

Perplexity tested this on a 63-task subset of Terminal-Bench 4.1, run in Claude Code. Anthropic documents that Claude Fable 5.2 safeguards can block benign security and life sciences work.

  • Claude Fable 5.2 alone: 38/63 tasks.
  • Fable plus routes to GPT-6.1 Sol: 41/63.
  • Fable plus routes to GPT-6 Astra: 41/63.

The routes covered security, biology and after_refusal requests. That is +3 tasks, at a higher estimated cost per task. Perplexity calls it an adjusted comparison; results vary by workload.

How is Orchestrator priced?

Each request is billed at the answering model’s published per-token rate. Failover to another provider does not change the rate. Perplexity says there is no additional platform fee on top of credits.

For example, perplexity/glm-5.3 lists $1.4 input, $4.4 output and $0.26 cache read per 1M tokens. Usage draws from prepaid Perplexity API credits, also purchasable through AWS Marketplace.

Access is tiered by cumulative credit purchases:

  • Tier 0: Google, xAI and open-weight models.
  • Tier 1 ($50): OpenAI and most Anthropic models.
  • Tier 2 ($250): Claude Opus 5, Opus 5.5 and the Fable models.

How does it compare with OpenRouter and Vercel AI Gateway?

FeaturePerplexity OrchestratorOpenRouterVercel AI Gateway
Model catalogFrontier (OpenAI, Anthropic, Google, xAI) plus open-weight GLM, Kimi, DeepSeek; count not disclosed (blog)400+ models, 70+ providers (source)400+ models (source)
API formatsChat Completions, Responses, Anthropic Messages (docs)Chat Completions, Responses, Anthropic Messages (docs)Chat Completions, Responses, Anthropic Messages (docs)
Platform feeNo additional platform fee on credits (blog)5.5% on credit purchases (Standard), 8% (Business) (pricing)No platform fee, no token markup (pricing)
Token pricingAnswering model’s published rate (FAQ)Provider price passed through (FAQ)Provider list price (docs)
Same-model provider failoverYes, automatic (docs)Yes, automatic fallback (source)Yes, automatic (changelog)
Prompt-based auto routerperplexity/auto, preview, 1 to 5 routes (docs)openrouter/auto, no router fee (docs)Not disclosed
Bring your own keyNot supported (FAQ)Supported, 5% fee above allowance (FAQ)Supported, no markup (docs)

Key Takeaways

  • 1 endpoint for OpenAI, Anthropic, Google, xAI and open-weight models.
  • Same-model failover across providers, billed at the same rate.
  • perplexity/auto routes by plain-language descriptions, in preview.
  • Refusal routing: 38/63 to 41/63 on Terminal-Bench 4.1, self-reported.


Check out the launch post, technical blog, quickstart, model catalog and routing docs. You can check the deployment options and specs here through our GPULeaderboard.com chrome extension.

Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us

The post Perplexity Launches Orchestrator API for Failover and Model Routing appeared first on MarkTechPost.

Be the first to rate this article.

Comments & Questions (0)

Captcha
Please be respectful — let's keep the conversation friendly.

No comments yet

Be the first to comment!