> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-users/all-about-llms/when-a-model-is-retired.md).

# When a Model Is Retired

AI models are replaced by newer versions over time. When Blockbrain takes a model out of service, it names a replacement, so your chats, bots and agents keep working.

#### Deprecated and retired

| Status         | What it means                                   | What you see                                                 |
| -------------- | ----------------------------------------------- | ------------------------------------------------------------ |
| **Deprecated** | The model still works, but will be retired soon | A banner naming the replacement, with a **Switch to** button |
| **Retired**    | The model is no longer available                | The replacement is used automatically, and a banner says so  |

The replacement runs at the same provider, in the same region or a narrower one, and does the same job as the model it replaces.

#### In a chat

When the model of your chat is deprecated, a banner shows above the message field and names the replacement. Click **Switch to** to use the replacement right away.

When the model is retired, the chat uses the replacement automatically. The banner tells you which model the chat now uses.

#### In bots and agents

When you edit a bot or an agent that uses a deprecated or retired model, the replacement is selected for you. Click **Save** to apply it.

Bots and agents keep running until then. A retired model is replaced automatically when they run.

{% hint style="info" %}
New models and retirements are announced in [LLM Updates](https://docs.blockbrain.ai/news/llm-updates.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blockbrain.ai/for-users/all-about-llms/when-a-model-is-retired.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
