Estimate your monthly API cost

Estimate the tokens behind API requests, chat sessions, or agent runs, then apply your model’s rates.

Starting values are assumptions. The result covers token-billed API use; subscriptions and capacity plans require a separate comparison.

How the estimate works
What does one workload look like?

Agent workflow structure

Choose a starting workflow, then adjust its model calls, tool results, and context assumptions. A compact loop that alternates model actions and tool observations.

History sent again is the share of earlier content included in later model calls. It does not change how Standard Thinking stores your data. A history cap of 0 means no cap in this estimate.

Model and cost assumptions

The multiplier repeats the entire scenario, including model and tool calls. Add model-only evaluation calls to the workflow assumptions instead. The defaults are DeepSeek-V4.1-Flash’s rates and context window from the API rate table. Rates are editable assumptions; view API rates before using the estimate for budgeting.

Three choices shape every estimate

Workload type controls how calls and history are counted. Agent presets are examples; replace their values with your application’s measurements.

What does one workload look like?

Requests counted separately · Chat history · Tools and model calls

API · Chat · Agent

Workflow preset

A compact loop that alternates model actions and tool observations.

Simple tool loop

Model and cost assumptions

The workload multiplier scales the complete scenario, including model and tool calls, to represent retries or repeated runs.

Context limit · rates

Count what the model processes on each call

A user’s task can involve several model calls. Count what each call receives and produces, including the calls made by parallel workers.

Include context sent again

For an assumed five-call run, a 1,000-token prefix sent on every call contributes 5,000 input tokens before new messages or tool results.

Count each model call

Planning, worker tasks, summaries, and retries may add calls to the workflow.

Check the largest context

Monthly totals estimate the bill; the largest individual context is compared with the model limit. Passing that check does not validate the whole workload.

Use rates for your model

Replace the example rates and context limit with the values that apply to your selected model.

Compare API rates using the same call assumptions. For Product Plan, bring peak traffic and request sizes when discussing capacity.

View all resources