---
title: "WordPress Abilities API and AI Connectors: What Site Owners Should Know"
description: "The WordPress Abilities API and AI Connectors in plain English: what your plugins expose, who can run it, where AI keys are stored, and what to lock down."
url: "https://skybootstrap.com/wordpress-abilities-api/"
canonical_url: "https://skybootstrap.com/wordpress-abilities-api/"
date: "2026-10-28T21:57:00+06:00"
modified: "2026-10-28T13:57:59+06:00"
author: Skybootstrap Team
type: article
site: SkyBootstrap
language: en-US
---

# WordPress Abilities API and AI Connectors: What Site Owners Should Know

The WordPress Abilities API is a list of actions your site can perform for software and AI agents, from “get site info” to “change SEO settings”, each with its own permission check. You don’t have to install anything to have it. On our WordPress 7.1.3 test site, two common SEO plugins had already registered 42 abilities between them. Of the site’s 45 abilities, 15 could make changes, from SEO settings to robots.txt rules.

This guide is for site owners rather than developers. It covers what’s on your site, who can use it, how AI tools connect, and where WordPress keeps your AI keys, with what we found when we tested each one. Short version: nothing here runs on its own, so the real question is which accounts and passwords can reach it.

## What is the WordPress Abilities API?

The Abilities API, added in WordPress 6.9, is a registry of named actions that core, plugins and themes declare. Each comes with an input format and a permission check, so software and AI agents can find and run them without a custom integration.

An ability is one of those actions, such as `core/get-site-info` or a plugin’s “update robots.txt rule”.

Each ability comes with a few extra parts. A permission callback is the check that decides which users may run it, using the same roles and capabilities as the rest of WordPress. Annotations are flags the plugin author sets, such as “read-only” or “destructive”, to tell callers what the ability does. WordPress treats them as hints and doesn’t check them, so “read-only” is the author’s word, not a lock.

Abilities a plugin opens to the REST API can be listed and run at `/wp-json/wp-abilities/v1/`. Seeing the list needs a logged-in account; whether an ability can be run is decided by that ability’s own permission check.

WordPress 7.0, released in May 2026, built on it. It added the AI Client, which the WordPress 7.0 Field Guide describes as “a central interface that lets plugins communicate with generative AI models”. It also added AI Connectors for storing provider keys, and a JavaScript version of the Abilities API. A proposal for 7.1 adds read-only core abilities for settings, content and users. But our 7.1.3 test site still registered only the original three, so check your own list rather than a changelog.

## Which abilities does your site already have?

Probably more than you think: our test site with Rank Math and AIOSEO had 45 abilities, 42 of them from the two SEO plugins, and 15 of the 45 can make changes. Core itself registers only three, all read-only.

| Source | Abilities | Read-only | Can change things |
| --- | --- | --- | --- |
| WordPress core | 3 | 3 | 0 |
| Rank Math 1.0.280 | 29 | 18 | 11 |
| AIOSEO 5.0.3 | 13 | 9 | 4 |

The ones that change things include Rank Math’s “Fix site SEO” and its settings tools for sitemaps, breadcrumbs and module switches. On the AIOSEO side, they include updating a post’s SEO data and adding, editing or deleting robots.txt rules, the last one marked destructive. We only tested Rank Math and AIOSEO; other SEO plugins may register none or many, so check your own list. Other plugins are joining in too: WP Mail SMTP and WPForms register their own, and WPForms can optionally allow writes.

Every one of the 45 was available over the REST API, and every plugin ability was flagged for AI tools to use through the MCP Adapter. To see your own list, save this file as `list-abilities.php` and run `wp eval-file list-abilities.php` from your site’s folder with WP-CLI, the WordPress command-line tool:

```
<?php
// List every ability on this site: its name, whether it is marked read-only, and whether it is marked destructive.
// Run with WP-CLI from the site folder: wp eval-file list-abilities.php
foreach ( wp_get_abilities() as $ability ) {
$meta = $ability->get_meta();
$notes = $meta['annotations'] ?? array();
printf(
"%-45s %-10s %s\n",
$ability->get_name(),
! empty( $notes['readonly'] ) ? 'read-only' : 'CHANGES',
! empty( $notes['destructive'] ) ? 'destructive' : ''
);
}
```

