API Notebooks in Anypoint Exchange are specifically designed to provide an interactive, code-centric documentation environment. They are web-based tools where developers can write and execute JavaScript code to demonstrate representative scenarios, often involving calls to multiple APIs. This allows consumers to not only read about the API but also investigate and run live code that illustrates complex use cases, directly fulfilling the requirements of the question for an executable, scenario-based documentation experience.

A. Enable mocking services for each of the relevant APIs and expose them via their Anypoint Exchange entry: Mocking services are for contract testing and basic interaction before an API is built; they do not provide an executable, code-centric environment for demonstrating scenarios.

B. Ensure the APIs are well documented through their Anypoint Exchange entries and API Consoles and share these pages with all API consumers: The API Console allows testing of individual endpoints but does not support demonstrating orchestrated scenarios involving multiple APIs in a single, runnable narrative.

D. Make relevant APIs discoverable via an Anypoint Exchange entry: Discoverability is a prerequisite for consumption, not the documentation environment itself. It allows consumers to find the API but doesn't provide the interactive, code-centric experience.

1. MuleSoft Official Documentation, "API Notebook": "An API notebook is a web-based, interactive tool in which you can describe and show the functionality of your API. You can use an API notebook to create tutorials, demonstrate common use cases, and allow users to experiment with your API." This source directly validates that API Notebooks are the intended tool for creating demonstrable, experimental use cases.

Source: MuleSoft Docs, docs.mulesoft.com/exchange/to-create-api-notebook. Accessed under the "API Notebook" section.

2. MuleSoft Official Documentation, "API Notebook Examples": This documentation provides concrete examples of how API Notebooks can be used to chain API calls, demonstrating a sequence of operations that represent a real-world scenario. For instance, an example might show how to first authenticate, then retrieve a list of items, and finally get details for a specific item.

Source: MuleSoft Docs, docs.mulesoft.com/exchange/notebook-examples. Accessed under the "Chain API Calls" subsection.

3. Anypoint Platform Architecture: Application Networks Courseware: Module 5, "Driving Consumption of Organizational Assets," emphasizes the role of Anypoint Exchange in creating a rich consumer experience. It positions API Notebooks as a key feature for going beyond basic documentation to provide interactive, runnable examples that accelerate API adoption and understanding.

Source: MuleSoft Training, Anypoint Platform Architecture: Application Networks, Module 5.