KaliCart Bridge – Product Feed for ChatGPT & AI Agents
Validated OpenAI-compatible product feed for ChatGPT product discovery (ACP), plus catalog API, MCP server and UCP discovery for AI agents.
Will this break my store?
What the WordPress.org registry says about keeping KaliCart Bridge – Product Feed for ChatGPT & AI Agents running.
Tested to 7.1.1
Tested against the WordPress branch in use today.2 days ago
8.0
Your host must be running at least this version.6.0
woocommerce
These must be installed and active first.1
A single maintainer. Worth knowing if the plugin is load-bearing for your store.Maintenance & trust
Scored on how KaliCart Bridge – Product Feed for ChatGPT & AI Agents is looked after — not on how many stores run it.
Maintenance
35 / 35WordPress compatibility
20 / 20Support responsiveness
Not enough dataMerchant satisfaction
Not enough dataListing transparency
6 / 10Ratings
No one has rated this plugin on WordPress.org yet. That is a statement about the ratings page, not about the plugin — plenty of well-kept plugins never collect them.
Make your WooCommerce catalog ready to be read and verified by AI shopping systems.
KaliCart Bridge gives you an immediate catalog-readiness report inside WooCommerce: it identifies products with missing images, brand, usable description, category, price or SKU, and links you directly to the native Products screen to fix them. It then exposes your live catalog in a structured form for AI agents and can generate a validated product feed ready for ChatGPT merchant submission.
No LLM runs on your site. No cloud service or customer data is sent anywhere by default. Prices, availability and product changes remain live on your WooCommerce store.
The plugin does not promise traffic, ChatGPT placement or merchant approval. It prepares and exposes your catalog; OpenAI controls access to its own shopping surfaces and delivery channel.
What you get after installation
- A catalog-readiness report with actionable product fixes.
- A current, structured catalog API for agents that reach your store.
- An optional ChatGPT feed, validated before export.
- Optional inclusion in KaliCart’s federated catalog, only with explicit consent.
Documentation: https://bridge.kalicart.com/docs/
For developers and AI integrations
What it does:
- Exposes a
/discoveryendpoint — the single entry point any agent needs to understand your catalog - Provides
/catalog/search,/catalog/products,/catalog/product/{id},/catalog/categoriesendpoints - 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_urlandsearch_url_templatefields 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
<link rel="kalicart-agent">in your site<head>for agent auto-discovery - Adds an “agent ready” badge in the footer
- Injects
Allow: /wp-json/kalicart/inrobots.txt - Generates
/kalicart-sitemap.xmllinked 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 optional Federated Catalog and provider-specific distribution channels require separate explicit actions (see “External services” below)
- 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_genderattribute, 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_coloreand 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.
ChatGPT Product Discovery Feed
- Configure and generate. Set your return policy URL and target countries (derived from your WooCommerce selling locations); optionally set a brand fallback for own-label stores. The plugin validates every row against the OpenAI Product Feed specification: incomplete store configuration blocks generation entirely, products without image or brand are excluded and counted, and a failed run never destroys the last valid feed.
- Apply at chatgpt.com/merchants. Application and approval are required and decided by OpenAI.
- Deliver after approval. Upload the generated file (stable filename,
jsonl.gzsupported) on the delivery channel OpenAI assigns. The plugin regenerates a full daily snapshot via WP-Cron.
No acceptance or visibility is guaranteed by the plugin: approval, delivery access and final ranking are determined by OpenAI.
External services
This plugin works fully standalone. It connects to one external service only after an explicit administrator action in WP Admin → KaliCart Bridge. Federated Catalog participation and each provider-specific distribution authorization are separate choices; a provider channel cannot be authorized until the Federated Catalog is active.
Service: KaliCart Global (https://dashboard.kalicart.com)
When data is sent: When an administrator activates or revokes the Federated Catalog, requests its external-visibility status, or explicitly grants or revokes a named federated distribution channel. After a provider receipt exists, opening the plugin page requests its processing status using the public site URL and consent ID. A failed provider-receipt delivery may be retried twice, after approximately one minute and five minutes. Nothing is sent merely because the plugin is installed or activated.
What is sent: Federated Catalog activation, revocation and visibility checks send the site’s public URL (e.g. https://yourstore.com). A provider authorization receipt additionally sends its consent ID, provider, purpose, action, UTC timestamp, plugin and terms versions, consent locale, and SHA-256 evidence-chain hashes. The administrator’s WordPress user ID and localized consent text remain only in the store’s local evidence log. No customer, order, payment, credential or API-key data is transmitted.
What the service does: The URL tells KaliCart Global your store wishes to be discovered. KaliCart Global periodically reads your already-public catalog and includes it in federated agent search. For a separately authorized provider channel, KaliCart Global stores the minimal receipt and verifies the matching authorization against the store’s public discovery document before the channel can become eligible. It only reads public catalog data; it never writes to your store. Revoking the provider channel does not revoke Federated Catalog participation, and revoking federation suspends distribution without rewriting the authorization history.
Privacy notice: https://bridge.kalicart.com/privacy/
Terms / documentation: https://bridge.kalicart.com/docs/
The feed format is region-neutral. Merchant eligibility and shopping-surface availability are determined by OpenAI and may vary by market.
No, by design. The feed is discovery-only (is_eligible_checkout=false): customers buy on your storefront and you remain merchant of record. This matches OpenAI’s own shift toward merchant-owned checkout.
Not unless you choose to. By default the plugin runs entirely on your server and sends nothing externally. Activating the optional Federated Catalog sends your store’s public URL to KaliCart Global. A provider-specific distribution channel is a second, separate opt-in: its tamper-evident receipt contains the public URL and authorization metadata and hashes, but never the administrator identity or localized consent text. No customer, order, payment or credential data is sent. See “External services” below, and the privacy notice at https://bridge.kalicart.com/privacy/.
No. This plugin is fully standalone and free.
The Federated Catalog is an optional discovery network operated by KaliCart Global. The Bridge makes your catalog readable by agents that already reach your domain; the Federated Catalog makes it discoverable by agents that do not know your store yet. It is opt-in, separate from the local Bridge endpoints, and revocable at any time.
There are two discovery paths. Local signals — .well-known files, robots.txt entries, the rel="kalicart-agent" head link and the badge — help an agent that lands on your own domain find the Bridge. They do not feed the federated index by themselves. The federated index is a separate cross-merchant index: after you activate it, KaliCart Global reads your already-public /discovery and /catalog/* endpoints and lets agents search across participating stores.
End to end: from WP Admin → KaliCart Bridge you activate the Federated Catalog; the plugin sends only your public site URL; KaliCart Global pulls the public catalog read-only; matching results route agents back to your store. Authoritative price, availability and checkout stay on your WooCommerce site, served live by your Bridge. If you revoke consent, your catalog leaves federated results while direct agent access to your store remains active.
Public endpoints (discovery, search, products, categories) are accessible without authentication — same as the WooCommerce REST API public surfaces. The /health endpoint requires manage_woocommerce capability.
Yes — all three signals (badge, robots.txt, sitemap) can be toggled individually in the KaliCart settings tab.
5 minutes. You can force a refresh via the “Refresh analysis” button or the ?force=true query parameter on the /health endpoint.
The catalog can be consumed two ways. Any agent can call the plain REST endpoints under /wp-json/kalicart/v1/catalog/ directly. MCP-capable clients can instead connect to the MCP server at /wp-json/kalicart/v1/mcp (JSON-RPC 2.0): the assistant connects to that URL — no API key — and gains the catalog tools (search_products, get_product, list_categories, get_meta, list_products). In clients that support remote MCP connectors, add it as a custom connector pointing to that URL.
Yes, when the chatbot service can ingest URLs, API documents or external knowledge sources. Give it the discovery URL first: https://yourdomain.com/wp-json/kalicart/v1/discovery. From there it can find the catalog endpoints, the OpenAPI description and the MCP endpoint. If the service supports live REST or MCP calls, it can query current catalog data directly. If it only imports a knowledge base, it may create a snapshot: useful for product answers, but final price, stock, coupons, shipping and checkout should still be verified on the merchant site.
The benefit is practical: chatbot builders can read a structured, machine-readable WooCommerce catalog instead of scraping product pages. The Bridge does not add an LLM to your site and does not decide how the chatbot works; it supplies cleaner catalog data for tools that can consume it.
Plugin details
Tags on WordPress.org
Alternatives
Other plugins in the same categories.
MxChat – AI Chatbot & Content Generation for WordPress
AxiaChat AI – Free AI Chatbot (Answers Customers Automatically)
Notification for Telegram
BEAR – Bulk Editor for WooCommerce Professional. AI assistant on board (MCP Server)
Mail Mint – Email Marketing, Automation & WooCommerce Emails with AI Assistance
