When should you use it?
- You keep grocery receipts digitally
- You want recipes that use what you have
- You budget groceries
Not for: Households without receipt data; Anyone wanting a no-code setup
What do you need, and what do you get?
You need
- Receipts or spending data
- Recipe history
- Grocery budget
- Store price data
You get
- Estimated stock list
- Recipe suggestions
- Budget-aware shopping list
How does it work, step by step?
- Collect receiptsImport grocery receipts into one place with item and date.
- Estimate stockSubtract what recipes used, by date, to estimate what is left.
- Add store dataPull prices and availability for staples from your local store.
- Expose a small tool setGive the assistant a few tools: stock, budget, prices.
- Ask for a planRequest recipes that use stock first and a list that fits the budget.
The prompt
Our own prompt, inspired by Zacariah (@ZacariahHeim) and written to work in ChatGPT and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Estimated pantry stock: {stock}. Grocery budget left this period: {budget}. Store prices: {prices}. Suggest {count} dinners that use stock first. For each, list ingredients to buy with estimated cost. Keep the total within budget and say which stock items are uncertain and worth checking.
Inspired by Zacariah (@ZacariahHeim): Something that AI has helped me automate and I am VERY happy with: Buying Groceries + Creating Recipes. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Estimates drift without occasional real counts.
- Store data access varies; respect each store's terms.
Our take
Zacariah (@ZacariahHeim) uses purchase receipts plus spend history to estimate kitchen stock from recipe history and his grocery budget, plus local store prices, nutrition and availability, exposed to an AI harness through a small MCP interface for budget-aware recipes and orders. Receipts are a free record of what you own, and recipes tell you what you used. Combine them and an assistant can plan around your kitchen rather than an ideal pantry. Keeping the tool surface small makes misuse less likely. Do a quick real pantry count once a month and feed corrections back in. Import receipts with item and date, subtract what recipes used, and expose only a few tools to the assistant: stock, budget and prices. Respect each store's terms on data access. This is not a no-code setup, and estimates drift without real counts. Ask for recipes that use stock first and a shopping list that fits the budget, then check both against your own sense of what is in the cupboard.
Where the time goes back: Planning meals and lists from what you already bought cuts waste and the budget math.
FAQ
Do I need MCP?
How accurate is the stock estimate?
Source and credit
Inspired by Zacariah (@ZacariahHeim). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Something that AI has helped me automate and I am VERY happy with: Buying Groceries + Creating Recipes
- Creator
- Zacariah (@ZacariahHeim)
- Published on
- X
- Original date
- Oct 5, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.