You need a product feed in Google Merchant Center format, shared through a URL, an Amazon S3 or Google Cloud Storage (GCS) bucket, or SFTP. You also need a Botify crawl of your product detail pages (PDPs).

No. AgenticCatalog starts from an existing product feed.

No. AgenticCatalog needs a feed in Google Merchant Center format. It does not matter which system produced it.

No. AgenticCatalog does not require SpeedWorkers or log files, and a crawl of your PDPs is enough. You do not need a full crawl of your website.

Possibly, depending on your use case. AgenticCatalog works alongside your existing feed workflow. It enriches your feed for AI platforms and delivers it to the destinations you configure.

Live Update refreshes the price and availability that SpeedWorkers serves to AI bots when they crawl your PDPs. It does not send your product data to AI platforms. AgenticCatalog delivers your product data to AI platforms directly, without waiting for AI bots to crawl your pages, and enriches that data before delivery.

Yes, as long as each product has a product page and you have a product feed.

AgenticCatalog is available worldwide. Destinations may be limited by region, depending on the platform. For example, OpenAI currently supports the US market only.

There is no technical limit, but limits are tied to your Botify contract.

Start with a low product limit, relative to your feed size. For example, start with 100 products, then 1,000, then 10,000.

AgenticCatalog pulls your feed from a URL, an Amazon S3 or GCS bucket, or SFTP. If the location is private, you provide access credentials during setup.

Your feed must include the attributes Google Merchant Center requires: id, title, description, link, image_link, availability, price, and brand. Some product types require more attributes; see Google’s product data specification. The more complete your feed is, the more context enrichment has to work with.

The more attributes you send, the better. Botify recommends focusing on contextual and conversational attributes: product highlight, product detail, Q&A, related product, document link, popularity rank, item group title, and variant options.

No. AgenticCatalog requires a feed in Google Merchant Center format. Most PIM systems can generate one.

AgenticCatalog ingests your full feed each time.

No. Each AgenticCatalog feed source has one language and one currency. If your catalog uses several languages or currencies, set up a separate feed source for each.

AgenticCatalog enriches product attributes to improve discovery; it does not manage your products. AgenticCatalog does not change the way you sell your products in different regions.

Not currently. AgenticCatalog uses your feed and your crawled PDPs. It does not ingest PDFs or other static files.

Not currently. AgenticCatalog does not integrate with review platforms.

Enrichment combines your feed data with Botify’s crawl data from your PDPs, such as descriptions, specification tables, and reviews. AgenticCatalog does not invent or assume attribute values that are not in this data.

AgenticCatalog uses multiple agents with different models. These models can change at any time.

Not currently.

Not currently.

AgenticCatalog normalizes values when needed. It does not currently infer Global Trade Item Numbers (GTINs).

AgenticCatalog does not currently support translation use cases.

Not currently. AgenticCatalog delivers enriched values in the feeds it sends to your destinations. It does not change your website.

The Enrichment Report includes a downloadable spreadsheet of every original and enriched value. To review results before you enrich your whole feed, use enrichment testing on a sample of products.

For each attribute and destination, you control the following:

No. You influence what AgenticCatalog generates through attribute rules and guidelines, but you cannot edit or add content to individual enriched values. You can, however, review individual enriched values.

AgenticCatalog never changes sensitive data, such as price, availability, links, and IDs. AgenticCatalog stores enriched values for other attributes, such as title and description, for 60 days. If you change one of these attributes after it has been enriched, the enriched value is still used until it expires. To make sure your own value is always used when it is present, set the attribute to enrich only when empty.

Enrichments are tied to a product ID. If a product disappears from the feed and then reappears, AgenticCatalog uses the cached enrichment, as long as it is still valid.

No. AgenticCatalog does not change price, availability, or stock data. These values come from your feed.

Not currently.

When LLM optimization is disabled in Admin settings, AgenticCatalog does not use its AI enrichment agent. It does not look for data within attribute values, such as the description, and does not generate attributes, such as Q&A. AgenticCatalog only copies product data extracted from the crawl into the feed.

AgenticCatalog delivers to OpenAI and to Google Merchant Center, as a primary or supplemental data source. It can also deliver over SFTP, or publish the enriched feed at a direct link that third-party tools, such as feed managers or PIM systems, pull from. Other AI platforms, such as Microsoft Copilot or Perplexity, are not currently supported destinations.

To deliver to OpenAI, you need approval in OpenAI’s merchant program. To deliver to Google Merchant Center, you invite Botify’s service account to your Merchant Center account.

You configure each destination in AgenticCatalog: its connection details and which attributes it receives. AgenticCatalog then delivers the feed at least once a day, on a schedule set by your Botify team.

Yes. You can keep using your feed tool to distribute the enriched feed. Connect your tool to AgenticCatalog using a direct link or SFTP.

Not if you deliver as a supplemental data source. A supplemental source adds or overrides attributes on products already in your primary feed, so it works alongside your existing Merchant Center setup without creating duplicate products.

Yes. You can download enriched feeds as CSV files.

AgenticCatalog can add Urchin Tracking Module (UTM) parameters to the product URLs in your feed: utm_medium=organic and utm_campaign=genai_shopping. You can customize both values. OpenAI adds utm_source=chatgpt.com. Together, these parameters identify visits that come from your delivered feed in your analytics.

Botify monitors impressions and clicks from Google Shopping traffic through your Google Merchant Center connection. Botify measures OpenAI traffic by monitoring visits from chatgpt.com in the analytics tool integrated with your Botify project.

Botify recommends running a split test for each destination, comparing products delivered with enrichment against a control group. The Insights tab shows clicks, impressions, and visits for each destination over time, with the test and control groups shown separately while a test runs.

Once you set up a split test, the groups remain the same until you reshuffle them. Botify assumes that products in both groups go out of stock at the same rate. If one of the groups becomes too small, an alert message is displayed.

It could, potentially. AgenticCatalog improves the quality and structure of the product data that AI platforms receive, which improves your AI presence. Visibility also depends on other factors, such as whether AI bots can access and render your pages, how each platform processes your feed, and your brand’s authority.

There is no separate terms and conditions page for AgenticCatalog. Your Botify account team can walk you through the AgenticCatalog agreement.