Skip to main content
Generatify registers its endpoints under the generatify/v1 namespace. Most of them exist to serve the plugin’s own admin screens and front-end scripts, so treat them as an internal API rather than a versioned public contract. The exception is the WebMCP group, which is designed to be called by something other than the plugin.

​
Authentication

Administrative endpoints require a capability and a valid X-WP-Nonce header. Front-end endpoints are public because visitors are not logged in.
Do not request a nonce from /helpdesk-agent/nonce and reuse it for an administrative call. That route re-resolves the user from the cookie so that logged-in visitors get a nonce bound to themselves rather than to user 0, and it is deliberately never cached.

​
Endpoints

​
Settings

​
Update settings

​
endpoint
Merges the supplied values over the stored settings. Send only the keys you want to change.
Fires generatify_settings_update:before and :after around the write.
This endpoint can write API keys, since they are ordinary settings. Anyone who can call it with manage_options can read and replace your provider credentials.
There is no GET counterpart. Read settings in PHP with get_option('generatify_settings').

​
Copilot

​
endpoint
Runs a copilot turn, including the tool loop that reads your site and prepares any changes. Requires manage_options.
​
endpoint
Reports progress for a running request, so the interface can show what the assistant is doing rather than a blank spinner.
​
endpoint
Backs the mention control in the prompt box, returning content matching a query. Requires edit_posts.

​
Content generation

All five generation routes require edit_posts and a connected provider.
​
endpoint
Reports whether any connected key offers an image model. The editor calls this before showing the featured image control, which is why you see a specific message rather than a failure when only Claude or Kimi is connected.

​
Helpdesk agent

​
endpoint
Returns a fresh REST nonce for the front-end widget. Never cached.
​
endpoint
Sends a contact form submission by email. The recipient, subject, body, and headers are all filterable.
​
endpoint
Answers a visitor message in conversation mode. Only registered when Pro is active, which is why conversation mode does nothing on a free install.

​
Browser AI tools (WebMCP)

Registered only when WebMCP Tools is enabled, under generatify/v1/webmcp. All are public, because a browser agent acts as an anonymous visitor. Results are capped at 20 rows. With WooCommerce active:
/webmcp/cart/add is the only route in the plugin that changes anything without authentication, and it is constrained accordingly:
​
generatify_not_found
No published product with that ID.
​
generatify_not_purchasable
The product is not purchasable, or is not a simple product. Variable products are refused because a variant cannot be chosen from here.
​
generatify_out_of_stock
Not enough stock for the requested quantity.
​
generatify_no_cart
The cart is not available.

What this exposes, and whether to enable it

The reasoning behind the limits, and when to leave it off.