KaliCart Bridge – AI Agent Catalog for WooCommerce vs WooCommerce Legacy REST API

KaliCart Bridge makes your WooCommerce product catalog computable: it exposes a structured, normalized REST API and an MCP server that AI shopping agents and assistants — such as ChatGPT, Claude, Gemini, Perplexity and any MCP-capable client — can read and act on directly. No LLM runs on your server; the plugin only turns your existing catalog into clean, computable data. Documentation: https://bridge.kalicart.com/docs/ What it does: Exposes a /discovery endpoint — the single entry point any agent needs to understand your catalog Provides /catalog/search, /catalog/products, /catalog/product/{id}, /catalog/categories endpoints Exposes a Model Context Protocol (MCP) server at /wp-json/kalicart/v1/mcp (JSON-RPC 2.0) so MCP-capable agents can call the catalog as tools — same data as the REST endpoints, no API key Gives AI chatbot and assistant builders a structured catalog source to ingest or call, instead of scraping product pages Computationally normalizes product data: prices (min/max for variables, sale %, discount), stock, gender inference, color family mapping, size type detection Exposes WooCommerce shipping-zone policy for agent reasoning; checkout remains the final authority for exact destination/cart shipping cost Exposes active product/category-compatible coupons as conditional checkout savings; coupons never replace the catalog price Category tree nodes include direct products_url and search_url_template fields so agents can navigate without constructing URLs manually Dashboard issue cards and suggestions link to filtered product lists for direct remediation Uses your merchant taxonomy — no global remapping, products stay in your WooCommerce categories Injects a in your site for agent auto-discovery Adds an “agent ready” badge in the footer Injects Allow: /wp-json/kalicart/ in robots.txt Generates /kalicart-sitemap.xml linked from the WP sitemap index Shows a catalog health dashboard in wp-admin with quarantine tracking and improvement suggestions What it does NOT do: No LLM calls No cloud dependency for core functionality No data sent anywhere outside your server by default — the only optional exception is the Federated Catalog feature (see “External services” below), which you turn on explicitly No API key required for public endpoints Normalization engine: Price: regular, sale, current, discount %, currency — variable products get min/max ranges Stock: status, in_stock bool, quantity if managed, backorder policy Gender: inferred from pa_gender attribute, category paths, tags, product name (multilingual keywords: IT/EN/FR/DE/ES) Color: mapped to 13 color families via keyword matching on pa_color/pa_colore and product metadata Size: detected from pa_size/pa_taglia, type auto-detected (clothing S/M/L, numeric EU, shoes EU half-sizes) Catalog health / quarantine: Products are scored 0–100 based on: title quality, description length, category assignment, price validity, image presence and SKU presence. Quarantine is reserved for blocking computability issues: ambiguous/too-short titles, missing or very short descriptions, missing real categories, and missing or zero prices. Missing images and SKUs remain clickable improvement suggestions but do not quarantine products. Checkout sessions (optional): When enabled in WP Admin → KaliCart → Settings, agents can create checkout sessions containing one or more products. Each session returns cart_url (lands on WooCommerce cart for review) and checkout_url (goes directly to checkout). Sessions expire after 30 minutes. No OAuth, no PII, no payment on the agent side. Model Context Protocol (MCP) endpoint: The same read-only catalog is also exposed as an MCP server at /wp-json/kalicart/v1/mcp (JSON-RPC 2.0 over HTTP POST). MCP-capable agents and assistants connect to it and call the catalog as tools: search_products, list_products, get_product, list_categories, get_meta. It is read-only and needs no authentication, exactly like the public REST endpoints — it adds a second transport, not new data. No LLM, no external calls. Checkout and payment are never exposed over MCP. External services This plugin works fully standalone. It connects to one external service only if you explicitly opt in by activating the optional Federated Catalog feature in WP Admin → KaliCart Bridge. Service: KaliCart Global (https://dashboard.kalicart.com) When data is sent: Only when an administrator clicks “Activate Federated Catalog” (and, symmetrically, “Revoke consent”). Nothing is sent automatically, on activation, or in the background. With the feature off, the plugin makes no external requests. What is sent: A single value — your site’s public URL (e.g. https://yourstore.com). On revoke, the same URL is sent to withdraw. No customer data, orders, personal data, credentials, or API keys are ever transmitted. What the service does: The URL tells KaliCart Global your store wishes to be discovered. KaliCart Global then periodically reads your already-public catalog (the same data exposed by the Bridge’s public REST endpoints) and includes it in federated agent search. It only reads; it never writes to your store. Revoking stops this and parks your catalog. Privacy notice: https://bridge.kalicart.com/privacy/ Terms / documentation: https://bridge.kalicart.com/docs/

The Legacy REST API will no longer part of WooCommerce as of version 9.0. This plugin restores the full functionality of the removed Legacy REST API code in WooCommerce 9.0 and later versions. For all intents and purposes, having this plugin installed and active in WooCommerce 9.0 and newer versions is equivalent to enabling the Legacy REST API in WooCommerce 8.9 and older versions (via WooCommerce – Settings – Advanced – Legacy API). All the endpoints work the same way, and existing user keys also continue working. On the other hand, installing this plugin together with WooCommerce 8.9 or an older version is safe: the plugin detects that the Legacy REST API is still part of WooCommerce and doesn’t initialize itself as to not interfere with the built-in code. Please note that the Legacy REST API is not compatible with High-Performance Order Storage. Upgrading the code that relies on the Legacy REST API to use the current WooCommerce REST API instead is highly recommended.