AI 模型情报

Writer: Palmyra X5

kilo/palmyra-x5

出品方: kilo · 发布 2025-04-28

$0.600
输入 / 1M token
$6.00
输出 / 1M token
1.04M
上下文长度
8K
最大输出

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

能力清单

工具调用推理? 结构化输出附件开放权重温度可调
支持模态: 输入 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.

Coding21
  • Tool calling0/40
  • Structured output0/20
  • Reasoning0/10
  • Context window (100K → 1M)20/20
  • Provider availability1/10
Agents6
  • Tool calling0/35
  • Structured output0/25
  • Reasoning0/15
  • Output token limit5/15
  • Provider availability1/10
JSON / structured output17
  • Structured output / JSON mode0/50
  • Tool calling0/20
  • Temperature control10/10
  • Price-friendly for high-volume7/20
Cost efficiency42
  • Headline price (log-scaled)42/95
  • Has prompt-cache pricing0/5
Long context91
  • Context window (100K → 2M)81/90
  • Has published price for full window10/10
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
$6.00
< $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
$12.00
< $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
$4.20
< $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
$10.80
$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
$10.80
$0.01 per request
12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step.

定价详情

推荐定价来自 kilo · writer/palmyra-x5

$0.600
输入
$6.00
输出

在 1 家渠道可用

服务商服务商模型 ID输入 / 1M输出 / 1M上下文发布日期
Kilo Gateway
kilo
writer/palmyra-x5$0.600$6.001.04M2025-04-28

Frequently asked questions

How much does Writer: Palmyra X5 cost?

Writer: Palmyra X5 costs $0.600 per 1M input tokens and $6.00 per 1M output tokens, sourced from kilo. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.

What is the context window of Writer: Palmyra X5?

Writer: Palmyra X5 has a context window of 1.04M tokens, with a max output of 8K tokens per reply. This is the total combined size of prompt + completion.

Does Writer: Palmyra X5 support tool calling?

No. Writer: Palmyra X5 does not support tool calling (function calling). If your workflow requires it, look at the /capabilities/tool-calling list for alternatives.

Does Writer: Palmyra X5 support structured output / JSON mode?

Support for structured output / JSON-schema-constrained decoding is not reported for Writer: Palmyra X5 in our data source. Verify with kilo's official documentation before relying on it in production.

Can Writer: Palmyra X5 accept image input?

No. Writer: Palmyra X5 only accepts text as input. If you need image input, see our /capabilities/vision list for current vision-capable models.

Is Writer: Palmyra X5 open-weight?

No. Writer: Palmyra X5 is a proprietary model — only kilo (and any approved hosting partners) can serve it. The pricing above reflects the cheapest API access.

What are the best alternatives to Writer: Palmyra X5?

If Writer: Palmyra X5 doesn't fit, consider Free Models Router, Reka Edge, Reka Flash 3. 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 kilo models

Capability lists this model is in

最近更新:

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.