Tag: AI Assistants

A client wanted AI features on his WordPress site and every plugin used a different API. The new WordPress AI Client SDK gives plugins and themes one consistent, WP-native API for multiple providers.

A client spent six months stuck on API plumbing before any AI features shipped. The lesson: build WordPress AI on a proper AI Client SDK, with a standard way to register providers, before chasing features.

A client’s AI prototype broke because their site ran PHP 7.2 while our code used PHP 7.4. Here is how the WordPress Core AI team handles the same version gap, and how to build for it.

A client inherited an AI setup that was really just API calls held together with duct tape, and it kept breaking. Here is the architecture I use instead: provider interfaces and DTOs that let you swap AI models without rewriting everything.

Tying a WordPress site to one AI provider’s SDK makes switching painful later. This walks through an abstraction layer with per-provider adapters so you can change models without rewriting your core code.

A hardcoded AI API key in front-end JavaScript is a security hole and a performance drag. This shows how to move the calls to a WordPress server-side proxy using the REST API and wp_remote_post.

How to add AI to a WordPress site with the WordPress AI Client SDK instead of hardcoded API keys and provider-specific code. Covers setup, credentials, and generating text.

A prep checklist for the Core AI table at WordCamp US Contributor Day: the AI Building Blocks, the main project repos, and the Slack channel, so you can build instead of getting your bearings.

Wiring an AI into WordPress through generic CRUD endpoints got confusing and risky fast. Breaking actions into separate, per-post-type abilities with clear permissions gives the AI the precision it needs.