I tested it by installing https://github.com/saarnilauri/ai-provider-for-mistral from the zip file included on the relase page:

One implementation note to keep in mind regarding our direction is that the API key is currently auto-generated,so allow customization if needed. This is what I am currently passing to the client, which will likely evolve, but we could change it before WP 7.0 Beta 3:

<script
  id="wp-script-module-data-connectors-wp-admin"
  type="application/json"
>
  {
    "providers": {
      "google": {
        "name": "Google",
        "description": "Content generation, translation, and vision with Google's Gemini.",
        "credentialsUrl": "https://aistudio.google.com/app/api-keys",
        "settings": ["connectors_ai_google_api_key"]
      },
      "openai": {
        "name": "OpenAI",
        "description": "Text, image, and code generation with GPT and DALL-E.",
        "credentialsUrl": "https://platform.openai.com/api-keys",
        "settings": ["connectors_ai_openai_api_key"]
      },
      "anthropic": {
        "name": "Anthropic",
        "description": "Writing, research, and analysis with Claude.",
        "credentialsUrl": "https://console.anthropic.com/settings/keys",
        "settings": ["connectors_ai_anthropic_api_key"]
      },
      "mistral": {
        "name": "AI Provider for Mistral",
        "description": "",
        "credentialsUrl": "https://console.mistral.ai/api-keys",
        "settings": ["connectors_ai_mistral_api_key"]
      }
    }
  }
</script>

Size Change: 0 B

Total Size: 6.87 MB

_{compressed-size-action}

After debugging the issue of mistral and xAI not appearing seems to be because when both Gutenberg and latest beta are active, the screen code that seems to be loaded is the latest beta not Gutenberg not gutenberg. That should be fixed on a different PR when I tested with WordPress develop at WordPress/wordpress-develop@33688bb things worked:

There is an issue where for Grok it says install while it is already installed but other than that things loaded well.

Flaky tests detected in 5248929.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/22570185250
📝 Reported issues:

• [Flaky Test] Navigates the list via UP/DOWN arrow keys from action buttons #76008 in /test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: raftaar1191 <raftaar1191@git.wordpress.org>
Co-authored-by: jorgefilipecosta <jorgefilipecosta@git.wordpress.org>
Co-authored-by: felixarntz <flixos90@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Addressed feedback and applied refactorings

PHP (default-connectors.php):

• Grouped authentication fields (method, credentials_url, setting_name) into an authentication sub-object, eliminating the redundant settings array
• Renamed _gutenberg_get_provider_settings → _gutenberg_get_connector_settings and updated all consumers
• Standardized terminology: "connector" for domain concepts, "provider" only for AI Client SDK references
• Moved getCredentialsUrl() inside the if ($is_api_key) branch
• Refactored main function for readability: explicit field assignments instead of array_merge/array_filter, folded loops
• Updated docblocks to reflect new structure

TSX (default-connectors.tsx):

• ConnectorAuthentication is now a discriminated union ('api_key' | 'none')
• Renamed types/variables from "provider" to "connector" throughout
• Connector names use type-based namespace: ai-provider/{id} instead of core/{id}
• Renamed ApiKeyProviderConnector → ApiKeyConnector; moved helpLabel derivation inside the component
• Used new URL().hostname instead of regex for extracting help label
• Removed explicit ConnectorRenderProps annotation on render callback (inferred from registerConnector)

New structure passed to the client from the server:

<script id="wp-script-module-data-connectors-wp-admin" type="application/json">
{
  "connectors": {
    "google": {
      "name": "Google",
      "description": "Content generation, translation, and vision with Google's Gemini.",
      "type": "ai_provider",
      "authentication": {
        "method": "api_key",
        "settingName": "connectors_ai_google_api_key",
        "credentialsUrl": "https://aistudio.google.com/app/api-keys"
      }
    },
    "openai": {
      "name": "OpenAI",
      "description": "Text, image, and code generation with GPT and DALL-E.",
      "type": "ai_provider",
      "authentication": {
        "method": "api_key",
        "settingName": "connectors_ai_openai_api_key",
        "credentialsUrl": "https://platform.openai.com/api-keys"
      }
    },
    "anthropic": {
      "name": "Anthropic",
      "description": "Writing, research, and analysis with Claude.",
      "type": "ai_provider",
      "authentication": {
        "method": "api_key",
        "settingName": "connectors_ai_anthropic_api_key",
        "credentialsUrl": "https://console.anthropic.com/settings/keys"
      }
    },
    "grok": {
      "name": "Grok (xAI)",
      "description": "",
      "type": "ai_provider",
      "authentication": {
        "method": "api_key",
        "settingName": "connectors_ai_grok_api_key",
        "credentialsUrl": "https://console.x.ai/"
      }
    },
    "mistral": {
      "name": "AI Provider for Mistral",
      "description": "",
      "type": "ai_provider",
      "authentication": {
        "method": "api_key",
        "settingName": "connectors_ai_mistral_api_key",
        "credentialsUrl": "https://console.mistral.ai/api-keys"
      }
    }
  }
}
</script>

Still open for follow-up PRs

1. Provider logos from registry — need a way for AI providers to register and expose logos. Currently hardcoded in CONNECTOR_LOGOS (Connectors: Dynamically register providers from WP AI Client registry #76014 (comment)).
2. Provider descriptions — the hardcoded descriptions are too similar across providers and highlight features that overlap. Need better, more distinct descriptions — possibly sourced from the providers themselves through a custom wp.org endpoint for featured connectors (Connectors: Dynamically register providers from WP AI Client registry #76014 (comment), Connectors: Dynamically register providers from WP AI Client registry #76014 (comment), Connectors: Dynamically register providers from WP AI Client registry #76014 (comment)).

I think I addressed all the feedback raised after the last round of changes.

I just cherry-picked this PR to the wp/7.0 branch to get it included in the next release: 3763f32