EcomAIBridge for WooCommerce

Description

Make your store visible to AI.

EcomAIBridge connects your WooCommerce store to AI agents, chatbots, and LLM crawlers. Make your products visible to ChatGPT, Claude, Gemini and other AI tools — and add a built-in AI shopping assistant to your storefront.

Right now, customers are shopping through AI. They ask ChatGPT, Claude, Gemini and Perplexity for product recommendations and buy without ever visiting your store directly. If your store isn’t connected to AI agents through a REST API or chat widget, you’re invisible to them.

What this plugin does

  • Structured Product API — Clean, paginated, filterable JSON endpoints (/ecomaibridge/ai/products.json, /ai/categories.json, etc.) that any AI agent or app can call directly.
  • AI Discovery Manifest — A /.well-known/ai-bridge.json file that describes your store’s endpoints so AI crawlers can auto-discover what’s available.
  • Built-in AI Chat Widget — A floating shopping assistant for your storefront. Connects to Groq (free tier) out of the box, or any OpenAI-compatible endpoint via the Custom provider option.
  • 7-Day Activity Analytics — Lightweight, transient-backed analytics tab showing requests, top searches, missed-opportunity queries, and provider rate-limit hits.

A separate Pro Add-on plugin is available from ecomaibridge.com.

Built Natively for WooCommerce

Install from the WordPress plugin directory like any plugin, activate, and your product API is live instantly. Everything lives inside your WordPress admin — Overview, AI Chat Widget, Analytics, About.

External Services

This plugin can connect to one external LLM service of your choice (Groq by default, or any OpenAI-compatible endpoint via the Custom provider option). It is documented below so you understand exactly what data leaves your site, when, and to whom. The plugin sends no analytics or telemetry, and does not perform any background “phone home” requests for license checks, version pings, or usage tracking.

Groq AI Inference API — required only if you enable the chat widget and use the default Groq provider.

  • Endpoint: https://api.groq.com/openai/v1/chat/completions
  • Purpose: Generate AI chat responses for the storefront chat widget.
  • When called: Each time a visitor sends a message through the chat widget. No request is made if the chat widget is disabled.
  • Data sent: The visitor’s chat message, conversation history for the current session, and a system prompt describing your store. No personally identifiable customer information (name, email, address, payment data) is sent.
  • Authentication: The Groq API key you provide in plugin settings, stored only in your WordPress database and transmitted only as a Bearer token to Groq.
  • Required: You must obtain your own free Groq API key at https://console.groq.com.
  • Terms of Service: https://groq.com/terms-of-use/
  • Privacy Policy: https://groq.com/privacy-policy/

Custom OpenAI-compatible provider — only when you set the provider to “Custom” in admin and configure your own base URL.

  • Endpoint: whatever URL you enter in plugin settings.
  • Purpose, data sent, authentication: same as the Groq behaviour above, but routed to the endpoint you configured. Refer to your chosen provider’s terms and privacy documentation.

