Unknown providerLLMactive

Mistral NeMo API Pricing

2 available providers and 2 live price sources tracked, including 1 official provider.

Data snapshot:

Official input / 1M$0.15
Lowest input / 1M$0.019
Maximum input gap87.3%Not a service-quality measure
Comparable providers22 live

Mistral NeMo provider prices and multipliers

Input and output multipliers are each calculated as provider price ÷ official baseline; 1.00× equals the official price.

Providers: 2From, within billing group: $0.019Lowest observed: $0.019Lowest input multiplier: 0.13×
Official input baseline$0.15Official output baseline$0.15Price multipliers do not measure stability, rate limits, refunds, or service quality.
Mistral NeMo provider price and evidence comparison
Provider / operatorInput / 1M tokensOutput / 1M tokensvs officialPrice evidencePublic operating historyAPI docsRefund policyPayment / invoice
Mistral AIunknown$0.15$0.15
In 1.00×Out 1.00×
Official price sourcePlatform pageObserved: UnknownView docsNot providedvisa · mastercardunknown
OpenRouterunknown$0.019$0.03
In 0.13×Out 0.20×
Live API pricePlatform pageObserved: UnknownView docsNot providedvisa · mastercard · cryptounknown

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 Mistral NeMo API priced?

Input and output tokens are billed separately. The current recorded official baseline is $0.1500 input / $0.1500 output per 1M tokens.

Which provider is cheapest for Mistral NeMo?

The lowest recorded input price is $0.019/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.