Skip to content
modeldeprecations.dev
Cohere c4ai-aya-expanse-8b

Aya Expanse 8B (Cohere)

Retired

Yes — Aya Expanse 8B is retired. Cohere deprecated it on April 4, 2026 and shut it down on April 4, 2026; API requests to it now fail. The recommended replacement is Command A.

The small half of Cohere Labs' 23-language Aya Expanse release, and a model a lot of people picked precisely because 8B was the size they could self-host. It was retired on 4 April 2026, the same day it was announced. The 32B version survives; this one does not.

The facts

Provider Cohere
Model id c4ai-aya-expanse-8b
Released
Deprecated April 4, 2026
Shutdown April 4, 2026 · 121 days ago
Status Retired
Last verified August 3, 2026

What to use instead

Cohere Command A command-a-03-2025 Provider-recommended Active

Cohere names command-a-03-2025 and command-a-reasoning-08-2025, both far larger than 8B. If size was the point, command-r7b-12-2024 is the nearest supported model.

What parameters command-a-03-2025 accepts on modelparams.dev

Change the id

In most cases the migration is one string. Check the parameter differences before you ship — newer models drop older sampling knobs more often than they add them.

- "model": "c4ai-aya-expanse-8b"
+ "model": "command-a-03-2025"

Frequently asked questions

When did Cohere Aya Expanse 8B shut down?
Cohere Aya Expanse 8B shut down on April 4, 2026. API requests to it fail from that date onward.
What replaces Cohere Aya Expanse 8B?
Cohere recommends Command A (`command-a-03-2025`) as the replacement for Cohere Aya Expanse 8B. Cohere names command-a-03-2025 and command-a-reasoning-08-2025, both far larger than 8B. If size was the point, command-r7b-12-2024 is the nearest supported model.
Is Cohere Aya Expanse 8B still available?
No. Cohere Aya Expanse 8B is retired and no longer served — it was shut down on April 4, 2026. Calls to it return an error.
How do I migrate from Cohere Aya Expanse 8B to command-a-03-2025?
Swap the model id in your API call: replace "c4ai-aya-expanse-8b" with "command-a-03-2025". Cohere names command-a-03-2025 and command-a-reasoning-08-2025, both far larger than 8B. If size was the point, command-r7b-12-2024 is the nearest supported model.

Sources

Found something wrong? The data is one YAML file — edit it on GitHub.

This page, for machines

Drop the badge in a README so it turns red the day this model is retired:

[![c4ai-aya-expanse-8b](https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/cohere/c4ai-aya-expanse-8b.json)](https://modeldeprecations.dev/cohere/c4ai-aya-expanse-8b)

Other Cohere models

All Cohere deprecations →

How to use this site

The full guide, in Markdown. Copy it and hand it to a coding agent verbatim.

# How to use modeldeprecations.dev

[modeldeprecations.dev](https://modeldeprecations.dev) answers one question per model: is it deprecated,
when does it shut down, and what replaces it. Every date on the site is cited to the
provider's own documentation, with the date we last checked it.

Three lifecycle states are used, matching the providers' own vocabulary:

- **active** — still supported, no deprecation announced.
- **deprecated** — the provider has announced it is going away. It still answers requests.
- **retired** — API access is gone. Requests fail.

A model can be active *and* carry a shutdown date: Anthropic publishes a
"not sooner than" date and Google publishes an earliest shutdown date for models
that are current and fully supported. Those are reported as scheduled shutdowns,
not deprecations, because that is what the provider actually committed to.

## Check one model

```bash
curl https://modeldeprecations.dev/api/v1/models/openai/gpt-4-32k.json
```

Or fetch the page as Markdown, which includes the answer, the dates and the sources:

```bash
curl https://modeldeprecations.dev/openai/gpt-4-32k.md
```

## Full catalog

```bash
curl https://modeldeprecations.dev/api/v1/models.json
```

Ids are `provider/model`. Dated snapshots (`gpt-4-32k-0613`) are listed as aliases of
their canonical entry rather than as separate records.

Each entry carries `computed_status`, the lifecycle state recomputed against the build
date — so a model whose shutdown has passed reads `retired` without anyone editing data.

## Badges

A shields.io endpoint per model, for READMEs that should go red when a model dies:

```
https://img.shields.io/endpoint?url=https://modeldeprecations.dev/badge/openai/gpt-4-32k.json
```

## Calendar and changelog

- Subscribe to every shutdown date: https://modeldeprecations.dev/calendar.ics
- Changelog RSS: https://modeldeprecations.dev/changelog.xml

## JSON Schema

```bash
curl https://modeldeprecations.dev/api/v1/schema.json
```

## Contribute

Data lives in YAML under `models/{provider}/{model}.yaml` in the
[GitHub repo](https://github.com/mnfst/modeldeprecations.dev). Every lifecycle date needs a source URL; CI rejects a
date without one. Open a PR.

## For agents

- Machine-readable overview: https://modeldeprecations.dev/llms.txt
- This guide plus every model inline: https://modeldeprecations.dev/llms-full.txt
- Any page also exists as Markdown: append `.md` to a model URL.
- In a browser, this site registers a **WebMCP** tool on `navigator.modelContext`:
  `check_model_deprecation`, `list_shutdowns`, `find_replacement`, and `get_usage_guide`.
- Parameters each model accepts are catalogued on the sibling site, https://modelparams.dev.