Installation

  1. Upload the ecomaibridge-for-woocommerce directory to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugins screen directly.
  2. Activate the plugin through the ‘Plugins’ screen in WordPress.
  3. You will see a new ‘EcomAiBridge’ menu item in your WordPress admin dashboard.
  4. Open the AI Chat Widget tab, paste a Groq API key (free at https://console.groq.com), and enable the widget.

FAQ

Do I have to use Groq?

No. Groq is preconfigured because they offer a free, fast LLM tier that’s easy to set up. The “Custom” provider option lets you point at any OpenAI-compatible endpoint (OpenAI, DeepSeek, Mistral, OpenRouter, Together, Ollama, etc.) by entering your own base URL, model, and API key.

Why do I need an API key?

The chat widget needs an LLM to generate responses. The key is stored only in your own WordPress database and is sent directly from your server to the configured provider — it never passes through any third-party server.

Does this replace WooCommerce default search?

No, EcomAIBridge runs as a layer alongside your store. It provides a conversational AI chat interface for your customers and machine-readable endpoints for external AI agents. It does not overwrite your theme’s default search bar.

Will this slow down my store frontend?

No. The API layer is completely headless and decoupled from your theme. The chat widget script is extremely lightweight and loads asynchronously, meaning zero impact on your page load times.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“EcomAIBridge for WooCommerce” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.0.3

  • Moved the admin screen from a top-level menu to Settings EcomAiBridge to follow the WordPress recommended placement for plugins of this scope.
  • About tab: the companion-plugin link now points to the dedicated upgrade page on ecomaibridge.com and includes the site domain and admin email as query parameters so the form is pre-filled.

1.0.2

  • Restructured the plugin to comply with WordPress.org Plugin Directory Guidelines on trialware and serviceware. Free is now fully self-contained — no extension hooks, no placeholder tabs, no upsell language tied to gated functionality.
  • AI Chat Widget tab: added Model and Base URL fields directly in free, alongside Provider, API Key, and rate-limit settings. Removed the dynamic provider help script.
  • Removed the llms.txt root-file generator. Discovery is now handled solely through the existing /.well-known/ai-bridge.json endpoint.
  • Removed the standalone api_key setting and the Store Settings tab — neither was used by any free endpoint.
  • Removed the placeholder “AI Personality”, “Business Info”, and “Behavior & FAQ” admin tabs (these features live in the separate Pro Add-on plugin and were not functional in free).
  • Renamed the License tab to About; replaced its feature comparison table with a single neutral note about the separate companion plugin.
  • All inline <script> and <style> blocks in admin views replaced with the standard wp_enqueue_* flow.
  • uninstall.php no longer references hardcoded WP_PLUGIN_DIR / WP_CONTENT_DIR constants — it now uses plugin_dir_path( __FILE__ ) and wp_upload_dir() for legacy directory cleanup.
  • Internal: removed all ecomaibridge_* action and filter hooks that existed solely as Pro extension points (LLM providers, chat hooks, widget config, discovery manifest, tier limits, route registration, admin tabs, tab-view replacement, save fan-out). Free-only analytics now records directly to the Stats class instead of fanning through an action.
  • Internal: simplified the LLM client to Groq plus a Custom OpenAI-compatible option. Removed the unused Anthropic native code path.

1.0.1

  • Removed the daily-message cap on the chat widget. Per-IP rate limiting (configurable in admin) is unchanged.
  • “Powered by EcomAIBridge” widget footer now defaults to off and only appears when the site administrator explicitly opts in via the Chat tab.
  • Added Requires Plugins: woocommerce to the plugin header so WordPress dependency-resolves WooCommerce automatically.
  • Hardened input handling: $_POST and $_GET arrays are now deep-sanitized before being forwarded to downstream code.
  • Removed creation of wp-content/ecomaibridge/ and the data/ cache/ logs/ directories inside the plugin folder. The plugin no longer writes any files inside the plugin directory or wp-content/.
  • Security: validate the configured LLM base URL against private, loopback, link-local, and cloud-metadata IP ranges to prevent SSRF.
  • Security: cap incoming /ai/chat request body size, JSON nesting depth, and per-message length to prevent unauthenticated memory-pressure DoS.
  • Security: added a global daily cap on /ai/chat requests (default 200) as a financial-DoS ceiling for stores facing rotating-IP attackers.
  • Security: restrict CORS on POST endpoints (/ai/chat) to the store’s own origin; read endpoints stay open for AI crawlers.
  • Security: rate-limit telemetry counter now only increments on actual HTTP 429 responses from the LLM provider.
  • Security: settings option set to non-autoload so the LLM API key is no longer pulled into memory on every front-end pageload.
  • Internal: cache-key fingerprinting switched from serialize() to wp_json_encode() so the value can never feed an unserialize sink.

1.0.0

  • First public release on the WordPress plugin repository.