Recipe Ingredient Substitution Suggester

WHAT IT DOES

Recipe Ingredient Substitution Suggester extracts ingredient lists from any recipe page and generates practical, accurate substitutions for each ingredient. Whether you're dealing with dietary restrictions (vegetarian, vegan, gluten-free, dairy-free), missing ingredients, or simply want healthier alternatives, this tool provides specific replacement suggestions including exact ratios and preparation notes. It considers flavor profiles and cooking chemistry to maintain recipe integrity while accommodating your needs.

WHERE IT RUNS

This tool operates as a userscript within the BotGentz extension framework, running directly in your browser on any website. It works on recipe blogs, cooking websites, food magazines, and virtually any page containing recipe content. The tool integrates seamlessly into your workflow, appearing as a draggable panel that stays accessible as you cook and plan meals.

HOW TO USE

Click "Scan Recipe" to automatically extract the recipe content from the current page. The tool intelligently identifies ingredient lists and preparation instructions. Alternatively, select text on the page before scanning to process only that portion. Configure your preferences: choose from dietary options (None, Vegetarian, Vegan, Gluten-Free, or Dairy-Free), select the substitution type (Health-Focused, Flavor-Focused, or Availability-Focused), and toggle ratios and prep notes on or off. Click "Suggest Substitutions" to send the recipe to the AI backend. Within moments, you'll receive a complete list of ingredient substitutions with specific measurements and preparation guidance. Use the "Copy Suggestions" button to save them for your shopping list or cooking session.

TECHNICAL OPERATION

Recipe Ingredient Substitution Suggester employs a multi-strategy extraction pipeline that first checks for selected text, then attempts WebMCP (navigator.modelContext) when available—a W3C proposal for structured page content access—and falls back to DOM-based content detection using prioritized selectors for recipe containers, ingredient lists, and content areas. The user's dietary preference, substitution type, and note inclusion setting are encoded as system-level instructions in the prompt sent to the AI. The text is truncated to 8000 characters and transmitted via GM_xmlhttpRequest to the AI backend. The AI, specifically prompted as a culinary expert, analyzes the recipe to identify each ingredient and its role (binder, leavener, flavor agent, structural component, etc.). It then generates substitutions based on culinary science principles, considering chemical properties, flavor compatibility, and textural contributions. The output includes specific replacement ingredients with precise ratios (e.g., "replace 1 egg with 1/4 cup applesauce") and preparation notes for optimal results. Each request is authenticated with a subscription key and counts against your monthly usage cap.

THE PANEL

The Recipe Ingredient Substitution Suggester panel is fully draggable and remembers its position between sessions using GM_setValue. It snaps to the edge of the viewport for a clean interface and can be collapsed to a small icon when not in use. The panel is resizable to accommodate longer content. Press Escape to quickly close or collapse the panel. The design is optimized for productivity with a dark theme, clear visual hierarchy, and responsive controls that adapt to your workflow.

PLEASE NOTE

This tool requires the free BotGentz extension installed in your browser and an active subscription to access the AI backend. AI-generated substitution suggestions are intended as culinary guidance and should be tested in small batches before preparing full recipes. Results may vary based on ingredient quality, brand differences, and cooking conditions. Always use your judgment and consider testing substitutions when possible. No page data is stored or transmitted beyond the content you explicitly submit for analysis. All processing occurs through secure HTTPS connections, and your subscription key is never exposed to the page context.