Plugins · Overview

Neuroon offers two paths for connecting your shop to the semantic engine:

1. Official plugins for platforms with their own ecosystem (WordPress).
2. Custom integration server-to-server when your stack is proprietary or does not fit a plugin (Next.js, Nuxt, Java monolith, etc.).

This page summarizes the capability matrix and points you to the right guide.

Capability matrix

Capability	WordPress · neuroon-search v0.8.4	Custom · script + server-to-server
Distribution	Official plugin (ZIP / wp.org pending)	CDN loader + your backend
Domain verification	Automated (Settings tab)	Manual via API
Product sync	Automatic (WooCommerce hooks)	Your cron / webhook
Cart bridge	Inline (WC events → neuroon:cart-update)	Manual dispatch
Conversion tracking	Server-side from WC checkout (recommended)	Server-side from your backend
Widget token	Signed server-side and cached in options + transient	Your cache (Redis, KV, memory, etc.)
Status	Maintained by Neuroon	Self-managed

Shopify is not supported as a plugin at this time. Shopify projects must use the custom path (CDN loader + server-to-server token issuance from a private app or an intermediate backend).

Two WordPress plugins, two different products

There are two WordPress plugins that share a domain but address different use cases:

Plugin	Version	Purpose
neuroon-search	0.8.4	Semantic search + catalog sync + embeddable widget. This is the piece these guides document.
neuroon-agentic-commerce	0.1.0	Universal Commerce Protocol (UCP) so AI agents (Google Search AI Mode, Gemini, ChatGPT) can discover and buy from your shop. Separate product, documented elsewhere.

Which one to choose

• You have WooCommerce: use plugins/wordpress/installation. It is the shortest path (automatic sync, cart bridge included).
• Your stack is proprietary (Next.js, Nuxt, Rails, Spring, etc.): start with plugins/custom/standalone and issue tokens server-to-server following the matching recipe.

Common public endpoints

Regardless of the path, every integration talks to the same small set of endpoints:

POST/api/plugin/shops/{shopId}/products/sync

POST/api/plugin/shops/{shopId}/verify

POST/api/plugin/shops/{shopId}/track/conversion

The Widget Token is signed by your own server locally using the Shop API Key as HMAC secret — it is not an endpoint. See Recipe · Server-to-server token.

If your platform is not listed above, the server-to-server pattern covers any stack: see recipes/server-to-server-token.

Support and contributions

• Report issues on the public tracker or from the dashboard.
• For critical custom integrations, contact the team (see resources/support).