> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/flagship-deprecated/release-notes/october----flagship-becomes-feature-experimentation--rollouts.md).
# October - Flagship becomes Feature Experimentation & Rollouts
## **What's new?**
### A new name, and use cases closer to your needs
Say goodbye to ***Flagship***!
AB Tasty presents ***AB*** ***Feature experimentation & Rollouts***, the new **brand identity** for our offer around **API based experimentations and SDKs**.
Platforms are about to be merged for a seamless experience and much more cross-technologies use cases.
## **What doesn't change**
***AB Feature experimentation & Rollouts*** is the new **commercial** name for ***Flagship***.\
\&#xNAN;***Flagship*** name is still used in our API and codebases and remains the basis for all our technical methods and functions. The technical documentation will continue to refer to ***Flagship*** as nothing changes from a technical and implementation points of view.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.abtasty.com/flagship-deprecated/release-notes/october----flagship-becomes-feature-experimentation--rollouts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.