Интерфейс моделей ИИ

devstral-2:123b

ollama-cloud/devstral-2-123b

От ollama-cloud · семейство: devstral · выпуск 2025-12-09

⚠ Это сообществом дообученная / производная модель — не официальный релиз вендора.

Неизвестно
Вход / 1M токенов
Неизвестно
Выход / 1M токенов
262K
Окно контекста
262K
Макс. вывод

Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.

Возможности

Tool callingРассуждение? Структурированный выводВложенияОткрытые веса? Управление температурой
Модальности: вход text · выход text

Model fit scores

0–100 · higher is better

These scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.

Coding49
  • Tool calling40/40
  • Structured output0/20
  • Reasoning0/10
  • Context window (100K → 1M)8/20
  • Provider availability1/10
Agents51
  • Tool calling35/35
  • Structured output0/25
  • Reasoning0/15
  • Output token limit15/15
  • Provider availability1/10
JSON / structured output20
  • Structured output / JSON mode0/50
  • Tool calling20/20
  • Temperature control0/10
  • Price-friendly for high-volume0/20
Cost efficiency0
  • Has published price0/100
Long context51
  • Context window (100K → 2M)51/90
  • Has published price for full window0/10
Production-readiness30
  • Number of independent providers5/40
  • Has published per-token price0/20
  • Context window ≥ 8K15/15
  • No data inconsistencies across providers10/10
  • Official model (not derivative)0/15

Cost Efficiency Index

Open full calculator →

Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.

This model has no published per-token price, so we can't compute a cost estimate. See the provider's official pricing page for current rates.

Доступна у 1 провайдеров

ПровайдерID модели провайдераВход / 1MВыход / 1MКонтекстВыпуск
Ollama Cloud
ollama-cloud
devstral-2:123bUnknownUnknown262K2025-12-09

Frequently asked questions

How much does devstral-2:123b cost?

devstral-2:123b does not have a publicly published per-token price in our data source. This usually means it is gated behind enterprise sales or invite access. Check ollama-cloud's official pricing page for the most current rates.

What is the context window of devstral-2:123b?

devstral-2:123b has a context window of 262K tokens, with a max output of 262K tokens per reply. This is the total combined size of prompt + completion.

Does devstral-2:123b support tool calling?

Yes. devstral-2:123b supports tool calling (function calling). This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.

Does devstral-2:123b support structured output / JSON mode?

Support for structured output / JSON-schema-constrained decoding is not reported for devstral-2:123b in our data source. Verify with ollama-cloud's official documentation before relying on it in production.

Can devstral-2:123b accept image input?

No. devstral-2:123b only accepts text as input. If you need image input, see our /capabilities/vision list for current vision-capable models.

Is devstral-2:123b open-weight?

Yes. devstral-2:123b's weights are publicly available, so you can self-host or fine-tune. Note that open weights ≠ open source — the training data and code are typically not released.

What are the best alternatives to devstral-2:123b?

If devstral-2:123b doesn't fit, consider ministral-3:14b, rnj-1:8b, ministral-3:8b. Each one targets the same use case — see the Related links below for direct head-to-head pages.

Where does this data come from?

All numbers come from the public models.dev API and are normalised into a single canonical model record. We re-pull daily and write any changes (price, context, capability) to the /changelog page.

More ollama-cloud models

Последнее обновление:

Data is sourced from models.dev and normalized for comparison. Prices and capabilities may change. Always verify critical production decisions with the provider's official documentation.