OptimToken All guides

Vision, audio, agents: what each capability adds to the bill

Published 2026-10-04 · Prose last reviewed 2026-10-20 · Figures recomputed nightly from the 2026-11-21 catalogue snapshot

A FinOps guide by OptimNow · prices from the live OptimToken catalogue

A product team says the feature needs to read screenshots. Someone then asks what vision costs, and the catalogue appears to answer: models that accept images carry a median blended price 2.91x the models that do not. That number is real and it is the wrong one to budget against. It compares model makers, not capabilities. This guide separates the two on 308 priced models. The cost that remains is the size of the shortlist each requirement leaves.

Four capabilities, all read from upstream facts

OptimToken reads capability tags from upstream model metadata. Image input and audio come from the model's declared input and output modalities. Tool use and a reasoning control come from the parameters the model accepts. Those four are facts about the model, so they can be priced.

Until 5 October 2026 the catalogue also carried a Code tag. It was assigned from a price threshold, so asking what Code adds to the bill would have returned the threshold. This guide never priced it, and the tag has since been removed.

Most of the catalogue-wide premium is a mix effect

Capabilities can cluster by model maker. A model maker whose entire line-up is multimodal and priced for enterprises puts every one of its models on the with-vision side. One selling small text models puts every one of its models on the other. Across the catalogue, the gap between the two sides then includes the gap between those two companies.

Compare inside one model maker's catalogue instead and the premium shrinks. Of the model makers with at least 2 models on each side, the median ratio between their vision models and their text-only models is 1.26x, against 2.91x across the catalogue. In 3 of 10 the ratio sits below 1, meaning that model maker's vision models are the cheaper half of its own line-up.

Vision price against text-only price, inside each model maker's own catalogue Vision price against text-only price, inside each model maker's own catalogue OpenAI 7.11x Tencent 2.43x Meta 2.05x Alibaba 1.75x Moonshot 1.34x Mistral 1.18x Nvidia 1.18x MiniMax 0.64x DeepSeek 0.60x Zhipu 0.57x
Vision price against text-only price, inside each model maker's own catalogue Vision price against text-only price, inside each model maker's own catalogue OpenAI 7.11x Tencent 2.43x Meta 2.05x Alibaba 1.75x Moonshot 1.34x Mistral 1.18x Nvidia 1.18x MiniMax 0.64x DeepSeek 0.60x Zhipu 0.57x
Median blended price of the model maker's vision models divided by the median of its text-only models. 1.00x is parity. Model makers with fewer than 2 models on either side are excluded, because one unusual row would set the ratio.

Across model makers the ratio runs from 0.57x to 7.11x, so image input is not free everywhere. Whose model you buy decides more of the bill than the capability does.

Counter-example: dropping a capability can raise the bill

The usual FinOps instinct is to treat model selection as rightsizing, and to stop paying for what the feature does not use. On this catalogue that instinct misfires at 3 of the 10 model makers with enough models to compare. At Zhipu the median vision model costs $0.986 per 1M blended tokens against $1.720 for its text-only models, so removing image input from the requirement moves the shortlist to the more expensive half.

At Google, the cheapest model accepting images is Gemma 3 4B at $0.085 per 1M blended tokens. Drop the image requirement and the cheapest thing on the same shelf is Gemma 2 27B at $0.650, a 7.65x gap in the wrong direction. Compare them side by side. The price follows the model's position in the line-up. The capability came with it.

What a requirement costs instead: the shortlist

If the rate card does not price capability, something else does. Every requirement removes models from consideration. A thinner shortlist costs you the competition that was holding the price down.

Models left when you require one capability (n=308) Models left when you require one capability (n=308) Tool use 274 / 308 Reasoning control 226 / 308 Image input 206 / 308 Audio in or out 31 / 308
Models left when you require one capability (n=308) Models left when you require one capability (n=308) Tool use 274 / 308 Reasoning control 226 / 308 Image input 206 / 308 Audio in or out 31 / 308
Each requirement applied on its own to the whole catalogue, not stacked. The pale bar is every priced model, the dark bar is the subset meeting that one requirement.

