Hey Product Hunt 👋 I built KaliCart Bridge because AI agents are already reading online stores—but they are doing it at the wrong layer. Today, an agent often has to parse a rendered product page, guess which number is the current price, infer whether an item is actually available, and reverse-engineer the store’s categories. A WooCommerce catalog already knows all of this precisely, so forcing agents to scrape the storefront felt unnecessary and unsafe. KaliCart Bridge gives the catalog a structured, read-only interface. An agent starts from a discovery document, learns what the store supports, and can then search products or retrieve catalog data through REST or MCP. The safety boundary matters to me: the plugin cannot alter products, touch orders, process payments, or complete checkout. It exposes public catalog information in a form machines can interpret reliably, while WooCommerce keeps control of the transaction. It is now available for free on WordPress.org. I would especially value feedback from people building agents, MCP integrations, or complex WooCommerce catalogs. Where does the contract still leave room for ambiguity? Which product or variation edge cases should the Bridge handle next? Thanks for taking a look—and please challenge the design. That is exactly why I am launching it here. — Giuseppe

KaliCart Bridge

Make WooCommerce catalogs readable by AI agents

Make WooCommerce catalogs readable by AI agents