Ability reference
Every operation an AI client can call, grouped by the module that registers it. 1134 abilities across 55 modules. Each entry carries the label and description the plugin itself ships, generated from source so this page cannot describe something the product does not do.
A module only registers when its companion plugin is present and, for Pro modules, a licence is active. The active safety profile then decides which of its abilities appear in the agent’s tool list at all.
How to read this reference
Every module page splits its abilities into three sections, because the difference between them is the difference between a call you can let an agent make unattended and one you should not. 483 of the 1134 abilities are reads: they inspect state, return it, and change nothing, so they stay available in every safety profile including Read Only, and they are not rate limited. Writes create or update something and are gated by both the profile and the WordPress capabilities of the user behind the connection, at a ceiling of 120 write calls per minute per credential. The remaining 255 are marked destructive in the plugin source, which means WPPilot refuses the call unless it carries an explicit confirmation flag, every single time, with no session-wide way to opt out of that prompt.
The ability name in the left column is the exact string an agent calls, so it is also what appears in the change ledger and in an approval request. The description beside it is the one the plugin registers with WordPress: it is what the model reads when it decides which tool to use, and it is reproduced here verbatim rather than rewritten, which is why some entries read like API contracts rather than documentation.
104 abilities ship in WPPilot Free and register on every install. The rest belong to Pro modules, which load only when their companion plugin is detected and a licence is active. If a module is missing on a live site, the fastest answer is the integration health report described in troubleshooting, not this page: the registry on the installed site is always the authority, and this reference is generated from the shipped source at build time.
Why this page is generated
A hand-maintained tool list is wrong within two releases. Somebody renames an ability, somebody else ships a module, and the documentation keeps describing a product that no longer exists, which is worse than no documentation because a reader has no way to tell which half is stale. This page is built from the same registration calls the plugin makes at runtime, so a capability appears here when it ships and disappears when it is removed, with no editorial step in between that could forget.
The trade-off is tone. These descriptions were written for a model choosing between tools, not for a person browsing, so they read like contracts and occasionally mention parameter names that mean nothing without the schema beside them. That is deliberate: paraphrasing them into friendlier prose would put a second, subtly different description of every ability into the world, and the one the model reads would no longer be the one you read. For a guided introduction to any module, its integration page covers the same ground as workflows rather than as a contract.
One thing this page cannot tell you is what is available on your site. A module registers only when its dependency is present and, for Pro, a licence is active, and the safety profile then decides which of its abilities reach the agent’s tool list at all. Two sites running the same WPPilot version can expose very different surfaces, which is intended. Treat this as the catalogue of what can exist, and the installed site’s own registry as the record of what does.
WPPilot Free
104 abilities
The core WordPress surface every install gets: posts, pages, custom post types, taxonomies, media, comments, revisions, menus, users and allowlisted settings. Nothing here needs a licence or a companion plugin, and it is the set an agent falls back to when no specialised module matches the request.
Page builders
366 abilities
Builder-native document and element operations for Elementor, Bricks, Divi, Oxygen, Breakdance, Beaver Builder, WPBakery, Etch and Mosaic. Each builder stores its own structured tree rather than plain post content, so these modules read the real schema before proposing a change instead of writing markup the editor cannot reopen.
Themes and blocks
145 abilities
Block libraries and theme frameworks: GenerateBlocks, Kadence Blocks, Spectra, Astra, GeneratePress, Kadence, OceanWP, Avada and the block-theme bridge. They expose block names, attribute schemas, global styles and template parts so generated layouts match what the installed theme actually supports.
Content modelling
157 abilities
Custom field and content-structure plugins, ACF, ACPT, JetEngine, Meta Box and Pods. Field groups, post types, taxonomies and option pages are read as typed definitions, which is what lets an agent write values that validate rather than guessing at meta keys.
Forms
162 abilities
WPForms, Gravity Forms, Fluent Forms, Formidable, Contact Form 7 and Ninja Forms. Field discovery, form creation, notification settings and entry reads, with the submission and confirmation paths left to be verified in the plugin itself after a change.
SEO
46 abilities
Yoast, Rank Math, AIOSEO and SEOPress. Titles, meta descriptions, canonical URLs, robots directives, schema settings and redirects are read and written through each plugin's own storage, so nothing bypasses the SEO plugin that owns the output.
Commerce
55 abilities
WooCommerce products, variations, attributes, categories, orders, coupons and store settings. Catalogue work is the largest single module in the registry, and every write is still bound by the safety profile and the connected user's shop capabilities.
Multilingual
33 abilities
Polylang and Weglot. Language configuration, translation links between posts, and the state of a translated page, so a multilingual site is treated as one connected set of content rather than unrelated duplicates.
Events and membership
27 abilities
The Events Calendar, Paid Memberships Pro, Tutor LMS and BuddyPress. Events, venues, membership levels, courses, lessons and community objects, the areas where a careless write affects people's access rather than just a page's appearance.
Developer tools
11 abilities
Code Snippets, Dynamic Shortcodes and Bricksforge. These reach the parts of a site that execute code, so they are the first abilities a restrictive safety profile withholds and the clearest case for a staging site.
Platform
28 abilities
Diagnostics, integration health, the change ledger, rollback, approvals and agent memory. This group answers what WPPilot itself is doing: which modules loaded, what an agent changed, what is waiting for a human, and what it is allowed to remember.