Food ChatGPT Plugins
Last reviewed
May 9, 2026
Sources
No citations yet
Review status
Needs citations
Revision
v2 ยท 2,510 words
Improve this article
Add missing citations, update stale details, or suggest a clearer explanation.
Last reviewed
May 9, 2026
Sources
No citations yet
Review status
Needs citations
Revision
v2 ยท 2,510 words
Add missing citations, update stale details, or suggest a clearer explanation.
See also: ChatGPT Plugins, ChatGPT Plugin Categories and Food
Food ChatGPT Plugins were the subset of third-party plugins published in the ChatGPT plugins store between March 2023 and April 2024 that focused on cooking, recipes, grocery shopping, restaurant discovery, and food delivery. The category sat alongside Beverage ChatGPT Plugins and overlapped with Shopping ChatGPT Plugins at the retail end of the catalogue. Operated by OpenAI as part of the broader plugin program for ChatGPT, the food category drew unusual attention at launch because two of its inaugural participants (Instacart and OpenTable) were household consumer brands that gave the plugin program early credibility. The whole plugin framework, food category included, was deprecated on March 19, 2024 and shut down on April 9, 2024, succeeded by Custom GPTs and the GPT Store. This article treats the food category as a historical reference for an early experiment in connecting a large language model to live food and grocery services.
OpenAI announced ChatGPT plugins on March 23, 2023 in a blog post titled "ChatGPT plugins." The post described plugins as the company's first plugins for the chatbot and presented them as a way to let ChatGPT "access up-to-date information, run computations, or use third-party services." The launch slate listed eleven external partners and two first-party plugins (a code interpreter and a browsing tool). Two of those eleven external partners were food-adjacent: Instacart for grocery ordering and OpenTable for restaurant reservations. Access at launch was gated behind a waitlist and rolled out gradually to ChatGPT Plus subscribers through the spring of 2023.
On May 12, 2023 OpenAI announced that web browsing and plugins would become available to all ChatGPT Plus subscribers the following week. The plugin store opened for general access on May 19, 2023, after which the catalogue grew quickly. Independent developers added recipe assistants, ingredient databases, restaurant search engines, and food delivery integrations across the second half of 2023. The food category in the plugin store therefore had two distinct phases: a short alpha period in March and April 2023 dominated by the launch partners, and a much larger general-availability phase from late May 2023 through early 2024 in which long-tail third-party plugins outnumbered the original brand-name entries.
The deprecation arrived in two steps. At OpenAI DevDay on November 6, 2023 the company introduced Custom GPTs and announced that plugins would eventually be retired in favour of GPTs and their tool-calling layer, called Actions. The plugin store stopped accepting new submissions soon afterward. On March 19, 2024 OpenAI sent the formal deprecation notice to plugin developers, and on April 9, 2024 plugins were turned off for end users. The official help-center notice was titled "Winding down the ChatGPT plugins beta" and pointed users and developers to GPTs and the GPT Store for equivalent functionality.
The key dates for the food category are summarised in the table below.
| Date | Event |
|---|---|
| March 23, 2023 | OpenAI announces ChatGPT plugins. Instacart and OpenTable are listed among the eleven external launch partners. |
| May 12, 2023 | OpenAI announces general availability of plugins for ChatGPT Plus subscribers. |
| May 19, 2023 | Plugin store opens to all Plus subscribers. Third-party recipe and food plugins begin to appear in volume. |
| November 6, 2023 | OpenAI DevDay introduces Custom GPTs and Actions. Plugins are publicly described as a sunsetting feature. |
| January 10, 2024 | GPT Store opens, beginning the migration of plugin functionality into branded GPTs. |
| March 19, 2024 | OpenAI formally deprecates the plugins beta. |
| April 9, 2024 | The plugin store and plugin runtime are turned off for end users. |
A food plugin was a small piece of server software exposing an HTTP API to the chatbot. Like every plugin, it consisted of two artefacts on the developer's domain: a manifest file named ai-plugin.json served at /.well-known/ai-plugin.json, and an OpenAPI specification describing the available endpoints. ChatGPT used the manifest to describe the plugin to the GPT-4 model in natural language and used the OpenAPI document to plan and validate calls.
The practical capabilities clustered into a small number of recurring patterns:
Almost no food plugin completed a transaction inside ChatGPT itself. The standard pattern was for the plugin to return a deep link (for example to a populated grocery cart or to a restaurant reservation page) which the user opened in a browser to finish the task. This boundary was a deliberate part of the plugin design: ChatGPT could compose, search, and summarise, but the actual purchase or booking happened on the partner's own site, where existing payment, identity, and trust mechanisms already lived.
The two best-documented food plugins are the launch partners that OpenAI named in its original March 23, 2023 announcement.
Instacart was one of the eleven external launch partners on March 23, 2023. According to OpenAI's announcement and Instacart's own coverage at the time, the plugin let a user describe a meal or recipe and then convert the resulting ingredient list into a shopping cart at a local grocery retailer. A typical interaction read like this:
The Instacart plugin was repeatedly cited in coverage of the plugin launch as a flagship example of what plugins were for, because it tied together a clearly defined consumer task (cooking dinner) with a clearly defined retail backend (a same-day grocery service).
OpenTable was the second food-adjacent launch partner. The plugin let ChatGPT search OpenTable's reservation index and return restaurants that matched a user's natural-language query ("find me a quiet Italian restaurant near Union Square next Friday at seven"). The plugin would return a short list of candidate restaurants with metadata such as cuisine, price range, and a reservation link. Booking itself was finalised on OpenTable's own pages.
The presence of OpenTable in the launch slate (alongside Expedia and Kayak in travel) signalled that OpenAI's plugin program was aimed at integrating with mainstream booking platforms rather than rebuilding them inside ChatGPT.
Wolfram, a launch partner usually associated with mathematics and curated reference data, exposed nutritional and food-composition information through its Wolfram Alpha back-end. Though not normally classed under food, it was used heavily for food-adjacent queries about calories, macronutrients, cooking unit conversions, and ingredient composition.
After general availability on May 19, 2023, independent developers published recipe-oriented plugins covering recipe search by ingredient or dietary tag, multi-day meal planners with consolidated shopping lists, calorie and macro lookups against public nutritional databases, and restaurant search wrappers built on public review APIs. Because this wiki only documents plugins that can be cross-referenced to a primary source, the article does not enumerate them by name. Most were short-lived. With the deprecation of the plugin program in April 2024, they either shut down or migrated their backends to GPT Actions inside a Custom GPT.
Three workflow patterns dominated discussion of the food category during the plugin era.
This was the canonical Instacart-style flow and was used in OpenAI's own launch demos:
This workflow is the one most often cited in retrospectives of the plugin era because it tied together generation (recipe), planning (consolidated list), and action (cart link) in a single conversation.
The restaurant flow was simpler and more familiar:
In contrast to the grocery flow, the restaurant flow rarely reached a confirmed booking inside ChatGPT itself. The chatbot's role was discovery, not transaction.
A quieter but heavily used workflow involved asking the chatbot for nutrition facts or ingredient substitutions. The base model could answer many such queries from training data, but plugin-backed answers were preferred for current or branded data. Wolfram and several smaller nutritional-database plugins served this need.
OpenAI gave several public reasons for ending the plugin program. The food category illustrated all of them.
For the food category, the discovery problem and three-plugin limit were the most painful. A typical Sunday meal-planning session wanted a recipe plugin, a grocery plugin, and a nutrition plugin at once, which filled the plugin budget and left no room for a pairing plugin or a calendar plugin.
The successor to the plugin program is the combination of Custom GPTs and the GPT Store. A GPT bundles three things: custom instructions, optional knowledge files, and Actions (the new name for the plugin-style API call layer). For the food category, this packaging changed the shape of the catalogue.
Where the plugin store presented dozens of single-purpose plugins (one for recipe search, one for grocery, one for nutrition), the GPT Store presented a smaller number of branded assistants such as "meal planner" or "restaurant scout." Each GPT could call the same kind of HTTP backend a plugin used to call, so the underlying technology was largely unchanged, but discovery moved from a flat list of plugins to a marketplace of named applications.
The Actions layer underneath GPTs uses the same OpenAPI specification format that plugins used. Most food plugin developers who continued operating in 2024 ported their backends to Actions inside a Custom GPT with limited code changes. A user no longer chose individual plugins inside a chat: they chose a GPT in the GPT Store, opened it, and the relevant Actions ran automatically.
The table below contrasts the food category before and after the transition.
| Aspect | Plugin era (2023 to 2024) | GPT era (2024 onward) |
|---|---|---|
| Discovery | Flat plugin store inside ChatGPT | Branded GPTs in the GPT Store |
| Activation | User toggled up to three plugins per chat | User opened a single GPT |
| Backend contract | OpenAPI plus ai-plugin.json manifest | OpenAPI plus a GPT configuration |
| Persistence of identity | None. Plugins were stateless API wrappers | GPTs carry instructions and knowledge across sessions |
| Revenue model | None for developers | Revenue share announced for GPT Store |
| Migration cost for developers | n/a | Generally low: same API, repackaged behind a GPT |