On our test site it printed all 45, each marked read-only or CHANGES. CHANGES means the author didn’t mark the ability read-only, so treat it as able to change something. If you don’t have WP-CLI, ask your host or developer to run it for you.

## Who can see and run abilities?

On our test site, nobody without a login could see or run anything. Any logged-in user, down to subscriber, could see the full list, and only users with the right role could run each one. WordPress always requires a login to see the list, but whether an ability runs without one is up to the plugin that registered it. Here is what happened when we tried each kind of account over the REST API:

- Not logged in: every request was refused, both the list and every ability.
- Subscriber: saw all 45 abilities, with their descriptions and input formats, but could run only one, which returns their own profile.
- Administrator: could run all 45. Even the read-only `core/get-site-info` returns the site’s admin email address.

The subscriber result is worth a second look. Running is locked down, but the list itself tells any logged-in user which SEO plugins you run and what each ability accepts. On a site with open registration or many customer accounts, that’s more than most owners expect to share.

An application password is a separate password WordPress issues for one app or script, which you can revoke without changing your main login. It’s how external tools, including AI agents, sign in. By default WordPress only offers them on sites served over HTTPS, or on a site whose environment type is set to “local”. A plugin or your host can switch them on or off. Our test site ran on plain HTTP, so application passwords were refused until we set it to local for testing, then put it back.

To see what a write ability can do, we used an administrator’s application password to call AIOSEO’s “add robots.txt rule” ability and block GPTBot from the whole site. The call returned success, but robots.txt didn’t change, because AIOSEO’s custom robots.txt setting was switched off. Once we switched it on, the new rule appeared.

Two lessons follow. An agent with admin access can rewrite how crawlers see your site in one request, and a “success” reply doesn’t prove anything changed. We deleted the rule with the matching ability afterwards.

## How AI agents connect: the MCP Adapter

Through the MCP Adapter plugin, which turns abilities into tools an AI app such as Claude or Cursor can call, signed in as a WordPress user, usually with an application password. MCP, the Model Context Protocol, is a standard way for AI apps to discover and call outside tools.

The adapter isn’t part of core; you install it as a plugin. Its default server only offers abilities whose authors marked them for MCP, which every plugin ability on our test site was. It connects either locally through WP-CLI or over HTTP with an application password.