Read as a shortlist, the four requirements are not comparable at all. Tool use leaves 274 of 308 models, 89% of the catalogue. The cheapest model carrying it is Mistral Nemo at $0.030 per 1M blended tokens, against $0.012 for Summarize, the cheapest model overall. Requiring tool use multiplies the floor by 2.47x.

Worked example: the audio requirement

Audio behaves differently. It is the requirement worth planning around. Across the catalogue, 31 of 308 models accept or produce it, 10% of the total. The catalogue-wide price ratio is 2.16x, below image input's 2.91x, so on a rate-card reading audio looks the cheaper requirement. The cheapest model that handles audio is MiMo-V2.6-Flash at $0.238 per 1M blended tokens, against $0.012 for Summarize with no capability requirement at all. Adding audio to the specification multiplies the floor by 19.83x.

Concentration compounds it. Google makes 17 of the 31 audio models, 55% of the shortlist, spread across 8 model makers in total. A requirement met by one model maker on most of the shortlist is a negotiating position as much as a technical choice, and it belongs in the risk register next to the cost estimate. Where audio is a minority of requests, a router is the cheaper structure. Send the audio requests to a model that handles them and leave the rest on the catalogue floor. Paying the audio floor on every call buys audio for calls that carry none.

How to use this when choosing a model

These steps assume a team that already tags requests by type, the Walk stage in FinOps maturity terms. A team still reading one monthly invoice has nothing to route yet, and request-level tagging comes first.

These are the prices we quote, on a 30/70 input-output blend (the formula is here). They do not include what a capability costs in tokens once it is used. An image is billed as input tokens when it reaches the model, and a long screenshot is a long prompt. Price the payload with that formula; this guide prices the shortlist only.

Figures on this page come from the 2026-11-21 price snapshot and rebuild nightly.

The FinOps reasoning behind this guide comes from OptimNow's open-source practice library: github.com/OptimNow/cloud-finops-skills. If you want your own model shortlist sized against the capabilities your workload uses, OptimNow runs that review.

Questions this guide answers

Do models with image input cost more?

Across the catalogue, yes. Inside one model maker's line-up, the premium is smaller. On the 2026-11-21 OptimToken catalogue snapshot, models accepting images carry a median blended price 2.91x that of models that do not. Comparing within each model maker that has at least 2 models on each side, the median ratio falls to 1.26x, and at 3 of 10 model makers the vision models are the cheaper half. Most of the catalogue-wide gap measures the difference between model makers, not the price of the capability.

How many models support audio?

On the 2026-11-21 OptimToken catalogue snapshot, 31 of 308 priced text models accept or produce audio, 10% of the catalogue. The cheapest is MiMo-V2.6-Flash at $0.238 per 1M blended tokens, against $0.012 for Summarize with no capability requirement, so requiring audio multiplies the price floor by 19.83x.

Does requiring tool use narrow the choice of model?

Barely. On the 2026-11-21 OptimToken catalogue snapshot, 274 of 308 priced models accept tool-use parameters, 89% of the catalogue, and the cheapest of them is Mistral Nemo at $0.030 per 1M blended tokens. The cheapest model overall is Summarize at $0.012, so requiring tool use multiplies the floor by 2.47x.

What does a capability requirement cost?

The shortlist rather than the rate. Each requirement removes models from consideration, and the floor rises with it. On the 2026-11-21 OptimToken catalogue snapshot: tool use leaves 274 of 308 models and a floor 2.47x the catalogue floor; a reasoning control leaves 226 of 308 models and a floor 3.00x the catalogue floor; image input leaves 206 of 308 models and a floor 1.00x the catalogue floor; audio leaves 31 of 308 models and a floor 19.83x the catalogue floor.

These are list prices.

Your real cost also depends on caching and batching, negotiated discounts, marketplace agreements, and the contracts you already have. OptimNow audits exactly that.

Get a FinOps review

Data snapshot: 2026-11-21 · Compare all models · Cloud compute pricing · All guides