WordPress 7 AI MAY 2026
WordPress 7.0 introduces three new core APIs — AI Client, Connectors, and Abilities — that standardize how plugins talk to AI providers and how AI agents call back into the site. PressBot is the AI operations layer that sits on top: audit, explain, plan, approve, apply, report. Works on WordPress 6.2+ today; treats WP 7's new APIs as progressive integration targets, not dependencies.
What changed in WordPress 7
WordPress 7.0 gives the ecosystem shared primitives instead of every plugin inventing its own provider setup. Three new APIs ship together. The shape of WordPress AI work changes around them.
php-ai-client
A provider-agnostic route for prompts and model calls. Plugins can ship one integration that targets Claude, GPT, or Gemini through a single Core-managed interface instead of writing four provider clients each.
Connectors API
A shared credential surface for AI providers. Site owners enter an API key once at the Core level, and any plugin that opts in can request access through a permission flow — instead of four separate “paste your Anthropic key here” settings screens.
Abilities API
A way for plugins to describe typed, discoverable, callable capabilities to AI clients in a structured way. An external agent can ask “what can this site do?” and get a real machine-readable answer.
What PressBot does today
WordPress 7 standardizes how AI gets called. PressBot standardizes what gets done with it — the day-to-day operations a site actually needs an AI to perform. Six phases, all repeatable, all auditable.
Scan posts, plugins, security checks, AI Visibility scores, content gaps. Evidence first, not vibes.
Translate findings into plain English. Why the audit flagged it, what's at risk, what fixing it costs.
Group fixable items into Trusted Plans with per-action before/after diffs — staged, not auto-applied.
You click apply. Destructive actions ask first. Restore support undoes the writes that support it.
Every audit, plan, and write is logged. Agencies hand the report to clients; site owners hand it to their future selves.
Two layers, not two products
The new Core APIs and PressBot are complementary, not competing. Core ships the shared primitives. PressBot ships the workflows that put those primitives to work.
WordPress 7 Core
Shared, low-level primitives that the whole plugin ecosystem can build against. Stops everyone from re-implementing the same provider clients.
PressBot
An AI operations layer for WordPress: audit, explain, plan, approve, apply, report. Aimed at recurring site work, not generic editor AI.
Compatibility
PressBot is not a WordPress 7 launch product. It runs on WordPress 6.2+ today and treats the new Core APIs as progressive integration targets — we plug into them as they stabilize, without making 7.0 a hard dependency.
The plugin works against WordPress 6.2+ with PressBot's own BYOK providers. You do not need to upgrade to 7.0 to install, configure, or use PressBot. The free chatbot, the Pro agent, RAG, and AI Visibility all ship without depending on the new Core APIs.
On WordPress 7.0+ installs, PressBot can recognise Core AI APIs as they become available. We treat AI Client, Connectors, and Abilities as integration targets, not dependencies — you choose when to opt in, plugin by plugin, ability by ability.
PressBot's BYOK providers (Anthropic, OpenAI, Google, DeepSeek for the public chat) keep working whether or not you wire up the Connectors API. We do not import raw Connector credentials; your encrypted PressBot keys stay separate.
Common questions about WordPress 7 AI
Quick answers to what most site owners and agencies ask now that WordPress 7 has shipped.
No. PressBot works on WordPress 6.2 and up. The plugin uses its own BYOK provider clients (Anthropic, OpenAI, Google, DeepSeek for the public chat) and its own tool-calling stack, so nothing on the WordPress 7 AI surface is a hard requirement.
If you do upgrade to WordPress 7, PressBot can progressively integrate with the new Core APIs — but that is opt-in, not automatic.
No. The official WordPress AI plugin from the AI team focuses on editor-facing generic AI (alt text, content suggestions, broad experiments). PressBot is aimed somewhere else: AI operations for WordPress — evidence, approvals, reporting, and recurring workflows that site owners and agencies repeat.
The two are complementary, not competing.
Not as a hard dependency, no. PressBot ships its own provider clients today and stays in control of cost, model selection, and per-agent routing. On WordPress 7+ installs we treat the AI Client as an integration target — usable for text calls when Core support is available — without taking it on as a runtime requirement.
The Connectors API lets WordPress own a shared credential surface that plugins can request access to. PressBot keeps its encrypted BYOK keys separate by default — we do not import raw Connector credentials. On WordPress 7+ we can detect Connector availability and route appropriate read-side calls through it, but the Pro admin agent's 99 tool workflows continue to use PressBot's own keys for predictability.
That is the most interesting one. Today PressBot ships 99 native tools spanning content, security, WooCommerce, Yoast SEO, and ACF. As more plugins register their own abilities through the WP 7 Abilities API, PressBot can call them just like its native tools — same review-required workflow, same Trusted Plans, same restore support. The ecosystem matures, PressBot inherits the new surface area.
They coexist. The official plugin sits inside the editor; PressBot's operator surface lives in the chat widget (visitor side) and the WordPress admin chat (admin side). Different scopes, different daily-use moments. If the official plugin requests a Connector credential, PressBot does not touch it.
No. The free tier is still the full visitor chatbot (including External Knowledge / RAG). PressBot Pro starts at $99/year for a single site and unlocks the admin agent, Plugin Guardian, Shield, Telegram bridge, GA4, lead capture, AI Visibility, and the full 99-tool MCP server. See the Pro page for the full breakdown.
Progressively, as the APIs settle. We do not want to ship a half-baked Core integration the week of 7.0 launch; the safer path is to wait for each API to stabilize, then plug PressBot's existing workflows into it. Track the changelog for the rollout.
WordPress 7 AI · the operator layer
WordPress 7 is the foundation. PressBot is what runs on it. Install the free chatbot today on WordPress 6.2+ — you do not need to wait for 7.0, and you will inherit the new Core APIs progressively as they stabilize.