KaliCart Bridge – Product Feed for ChatGPT & AI Agents

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. The only exception is the optional Federated Catalog feature: if you explicitly activate it, the plugin sends your store's public URL (and nothing else) to KaliCart Global so your public catalog can be included in federated agent search. No customer, order, or private data is ever 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.