>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3556309. --> Reported by: [matthews](https://www.drupal.org/user/114486) >>> <h3>Problem to Solve</h3> <p>Drupal CMS 2.0 includes AI Recipes intended to work immediately during installation or via Project Browser. The current AI Provider onboarding patterns require email setup, credentials, and billing configuration before anything works. This blocks the turn-key experience Drupal CMS aims to deliver.</p> <p>Selecting an AI Recipe in the installer must result in a working AI feature without friction.</p> <h3>Proposed Solution</h3> <p>Introduce a unified onboarding pattern allowing for anonymous AI usage during initial Drupal CMS usage when AI Recipes are selected. The amazee.ai AI Provider is ready to support this flow.</p> <p>This experience should apply when:</p> <p>&bull; The user selects an AI Recipe during Drupal CMS install<br> &bull; The user later installs an AI Recipe via Project Browser</p> <p>Default behaviour when the amazee.ai AI Provider is part of an AI Recipe<br> 1. User creates a Drupal CMS instance (Composer, download, desktop app)<br> 2. User selects an AI Recipe on the first installer screen<br> 3. The installer shows a short disclosure that an AI Provider module is being installed and initial AI usage will be fully anonymous<br> 4. The user can use AI immediately until the anonymous AI budget ($1&ndash;$2 value) is exhausted<br> 5. At that point, user is prompted to begin a free 30-day trial by providing an email address<br> 6. After the trial, the user may continue via paid subscription through the standard provider flow</p> <h3>Key characteristics</h3> <p>&bull; Zero manual setup<br> &bull; Zero friction to evaluate AI capability<br> &bull; No API key input<br> &bull; No personal data required until meaningful value is demonstrated</p> <h3>Project Browser parity</h3> <p>The same flow applies if the user installs an AI Recipe later via Project Browser.</p> <h3>Impact for AI Recipe Creators</h3> <p>No special configuration is required.</p> <p>Anonymous onboarding will be the default when including the amazee.ai AI Provider in a Recipe.</p> <p>This ensures consistent UX across Recipes written by different contributors.</p> <h3>Notes on Provider Ecosystem</h3> <p>This pattern is intended to be non-exclusive. Other AI Providers are welcome to deliver the same onboarding model.</p> <p>The goal: ensure AI in Drupal CMS always works immediately.</p> <h3>Acceptance Criteria</h3> <p>Minimum for Drupal CMS 2.0<br> &bull; If an AI Recipe includes an AI Provider, the provider is auto-installed with no blocking UI<br> &bull; Anonymous AI usage is enabled on first run<br> &bull; User receives clear notification and CTA when free credits are exhausted<br> &bull; Trial signup path is available and functional<br> &bull; Works both during installation and via Project Browser</p> <p>Future enhancements (optional)<br> &bull; Installer UX to select preferred AI Provider<br> &bull; Shared UX pattern for all Providers<br> &bull; Better UI for communicating credit usage</p> <p><img src="https://www.drupal.org/files/issues/2025-11-05/Drupal%20CMS%20%2B%20amazee%20provider%20for%20recipes%20simplified.jpg" alt="visual description of the text above."></p> > Related issue: [Issue #3567008](https://www.drupal.org/node/3567008) > Related issue: [Issue #3555869](https://www.drupal.org/node/3555869)