REST Fallback
The fallback of last resort: your AI reaches any plugin's REST routes directly, under your own permissions.
When nothing else covers a plugin, your AI can still reach its REST routes. The REST fallback lets it drive any WordPress plugin that registers REST routes, discovering your site's namespaces automatically. It is always on, and it is the last resort: a custom ability is the better path once you have one.
BuildPress ships built-in abilities for WordPress core, Elementor, JetEngine, ACF, Figma, and a bundled GSAP engine, and it can write a custom ability for any other plugin or theme on your site. The REST fallback sits underneath both. See the abilities overview for the full set.
Prefer a custom ability
A custom ability's tools are checked on your site and its writes read themselves back, so a change that quietly did nothing is caught. The REST fallback has none of that: it dispatches the call you asked for and reports the response. Ask your AI to study the plugin first, and keep the fallback for one-off reads and plugins you do not use often.
How it works
The fallback gives your AI three universal moves. It does not need to know a plugin in advance. It learns your site at runtime, then dispatches the call you asked for.
- 1
Discover the namespaces
Your AI lists the reachable non-native REST namespaces on your site, so it can see which plugins expose a controllable API.
- 2
Inspect one namespace
Your AI reads the routes and the methods each route supports inside a chosen namespace, so it knows what reads and writes are available.
- 3
Dispatch a call
Your AI makes the call by namespace, route, method, and params, then reads the result back to confirm it worked.
Calls run internally through WordPress core under your own capabilities. There is no external HTTP round-trip back into your site, and every call is written to the audit log. WooCommerce, for example, lives under the wc/v3 namespace, so your AI can reach products, categories, and settings there.
Native plugins stay on their own tools
Writes against WordPress core, Elementor, JetEngine, ACF, and BuildPress always route to the dedicated tools instead of the fallback, so you keep the verification and guardrails those abilities provide. Native reads are still allowed through the fallback. There is nothing to configure: the fallback is on for every site, and your WordPress account's permissions are the limit on what it can do.
Trigger the AI
You never call a route by hand. Describe what you want in plain English and your AI discovers, inspects, and dispatches for you. Paste any of these:
- "List my WooCommerce products and tell me which are out of stock."
- "What WPForms or Gravity Forms forms exist, and how many entries does the contact form have?"
- "Read my Yoast SEO settings and tell me which pages are missing a meta description."
- "See what plugins on my site expose a REST API the AI can reach."
WooCommerce has no built-in ability, so it runs through a custom ability or, before you write one, the fallback. For a full storefront walkthrough, see Build an ecommerce store.
Requirements
- The target plugin installed, active, and registering REST routes (WooCommerce, Gravity Forms, WPForms, Yoast, Rank Math, and others).
- Your own WordPress capabilities still apply: the fallback never lets your AI do anything your account cannot do.