Unknown providerLLMactive

Claude Sonnet 4.6 (batch) API Pricing

Compare prices from 1 provider, including 0 official. 1 price source is collected automatically.

Data snapshot:

Official input / 1M—
Lowest input / 1M$1.50
Maximum input gap—Not a service-quality measure
Comparable providers11 live

Claude Sonnet 4.6 (batch) provider prices and multipliers

No complete verified official input/output baseline is currently recorded, so provider quotes are shown without multipliers.

Providers: 1From, within billing group: $1.50Lowest observed: $1.50Lowest input multiplier: —
Official input baseline—Official output baseline—Price multipliers do not measure stability, rate limits, refunds, or service quality.
Claude Sonnet 4.6 (batch) provider price and evidence comparison
Provider / operatorInput / 1M tokensOutput / 1M tokensvs officialPrice evidencePublic operating historyAPI docsRefund policyPayment / invoice
OpenRouterOperator type not confirmed$1.50$7.50
In —Out —
Live API pricePlatform page ↗Observed: —UnknownView docs ↗Not providedVisa · Mastercard · CryptocurrencyInvoice support not confirmed

Platform-submitted information or domain verification does not mean the price was independently checked and is not a ComputeUnion guarantee of pricing, availability, refunds, compliance, invoices, or service quality.

External capability references

Only source results safely mapped to the official model name are shown.

No safely matched external result is available; adjacent model scores are not substituted.

FAQ

How is Claude Sonnet 4.6 (batch) API priced?

Input and output tokens are billed separately. A complete official input/output baseline is not currently recorded, so provider quotes are normalized per million tokens.

Which provider is cheapest for Claude Sonnet 4.6 (batch)?

The lowest recorded input price is $1.50/1M tokens from OpenRouter; verify provider terms and the observation date before production use.

How do official and relay prices differ?

Official and relay channels can differ in price, latency, limits, and service terms; evaluate them separately for production traffic.