Pricing calculator

Workload narrows the choice, the model is what you pick, and the commercial offering is what prices it. Everything below is priced by the pricing engine — this surface states the scenario and renders the result.

Runtime bundle
4267ff8ba415
Published at
2026-09-18T04:59:17Z
Catalogue fingerprint
2a40468a01db

Result

COMPLETE

Estimated cost

2.75 USD

Selection

Discovery and defaulting only. Not part of pricing identity.

What you pick. A price is never a property of a model.

Commercially authoritative. This is what prices the scenario.

provider
Agent Makers
channel
First-party managed API
status
Active
access scope
Public self-service
effective from
2026-02-27
policy version
audited-2026-10-01
disclosure
Public list
captured as of
2026-09-14

Usage

What goes in

tokens

The total you send, with any cached portion inside it.

tokens

A subset of the input total, not an addition to it.

Uncached inputDerived
1000000tokens

input less the cached portion, which is what the engine is sent

What comes out

tokens

Pricing options

Processing tierProduct default

A separate dimension from delivery.

Delivery modeProduct default

Batch is not Economy. The default is resolved by product configuration, never assumed.

Visible only where this offering records cache pricing.

Long contextDerived
Not derived for this scenario

not derived for this scenario

Capacity

Capacity modeProduct default

Structural: changing it rebuilds the form.

Services

  • Search GroundingAvailable

    Priced on its own meter; a service charge never folds into token usage.

  • Web SearchAvailable

    Priced on its own meter; a service charge never folds into token usage.

Commercial terms

Agreement pricing needs a verified customer identity, which this calculator does not establish. List pricing is shown.

More options

Separate from the runtime bundle version.

Period-level obligations are never applied to a request-scope estimate.

You set thisa value you chose

Product defaultconfiguration chose it

Derivedthe engine decided it, and it is not editable

Explanation level 3

Technical trace

The engine’s account of what it did, in the order it did it. Every value below is the engine’s own string, character for character — nothing here is rounded, reworded or shortened. Levels 1 and 2, in the estimate above, explain the price; this level is for a reader who has to reproduce or report it.

SUBJECT_PRICING

1 entry

Which subject was priced, and the published policy version that priced it.

  1. role
    SELECTED_OFFERING
    subject_kind
    OFFERING
    status
    PRICED
    requested_as
    selection.commercial_offering_id
METERING

3 entries

How each component's quantity was measured, and under which metering profile.

  1. component
    INPUT
    meter
    TOKEN_USAGE_INPUT
    profile_name
    Text Input Token Pass
    quantity
    1000000 TOKEN
  2. component
    OUTPUT
    meter
    TOKEN_USAGE_OUTPUT
    profile_name
    Text Output Token Pass
    quantity
    100000 TOKEN
  3. component
    CACHED_INPUT
    meter
    CACHE_HIT
    profile_name
    Cached Token Read
    quantity
    0 TOKEN
BASE_CHARGE_CALCULATION

3 entries

The rate applied to each measured quantity, and the amount it produced.

  1. component
    INPUT
    quantity
    1000000 TOKEN
    amount
    1.8 USD
  2. component
    OUTPUT
    quantity
    100000 TOKEN
    amount
    0.95 USD
  3. component
    CACHED_INPUT
    quantity
    0 TOKEN
    amount
    0 USD
CHARGE_MODIFIERS

1 entry

Rule outcomes in the phase that modifies charges, and what became of each.

  1. state
    UNRESOLVED
    reason

Run identity

These identify the run rather than explain the price. They are what a bug report needs. The page header above shows a twelve-character prefix of the catalogue fingerprint; the full sixty-four characters appear here and nowhere else.

catalogue_fingerprint
pricing_engine_version
0.7.0
orchestration_contract_version
v4
pricing_rule_registry_version
contract_digest
request_digest
execution_context_digest
runtime_state_digest