On the cart path the configured API key carries the cost and pepesto_credits reports what is left on it. pepesto_predirect is a different arrangement entirely — free to the API client, no key needed, with parsing and product matching deferred until the user opens the link, and the user rather than the client charged at checkout in the app. The catalogue dump is explicitly the wrong tool for everyday use: it is for a catalogue dump, a market analysis or a storefront build, and ordinary recipe-to-cart work goes through pepesto_oneshot or pepesto_products.
A recipe-to-cart server: it parses recipes from URLs, text or images, searches a recipe graph of 1M+ recipes, and maps ingredients to concrete supermarket products with prices and images.
- pepesto_oneshot, the end-to-end path: recipe URLs, free-form text and an image go in, and a redirect_url comes back that opens the Pepesto checkout for the user to verify and pay.
- The same flow in pieces when you want control — pepesto_parse returns title, ingredients, nutrition, instructions and a KgToken, and pepesto_products maps one or more KgTokens plus an optional manual shopping list to real products.
- Ingredients merged across recipes to reduce waste, with several product matches offered per ingredient so the choice stays with you or the user.
- pepesto_suggest, free-text search over a recipe graph of 1M+ recipes with filters for cuisine, dietary tags, ingredients to include or avoid, time and servings, returning images licensed for display without attribution.
- pepesto_predirect, which turns a shopping list into a deferred deep link to the Pepesto mobile app and returns instantly.
- pepesto_catalog, a dump of the indexed catalogue for one supermarket — around 1-2k SKUs of common cooking ingredients with names, prices, images and IDs — with an optional webhook_url for incremental updates on re-index.
- pepesto_credits, which reports the API credits left on the configured key.
PEPESTO_API_KEY, except on pepesto_predirect, which is a public endpoint and needs none. A supermarket_domain for anything that builds a cart, since products and prices are per store. And the user themselves at the end: the cart comes back as a redirect_url they open to verify and pay.
One command plus a key — claude mcp add pepesto -e PEPESTO_API_KEY=pep_sk_… -- npx -y @pepesto/pepesto-mcp, then supply credentials