Skip to main content
This is the complete rate card for Orion agent pricing. For the value overview, cost components, and worked examples, start with the Pricing page.

How a run cost is calculated

The standard dollar cost is the sum of model-token usage and fixed-price tools. The service-tier multiplier is applied once at the run level:
Where:
  • model_cost includes orchestration tokens and token-billed tool usage. Orchestration uses the rates for the model ID you selected; tool tokens are itemized on the per-span ledger
  • fixed_tool_cost is the sum of fixed-price tools such as segmentation, generation, OCR, and sandbox execution
  • mode_multiplier is determined by the service tier: 1.0× standard, 0.5× flex, or 1.8× priority
Every run itemizes these components into a per-span cost ledger, applying the multiplier once at the run level (effective_cost = SUM(span.cost) × mode_multiplier). The rates that feed each span are below.

Token rates

A run has two kinds of token usage:
  • Orchestration tokens: the Orion agent reasoning, dispatching tools, and writing the response. These bill at the rates for the model ID you selected.
  • Tool tokens: the LLM-backed tools the agent calls. These are billed by the tokens each tool consumes, at the rate for the model that ran that tool (which may differ from the model ID you selected). The ledger itemizes each span.
The ledger is the source of truth for each charge: it records the token counts behind every span. These tools are token-billed rather than fixed-price: Quality tiers (fast / auto / pro) use the tier rates below. Pinned Orion-2 backbones use model-specific input/output rates. The full list of accepted model IDs is in the Chat Completions API reference.

Orion 2 model token rates

Rates are USD per 1M tokens. Orchestration tokens use the rates for the model ID you selected. Tool-token spans are itemized on the ledger. Cached input tokens are billed at the listed fraction of the input rate.

Quality tiers

Curated Orion-2 tiers. Fast and Auto share the same token rates; Pro is higher.
Model IDInputOutputCached input
vlmrun-orion-2:fast$0.30$2.5010% of input
vlmrun-orion-2:auto$0.30$2.5010% of input
vlmrun-orion-2:pro$1.00$10.0010% of input

Open-weight pins

These open-weight Orion-2 backbones bill at the Fast / Auto token rates:
Model IDInputOutputCached input
vlmrun-orion-2:qwen3.6-35b-a3b$0.30$2.5010% of input
vlmrun-orion-2:gemma4-26b-a4b$0.30$2.5010% of input
vlmrun-orion-2:cosmos3-nano$0.30$2.5010% of input

Pinned hosted backbones

These variants bill at model-specific pass-through rates (not the Fast / Auto / Pro tier rates):
Model IDInputOutputCached inputThinking
vlmrun-orion-2:kimi-2.6$0.66$3.4122% of inputN/A
vlmrun-orion-2:muse-spark-1.1$1.25$4.2510% of inputN/A
vlmrun-orion-2:gemini-flash-3.6$1.50$7.5010% of input$7.50
vlmrun-orion-2:grok-4.5$2.00$6.0025% of inputN/A
vlmrun-orion-2:opus-4.8$5.00$25.0010% of inputN/A
vlmrun-orion-2:gpt-5.5$5.00$30.0010% of inputN/A
Cached input is billed at the listed fraction of the input rate (for example, 10% of input means cached tokens cost $0.10 when input is $1.00 per 1M). Thinking tokens, when present, bill at the Thinking rate. Costs scale with tokens consumed, so simple inputs are cheaper than complex ones. See model variants for when to pin each backbone.

LLM orchestration

Every agent run includes LLM token costs for reasoning, tool dispatch, and response synthesis, charged at the selected model ID’s input/output rates. Pinned frontier backbones (for example vlmrun-orion-2:gpt-5.5 or vlmrun-orion-2:opus-4.8) use their own model-specific rates from the table above. A typical single-tool Fast or Auto run adds approximately $0.01–$0.03 (or $0.03–$0.08 on Pro) in orchestration costs. Multi-step and frontier-model runs will be higher.

Fixed-price tools

These tools have a fixed dollar price per unit.

Image

Priced per image. Fast and Auto share the same rates; Pro is higher where noted.
CapabilityDescriptionFast / AutoPro
SegmentObject segmentation (GPU-backed)$0.01$0.02
Generate & EditGenerate or edit images from prompts$0.04$0.24

Document

Priced per page.
CapabilityDescriptionFast / AutoPro
OCR & LayoutExtract text and detect page structure$0.01$0.04
Extract grounding / confidenceOrion-2 document.extract surcharge when grounding or confidence is enabled$0.001$0.001

Video

Priced per second (generated video).
CapabilityDescriptionFast / AutoPro
Generate & EditGenerate video from text/image prompts$0.15/sec$0.40/sec
Standard video generation produces ~6 seconds. At Fast / Auto pricing, $0.15/sec × 6s = $0.90; at Pro, $0.40/sec × 6s = $2.40.

Compute & execution

Legacy pricing (vlm-1)

VLM Run is transitioning to dollar and token based pricing for Orion 2. The vlm-1 model family and older per-request rates below are kept for reference during the transition and may be removed in a future update. New workloads should use Orion 2 pricing above.
The vlm-1 model family is available on /v1/image/generate and /v1/document/generate routes with three quality tiers:Domain API token rates are in USD per 1M tokens:Set the model via request.model:

FAQ

Fixed-price tools (segmentation, image generation, video generation, OCR, sandbox execution) have predictable dollar prices per unit. Token-billed tools (captioning, detection, document parsing, video analysis) bill by the tokens they consume, itemized on the per-span ledger.
Open-weight pins (vlmrun-orion-2:qwen3.6-35b-a3b, vlmrun-orion-2:gemma4-26b-a4b, vlmrun-orion-2:cosmos3-nano) bill at the Fast / Auto token rates ($0.30 input / $2.50 output per 1M). Hosted frontier pins such as vlmrun-orion-2:kimi-2.6, vlmrun-orion-2:gpt-5.5, vlmrun-orion-2:opus-4.8, vlmrun-orion-2:muse-spark-1.1, vlmrun-orion-2:grok-4.5, and vlmrun-orion-2:gemini-flash-3.6 bill at their model-specific input/output rates in the Orion 2 model token rates section. Fixed-price tools still use the Fast / Auto / Pro tool rates based on the resolved quality tier.
It’s the sum of model token costs (orchestration + token-billed tools) and fixed-price tool charges. The response includes cost_dollars (effective amount after the service-tier multiplier) and standard_cost_dollars (baseline).
Every billable action during a run is recorded as a span: each LLM turn, each sandbox execution, and each tool call. The total is the sum of spans, with the service-tier multiplier applied once at the run level. This gives you full visibility into cost drivers.
Yes. Image I/O, rotation, cropping, video trimming, document navigation, UI detection, and similar utilities are free.