Skip to main content

Evaluation Cost Calculator

Estimate the tokens and cost of each DynamoEval evaluation type before you run it, then compare starting configurations for low, balanced, and high-risk use cases. These are estimates, not billing.

Evaluation

Volume

Non-compliant prompts are split across the policies you select. Compliant prompts are sent to the target model once for each policy.

Models and Reasoning

The budget is a cap you set: the most hidden reasoning tokens one call can use. Enter 0 for reasoning off. DynamoEval reserves 2,500, 4,000, 8,000, or 16,000 for minimal, low, medium, and high effort.

The share is an estimate, not a setting. The model decides how much of the budget each call uses, and you cannot set it. Reasoning tokens billed = calls × budget × share. At 100% every call is assumed to use its full budget, which is an upper bound for capped calls. Judge and helper calls have no cap, so they could exceed it. After one measured run, enter the average reasoning used divided by the budget.

Assumptions

These values have not been measured. Edit any of them below.

Edit assumptions

System Policy Compliance

$17

Low to High assumptions: $11 to $26

Evaluation model
$12
Target model
$4.72
Calls
3,310
Input tokens
6.4M
Output tokens
397k
Reasoning tokens
0
RoleCallsInputOutputReasoningCost
Target model1,255126k321k0$4.72
Refusal judge1,2555.7M13k0$10
Prompt generation549499k38k0$1.41
Rewording25135k25k0$0.41
Total3,3106.4M397k0$17
  • These are estimates, not billing. Prompt caching and batch discounts are not modeled, and results sit within about 10% of the cost guide at the same settings.

Pricing Basis​

List prices are USD per 1M tokens from OpenAI's model and pricing pages as of October 1, 2026. Azure Global Standard deployments match them, and Azure Data Zone deployments cost 10% to 20% more.

Figures come from the DynamoEval cost guide and match its tables within about 10% at the same settings. Values marked as assumptions have not been measured, so run one small evaluation and compare its token usage before relying on a larger estimate.