How this calculation works
Orchestrator API token catalog, which is in private preview at the checked date. These are Perplexity-hosted model routes, not the consumer subscription or retired Sonar assumptions. Cache reads are separate; no dedicated cache-write surcharge is modeled. Search API and Agent tool invocations need their own fee total.
Per request USD = Σ(disjoint billed tokens × selected USD per million / 1,000,000); period = requests/day × days × per request + extra period feesA worked example
A fictional workload of one thousand fresh input tokens and two hundred visible output tokens per request costs 0.006 USD per request at the default listed model rate. One thousand requests each day for thirty days gives 180 USD before any extra fee or tax. The rate table shows how selecting another published model changes that result.
Good to know
Independent estimate from the dated official rate card, not an invoice or live tariff. Verify current model availability, billing categories and provider terms. Do not use subscription allowances as API credit. Taxes, negotiated discounts and unentered charges are excluded.
Reference: Perplexity official pricing (opens in a new tab) ↗
Which Perplexity bill this estimates
Orchestrator API token catalog, which is in private preview at the checked date. These are Perplexity-hosted model routes, not the consumer subscription or retired Sonar assumptions. Cache reads are separate; no dedicated cache-write surcharge is modeled. Search API and Agent tool invocations need their own fee total.
A model selected here is a specific hosted price row. It is not a promise of access, a context-window validator or a statement that every deployment of that model costs the same amount. Use the provider that will actually issue your invoice.
The DeepSeek API cost calculator covers a separate account or billing model. Compare its own documented scope rather than carrying a quota percentage or hosted rate across providers.
Read more: Perplexity official pricing (opens in a new tab) ↗
Enter disjoint token categories
Input categories must not overlap. Fresh input excludes cache reads and separately billed cache writes; the output field should contain visible billed completion tokens. Add reasoning tokens only when the provider reports them separately and they are not already included in the output count.
A million tokens is the pricing denominator, not a minimum purchase. For example, one thousand tokens is one thousandth of a million. The calculator keeps fractional dollars internally and displays small per-request charges without rounding them into an apparent free service.
Choose a model and check the applicable tier
The table links each model row to its official source and displays the checked date. The result identifies the selected billing route and any automatic long-context or scheduled promotional transition supported by this snapshot.
A mixed workload needs separate calculations for differently sized requests or different models. One average prompt length can hide expensive threshold crossings; a request just over a tier boundary may price all of its tokens at the higher tier.
Ways to reduce Perplexity API spending
Choose the API surface before comparing prices. A Search API request is not the same billing unit as a model call. Use the requested model rate and add independently priced search or retrieval operations rather than expecting them to be included in output-token charges.
Compare cost per successful task as well as cost per token. A cheap first attempt followed by many repairs can cost more than a stronger model that finishes correctly. Measure a representative sample before forecasting a large daily volume.
Budget for more than the model response
The additional-fee field is one USD total for the entire entered period. Add independently priced tools, grounding, storage or regional charges there after checking their billing units. It is not a per-request amount and does not receive a token batch discount.
The INR result multiplies total USD by your entered exchange-rate assumption. It is not a live foreign-exchange quote and does not add Indian taxes or payment-provider conversion charges automatically. API accounts, console billing and consumer subscriptions remain separate.
Independent estimate disclaimer
Independent estimate from the dated official rate card, not an invoice or live tariff. Verify current model availability, billing categories and provider terms. Do not use subscription allowances as API credit. Taxes, negotiated discounts and unentered charges are excluded.
Rates checked 9 November 2026. Model lists are a researched selection, not an exhaustive live catalog. A later billing date uses only scheduled changes explicitly recorded in the source snapshot; verify any subsequent unscheduled changes before relying on the forecast. No API key is needed or requested.
A few questions, answered
Does a paid chat plan cover these API calls?
Do not assume so. This calculator estimates the selected API tariff. Any explicit account credits or separate subscription benefit must be checked in the relevant billing console.
Why can the invoice differ from the estimate?
Actual tokens, repeated agent calls, cache hits and writes, reasoning output, tools, regions, taxes and negotiated terms can differ from the entered scenario.