One Feed, Every Agent: GMC for Gemini, ACP for ChatGPT, MCP for Claude
The agentic commerce standards have not converged, and you do not have to wait for them to. The major AI shopping agents each consume a different format today, and Agenticfeed can speak all of them from a single catalogue. This is how you get your products in front of ChatGPT, Gemini and Claude now, while the standards settle.
Why not just wait for one standard?
In 2026 there is no single feed that every agent reads. OpenAI built the Agentic Commerce Protocol with Stripe. Google routes products through Merchant Center and the Universal Commerce Protocol. Anthropic's Claude connects over the Model Context Protocol. Each one is live, each one is different, and waiting for them to merge means sitting out the window where being present early counts for the most.
Agenticfeed removes the choice. It maps your catalogue once, to buyer intent, then syndicates that into each agent's native format. You do the work a single time and it lands everywhere. The alternative, hand-building a Merchant Center feed, an OpenAI feed and an MCP server separately, is exactly the plumbing problem we described in Agentic Shopping Isn't Magic Yet: Product Data Is Why.
GMC supplemental feed: the on-ramp to Gemini
Google Merchant Center is how a product reaches Gemini, Google's AI Mode and Shopping. Agenticfeed meets you wherever you are:
If you already publish a Merchant Center feed, Agenticfeed gives you a supplemental feed that layers your questions, answers and product highlights onto your existing products, merged by product id. Your primary feed keeps doing its job, and the supplemental one adds the conversational data agents actually reason over.
If you do not have a Merchant Center feed, Agenticfeed generates a full primary feed straight from your catalogue, with the same conversational attributes built in, so you can start from zero.
Either way there are no changes to your website. You add one URL as a data source in Merchant Center. GMC is the format, and Gemini is the destination.
ACP feed: the on-ramp to ChatGPT
OpenAI's Agentic Commerce Protocol is how a product reaches ChatGPT. Unlike Google, ChatGPT has no supplemental mechanism to merge onto, so Agenticfeed emits your complete product feed in ACP's JSONL format, with your question-and-answer pairs built in, ready to submit at chatgpt.com/merchants.
Your buyer intent data maps directly onto ACP's own conversational field, so the reasoning an agent needs travels with each product rather than being left behind on a web page. ACP is the format, and ChatGPT is the destination.
MCP: the on-ramp to Claude
Claude does not pull a static file. Anthropic's Model Context Protocol is a live connection: Claude queries a server in real time rather than fetching a feed on a schedule. Agenticfeed runs an MCP server, listed in the official MCP registry as io.github.bluestratus/agenticfeed, that Claude and any MCP client can connect to and query directly.
Instead of scraping a rendered page and guessing, the agent asks your Agenticfeed endpoint for the product and the intent it maps to: the questions it answers, the problems it solves and the use cases it fits. MCP is the format, and Claude is the destination. We covered the registry listing in Agenticfeed Is on the Official MCP Registry.
One catalogue, mapped to intent
The reason a single source can feed three very different formats is that they all sit on the same foundation: your catalogue mapped to buyer intent. Agenticfeed turns each product into the questions it answers, the problems it solves and the use cases it fits, each paired with a short answer grounded in the product itself.
That intent layer is what an agent reasons over, whichever channel it lives in. When a shopper says "I need a gift for a family who likes light strategy games, under thirty pounds, that plays in an hour," the agent matches that need to a product. Map the intent once, and a Merchant Center feed, an ACP feed and an MCP connector are simply three renderings of the same truth. This is the mechanism behind How AI Shopping Agents Choose Products.
The intent layer is an open standard
That mapping is not a private format locked to us. Agenticfeed publishes it as an open standard, the Agenticfeed Standard, on GitHub, so the work you do is portable. The Merchant Center feed, the ACP feed and the MCP connector are adapters: each one translates the same open standard into whatever an agent consumes today.
That is the whole idea. You map your catalogue to buyer intent once, in an open format, and Agenticfeed meets every agent where it currently is. The MCP connector is already a step toward agents reading the standard directly, and it is listed on the official Model Context Protocol registry as io.github.bluestratus/agenticfeed. As more agents adopt the standard, your feed already speaks it, so the work you do today does not expire when the formats change.
How to switch them on
From your Agenticfeed dashboard it is three URLs:
Gemini. Set your Google Merchant Center feed URL in your profile if you have one, and Agenticfeed shows your supplemental feed URL to add in Merchant Center. No feed yet? It shows a generated primary feed URL instead.
ChatGPT. Copy your ACP feed URL and submit it at chatgpt.com/merchants.
Claude. Point any MCP client, including Claude, at your Agenticfeed MCP endpoint.
Three URLs, three agents, one catalogue behind them, and no work repeated.
Frequently Asked Questions
Which feed goes to which AI agent?
Google Merchant Center (a supplemental feed if you already have one, or a generated primary feed if you do not) reaches Gemini and Google's AI surfaces. An Agentic Commerce Protocol feed reaches ChatGPT. The Model Context Protocol reaches Claude. Agenticfeed produces all three from one catalogue.
Do I need to change my website?
No. All three are generated from your Agenticfeed catalogue, not from your site. You add a URL as a data source in Merchant Center, submit a URL at chatgpt.com/merchants, and point MCP clients at your Agenticfeed endpoint. Nothing changes on your storefront.
What if I already have a Google Merchant Center feed?
Then Agenticfeed gives you a supplemental feed that enriches it, merging your questions, answers and product highlights onto your existing products by id, so your primary feed is untouched. If you do not have a Merchant Center feed, Agenticfeed generates a full primary feed from your catalogue with the same conversational data built in.
The Takeaway
The standards will converge eventually. Until they do, the merchants who win agent recommendations are the ones already present in every channel, in the format each agent speaks. Agenticfeed maps your catalogue to buyer intent once, as an open standard, then syndicates it as a Merchant Center feed for Gemini, an ACP feed for ChatGPT and an MCP connector for Claude. One source of truth, every agent, no waiting.