# Ember-1

Fireworks · Proprietary · bench-align-v5

> Every figure below is reproduced as its upstream source published it: nothing is modelled, estimated, interpolated or converted. `Unavailable` means no source published the value — it is never a zero. Each value carries its evidence state and the date it was observed.

Page: https://modelchoice.dev/models/ember-1  
JSON: https://modelchoice.dev/api/model/ember-1

## Facts

| Field | Value | Evidence |
| --- | --- | --- |
| Canonical id | `ember-1` | — |
| Overall score | Unavailable | Unavailable · source benchlm:models |
| Verified score (BenchLM): a separate BenchLM figure, not the overall score | 74 | Observed 2026-11-21 · source benchlm:models |
| Context window | 1.04M tokens | Observed 2026-11-21 · source benchlm:models |
| Modalities (models.dev) | Input: text, image · Output: text | Observed 2026-11-21 · source openrouter:pricing |
| Release date | 2026-09-23 | Observed 2026-11-21 · source benchlm:models |
| Access type | Proprietary | — |
| Blended $/1M (75% input / 25% output) | $6.00 | Derived from the input and output rates below |

**Only a verified score is published.** BenchLM publishes no overall score for this model, so the overall score stays unavailable. The verified score beside it is a separate figure in BenchLM's data. BenchLM does not document how the two are calculated differently, and they can differ widely, so one is never used in place of the other.

## Capability evidence

Seven axes from the ranking source. An axis the source did not score is unavailable, not zero. Beside each score is BenchLM's separate verified score for that axis; the two are published side by side and are not interchangeable.

| Axis | Score | Evidence | Verified (BenchLM) | Verified evidence |
| --- | --- | --- | --- | --- |
| Agentic | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |
| Coding | Unavailable | Unavailable · source benchlm:models | 79.9 | Observed 2026-11-21 · source benchlm:models |
| Knowledge | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |
| Reasoning | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |
| Multimodal & Grounded | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |
| Instruction Following | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |
| Math | Unavailable | Unavailable · source benchlm:models | Unavailable | Unavailable · source benchlm:models |

## Runtime service evidence

Measured values with the date they were observed. Nothing is inferred from a sibling model or a provider claim. Regional or per-endpoint measurements appear only when the API supplies them; none are modelled.

| Measurement | Value | Observed | Last good | Evidence |
| --- | --- | --- | --- | --- |
| Time to first token | Unavailable | Unavailable | Unavailable | Unavailable · source benchlm:speed |
| Throughput | 64 tok/s | 2026-11-21 | 2026-11-21 | Observed 2026-11-21 · source openrouter:endpoints |

## Endpoint and price matrix

Every published price component, including cache reads and writes.

| Component | USD | Evidence |
| --- | --- | --- |
| Input / 1M tokens | $3.00 | Observed 2026-11-21 · source benchlm:pricing |
| Output / 1M tokens | $15.00 | Observed 2026-11-21 · source benchlm:pricing |
| Cache read / 1M tokens | $0.30 | Observed 2026-11-21 · source benchlm:pricing |
| Cache write / 1M tokens | Unavailable | Unavailable · source openrouter:pricing |
| Blended / 1M (75% input / 25% output) | $6.00 | Derived — from the input and output rates above; it has no source record of its own |
| Cost per successful task (LiveBench) | Unavailable | Unavailable · source livebench:table |

**Pricing note.** Fireworks lists the Ember-1 serverless API at $3.00 input, $0.30 cached input, and $15.00 output per million tokens for `accounts/fireworks/models/ember-1`. The model page states a 1,040K-token context. Fewer generated reasoning tokens may lower total task cost, but the per-token rates match the Kimi K3 rates quoted in the launch post.

## Workload-aware monthly cost example

10 conversations per day × 8 messages × 22 active days, 1200 input and 400 output tokens per message, no cache. Derived here from the published rates above by this site's own calculator — not a figure any source published.

| Field | Value |
| --- | --- |
| Modelled monthly cost | $16.90 |
| Modelled tokens | 2.82M |

## Benchmark record

6 matched benchmark rows with their published value, unit, and provenance.

### Coding

| Benchmark | Value | Tasks | Difficulty | Provenance |
| --- | --- | --- | --- | --- |
| Terminal-Bench 2.1 | 82.0 | Terminal-based software-agent tasks | Professional software engineering | [Terminal-Bench](https://www.tbench.ai/) |
| SWE-bench Verified (Software Engineering Benchmark Verified) | 92.2 | 500 verified issues | Professional software engineering | [SWE-bench: Can Language Models Resolve Real-World GitHub Issues?](https://arxiv.org/abs/2310.06770) |
| DeepSWE | 75.2 | 113 software engineering tasks across 91 repositories and 5 languages | Long-horizon software engineering | [DeepSWE benchmark blog](https://deepswe.datacurve.ai/blog) |

### Agentic

| Benchmark | Value | Tasks | Difficulty | Provenance |
| --- | --- | --- | --- | --- |
| Terminal-Bench 2.1 | 82.0 | Terminal-based software-agent tasks | Professional software engineering | [Terminal-Bench](https://www.tbench.ai/) |
| τ²-bench Airline (τ²-Bench Airline Domain) | 66.0 | Airline customer-service tasks | Policy-constrained airline support workflows | [τ²-Bench: Evaluating Conversational Agents in a Dual-Control Environment](https://arxiv.org/abs/2506.07982) |
| Terminal-Bench 4.1 | 21.80 | 66 professional computer-work tasks | Frontier autonomous knowledge work | [Terminal-Bench 4.1](https://www.tbench.ai/news/terminal-bench-4-1) |

## Lifecycle and limitations log

Lifecycle events the source associates with this model.

No lifecycle event references this model. That is not evidence the model has no lifecycle plan — only that this source published none.

## What this profile does not claim

Values are reproduced exactly as their sources published them, in the units those sources declared; none are converted, interpolated, or averaged across providers. Any field marked unavailable was attempted and not returned. Last attempted fetch for this model's score: 2026-11-21 04:17 UTC.