The AI app gets three tools from it: one to discover abilities, one to read an ability’s details and one to run it. That’s enough for an agent to find “add robots.txt rule” on its own and call it. We didn’t install it on our test site, so this section follows [WordPress’s announcement of the adapter](https://developer.wordpress.org/news/2026/02/from-abilities-to-ai-agents-introducing-the-wordpress-mcp-adapter/).

The same post puts the risk plainly: “Because MCP clients act as logged-in WordPress users, always treat them as part of your application surface area.”

It recommends a dedicated user with limited capabilities for AI access and read-only abilities on any public endpoint. In practice, an agent can do whatever the account it signs in with can do.

## What are WordPress AI Connectors, and where do API keys go?

Connectors, added in WordPress 7.0 under **Settings → Connectors**, hold the API keys plugins use to call AI providers; a key typed into that screen is saved in your database as plain text. Only administrators can open the screen, and nothing is stored until you install a provider plugin and add a key.

![The WordPress Settings > Connectors screen listing Anthropic, Google and OpenAI with Install buttons, below a banner offering the AI plugin](https://skybootstrap.com/wp-content/uploads/2026/10/wordpress-abilities-api-connectors-screen.webp "Settings → Connectors on our WordPress 7.1.3 test site, with no provider plugins installed yet.")

WordPress lists Anthropic, Google and OpenAI, but each needs its provider plugin before it can be used, which is what the Install buttons add. Once a key is set, any plugin that uses the [WordPress AI Client](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/) can send prompts to that provider on your account.

WordPress looks for each key in three places, in order: an environment variable, then a PHP constant, then the database. When we saved a test key straight into that database option, it was stored exactly as typed. WordPress only hides it when showing it back, as dots followed by the last four characters.

[WPShout also notes](https://wpshout.com/wordpress-ai-connectors-api/) that core has no spend limit on AI calls. Anyone who can read your database, or a backup of it, can read a key stored there. A constant in `wp-config.php` keeps it out of the database. Add it above the line that reads “That’s all, stop editing!”, and use `GOOGLE_API_KEY` or `OPENAI_API_KEY` for the other two providers:

```
define( 'ANTHROPIC_API_KEY', 'your-key-here' );
```

## Frequently Asked Questions

### Do I need to install anything to use the Abilities API?

No. The Abilities API has been part of WordPress since version 6.9, and plugins register abilities on their own. On our 7.1.3 test site, Rank Math and AIOSEO had already registered 42 of the site’s 45 abilities, and 15 of those 45 could make changes, from SEO settings to robots.txt rules.

### Can someone run WordPress abilities without logging in?

On our test site, nobody without a login could see or run anything. WordPress always requires a login to list abilities, but whether a given ability runs without one is up to the plugin that registered it. Any logged-in user down to subscriber could see the full list, and only users with the right role could run each one.

### Where should AI API keys be stored in WordPress?

Keep them in wp-config.php where you can. A key typed into Settings, Connectors, added in WordPress 7.0, is saved in your database as plain text. Only administrators can open that screen, and nothing is stored until you install a provider plugin and add a key, so check the screen after installing any AI plugin.

## What should site owners do now?

As a site owner, list your abilities, give any AI agent its own low-privilege account, keep AI keys in `wp-config.php`, and switch off plugin features you don’t want agents to reach. In order:

1. Run the list script above and note every ability marked CHANGES. Those can change your site if an account is misused; the read-only ones can still reveal details such as your admin email address.
2. Give each AI agent or tool its own WordPress user with the lowest role that does the job, plus its own application password. Avoid giving an agent an administrator account; if a job truly needs one, create a separate admin user for it and revoke its application password when the job is done.
3. Review application passwords under **Users → Profile** for your own account, and on each user’s edit screen under **Users → All Users** for everyone else, and revoke any you don’t recognise.
4. Move AI provider keys out of the database: remove each key on the Connectors screen, then add it as a `wp-config.php` constant or one of your host’s environment variables. WordPress uses a constant or environment variable before the database, but never deletes the old copy for you.
5. Set a spending limit with your AI provider, since WordPress won’t.
6. If you don’t want agents near a plugin’s write features, check that plugin’s settings or ask its developer how to turn its abilities off. WordPress itself has no screen for switching abilities off; plugins control their own.

If you don’t use AI tools with your site at all, steps 1 and 3 are enough for now. On our test site nothing ran without a logged-in account, so the risk came from accounts and passwords, not from the API existing. A plugin could still open an ability to visitors, which is one more reason to rerun step 1 after installing plugins.

The Abilities API is about agents doing things on your site. Letting them read it efficiently is a separate job. [Our HTML vs Markdown token study](https://skybootstrap.com/html-to-markdown-for-llm/) shows what serving Markdown saves, and [our tutorial on serving Markdown versions of pages](https://skybootstrap.com/serve-markdown-to-ai-agents/) shows how to set it up. If you’d rather not set it up by hand, [our Skyboot AI Markdown plugin](https://skybootstrap.com/skyboot-ai-markdown/) does that reading side for you: [a Markdown version of every page and an llms.txt that lists them](https://skybootstrap.com/docs/skyboot-ai-markdown/llms-txt-and-markdown/). It only serves content for agents to read.

[Our guide to making WordPress readable for AI, starting with llms.txt](https://skybootstrap.com/llms-txt-wordpress/), covers the rest. Store owners should also read [how to prepare WooCommerce product pages for AI shopping agents](https://skybootstrap.com/ai-shopping-agents-woocommerce/).