Skip to content
BuildPressBeta
Integrations

REST Passthrough

Drive any plugin that exposes REST routes, with you deciding what your AI can touch.

For everything on your site without a dedicated integration, REST passthrough lets your AI drive any WordPress plugin that registers REST routes. WooCommerce, Gravity Forms, WPForms, Yoast, Rank Math, and more all become controllable, and your AI discovers your site's namespaces automatically.

BuildPress ships deep, purpose-built integrations for WordPress core, Elementor, JetEngine, ACF, Figma, and a bundled GSAP engine. REST passthrough covers the rest. It is the catch-all that gives your AI real control of plugins that BuildPress does not target directly. See the integrations overview for the full set.

How it works

Passthrough 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. 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. 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. 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.

Coming soon
The REST API Passthrough card at BuildPress -> Integrations, showing the independent Reads and Writes toggles.

You control reads and writes

Reads and writes are independent toggles at BuildPress -> Integrations -> REST API Passthrough. Turn writes off and your AI stays read-only through passthrough: it can inspect and report on third-party plugin data, but it cannot change it.

Native namespaces are handled differently. Writes against WordPress core, Elementor, JetEngine, ACF, and BuildPress always route to the dedicated tools instead of passthrough, so you keep the verification and guardrails those integrations provide. Native reads are still allowed through passthrough.

Leave writes off by default

Keep the writes toggle off unless you actually want your AI mutating third-party plugin data. Reads are enough to audit forms, settings, and products. Flip writes on only when you are ready for your AI to create or change records, for example when building out a WooCommerce catalog.

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:

  • "Add 5 sample products to my WooCommerce store with prices and categories."
  • "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."
  • "Use the REST passthrough to see what plugins on my site expose an API the AI can control."

WooCommerce has no dedicated integration yet, so it runs entirely through passthrough today. For a full storefront walkthrough, see Build an ecommerce store.

Coming soon
A short walkthrough of your AI discovering the wc/v3 namespace, inspecting product routes, and adding products to a WooCommerce store through passthrough.

Requirements

  • The target plugin installed, active, and registering REST routes (WooCommerce, Gravity Forms, WPForms, Yoast, Rank Math, and others).
  • The reads toggle on for reads, and the writes toggle on for writes (POST, PUT, PATCH, DELETE) at BuildPress -> Integrations.
  • Your own WordPress capabilities still apply: passthrough never lets your AI do anything your account cannot do.
Share