AI 模型情報

Reka Edge

kilo/reka-edge

出品方: kilo · 發布 2026-03-20

$0.100
輸入 / 1M token
$0.100
輸出 / 1M token
16K
上下文長度
16K
最大輸出

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

能力清單

工具呼叫推理? 結構化輸出附件開放權重溫度可調
支援模態: 輸入 image, text, video · 輸出 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.

Coding41
  • Tool calling40/40
  • Structured output0/20
  • Reasoning0/10
  • Context window (100K → 1M)0/20
  • Provider availability1/10
Agents46
  • Tool calling35/35
  • Structured output0/25
  • Reasoning0/15
  • Output token limit10/15
  • Provider availability1/10
JSON / structured output50
  • Structured output / JSON mode0/50
  • Tool calling20/20
  • Temperature control10/10
  • Price-friendly for high-volume20/20
Cost efficiency79
  • Headline price (log-scaled)79/95
  • Has prompt-cache pricing0/5
Long context0
  • Context ≥ 100K0/100
Vision64
  • Accepts image input50/50
  • Context window (10K → 1M)3/30
  • Has published price10/10
  • Provider availability1/10
Production-readiness58
  • Number of independent providers5/40
  • Has published per-token price20/20
  • Context window ≥ 8K8/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
$0.55
< $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
$1.10
< $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
$0.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
$0.90
< $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
$1.26
< $0.01 per request
12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step.

定價詳情

推薦定價來自 kilo · rekaai/reka-edge

$0.100
輸入
$0.100
輸出

於 1 家供應商可用

服務商服務商模型 ID輸入 / 1M輸出 / 1M上下文發布日期
Kilo Gateway
kilo
rekaai/reka-edge$0.100$0.10016K2026-03-20

Frequently asked questions

How much does Reka Edge cost?

Reka Edge costs $0.100 per 1M input tokens and $0.100 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 Reka Edge?

Reka Edge has a context window of 16K tokens, with a max output of 16K tokens per reply. This is the total combined size of prompt + completion.

Does Reka Edge support tool calling?

Yes. Reka Edge 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 Reka Edge support structured output / JSON mode?

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

Can Reka Edge accept image input?

Yes. Reka Edge accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check kilo's docs for the exact rule.

Is Reka Edge open-weight?

Yes. Reka Edge'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 Reka Edge?

If Reka Edge doesn't fit, consider Free Models Router, Reka Flash 3, AI21: Jamba Large 1.7. 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.

最近更新:

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.