[robelsust]

Description

Trac Ticket: https://core.trac.wordpress.org/ticket/64924

This PR introduces the has_ai_credentials(): bool helper function to WordPress core.

Plugins and core AI experiments frequently need to check whether a site has any AI credentials configured before enabling AI features or rendering settings that require an active AI provider.

Changes

• Adds has_ai_credentials(): bool to wp-includes/connectors.php.
• Iterates registered connectors of type ai_provider and inspects their configured authentication settings using _wp_connectors_get_api_key_source() across database options, constants, and environment variables.
• Respects wp_supports_ai().
• Adds the wp_has_ai_credentials filter and backward-compatible wpai_has_ai_credentials filter.
• Adds dedicated unit tests in tests/phpunit/tests/connectors/hasAiCredentials.php.

Props @therssoftware

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props therssoftware.

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

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.