> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/core-concepts/product-versions-availability-and-deprecations.md).

# Product Versions, Availability, and Deprecations

Availability depends on the deployed release, enabled features, provider, and execution surface. Check the current catalog before building a dependency on a node or tool.

{% embed url="<https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fitw9VAQfkOSOtbD6t4Q8%2Fproduct-versions-availability-and-deprecations.mp4?alt=media&token=b3e8cfce-a73c-4db1-af28-2c47188bf65e>" %}
Find the application release in Deployment Info and check the current integration catalog.
{% endembed %}

## Before you begin

Access to the tool catalog or the API/MCP endpoint used by your application.

## Versions and availability

| Term                 | Definition                                                                                                                                                                               |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Feature availability | Whether a capability is exposed for the account, configuration, and release in use. Check the actual product or tool catalog rather than assuming availability from another environment. |
| Deprecation          | Notice that a capability is being replaced or should no longer be used for new work. Follow the stated migration behavior; deprecated tools do not all have the same operating status.   |
| API version          | The request and response contract selected by an API route. It is separate from the saved workflow version you ask the API to run.                                                       |
| Project version      | A specific saved configuration of a project. Select it explicitly when a result must be reproducible.                                                                                    |

## Check feature and version availability

1. Find the feature in the current interface or discover it through the catalog.
2. Check its provider, required context, and deprecation information.
3. Record the API version and selected project version separately.

Your project uses a feature available in the selected catalog.

## Behavior and limitations

Availability can depend on your plan, permissions, and enabled features. Check the catalog in your account before configuring a tool. Deprecated tools can remain in older workflows. Use the replacement guidance for those tools; do not assume a deprecated action continues to perform its former operation.

## Related resources

[Organizations, Workspaces, Folders, and Projects](https://docs.stackai.com/technical-reference/core-concepts/organizations-workspaces-folders-and-projects.md)


---

# 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.stackai.com/technical-reference/core-concepts/product-versions-availability-and-deprecations.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.
