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

Qwerky 72B

nano-gpt/qwerky-72b

От nano-gpt · семейство: qwerky · выпуск 2025-03-20

$0.500
Вход / 1M токенов
$0.500
Выход / 1M токенов
32K
Окно контекста
8K
Макс. вывод

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.

Coding1
  • Tool calling0/40
  • Structured output0/20
  • Reasoning0/10
  • Context window (100K → 1M)0/20
  • Provider availability1/10
Agents6
  • Tool calling0/35
  • Structured output0/25
  • Reasoning0/15
  • Output token limit5/15
  • Provider availability1/10
JSON / structured output18
  • Structured output / JSON mode0/50
  • Tool calling0/20
  • Temperature control0/10
  • Price-friendly for high-volume18/20
Cost efficiency62
  • Headline price (log-scaled)62/95
  • Has prompt-cache pricing0/5
Long context0
  • Context ≥ 100K0/100
Production-readiness65
  • Number of independent providers5/40
  • Has published per-token price20/20
  • Context window ≥ 8K15/15
  • No data inconsistencies across providers10/10
  • Official model (not derivative)15/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.

ScenarioCostAssumption
RAG answer
per 1,000 RAG answers
$2.75
< $0.01 per request
5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot.
Support ticket triage
per 10,000 tickets
$5.50
< $0.01 per request
1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support.
Data extraction
per 1,000 documents
$1.25
< $0.01 per request
2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines.
Code review
per 1,000 PRs
$4.50
< $0.01 per request
8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads.
Agent step
per 1,000 steps
$6.30
< $0.01 per request
12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step.

Детализация цен

Рекомендованная цена от nano-gpt · featherless-ai/Qwerky-72B

$0.500
Вход
$0.500
Выход

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

ПровайдерID модели провайдераВход / 1MВыход / 1MКонтекстВыпуск
NanoGPT
nano-gpt
featherless-ai/Qwerky-72B$0.500$0.50032K2025-03-20

Frequently asked questions

How much does Qwerky 72B cost?

Qwerky 72B costs $0.500 per 1M input tokens and $0.500 per 1M output tokens, sourced from nano-gpt. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.

What is the context window of Qwerky 72B?

Qwerky 72B has a context window of 32K tokens, with a max output of 8K tokens per reply. This is the total combined size of prompt + completion.

Does Qwerky 72B support tool calling?

No. Qwerky 72B does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.

Does Qwerky 72B support structured output / JSON mode?

No. Qwerky 72B does not support structured output / JSON-schema-constrained decoding. If your workflow requires it, look at the /capabilities/structured-output list for alternatives.

Can Qwerky 72B accept image input?

No. Qwerky 72B only accepts text as input. If you need image input, see our /capabilities/vision list for current vision-capable models.

Is Qwerky 72B open-weight?

No. Qwerky 72B is a proprietary model — only nano-gpt (and any approved hosting partners) can serve it. The pricing above reflects the cheapest API access.

What are the best alternatives to Qwerky 72B?

If Qwerky 72B doesn't fit, consider Brave (Answers), Exa (Research), Auto model (Basic). 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 nano-gpt 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.