When should you use it?
- Big purchases where reviews conflict
- Shops with shipping costs that vary
- Sales you suspect are fake
Not for: Buying automatically; Bypassing bot checks on shops
What do you need, and what do you get?
You need
- Your use case, must-haves and price ceiling
- Shops that ship to you
- Price history source
You get
- Pick with delivered price
- Coupon test results
- Owner review summary
How does it work, step by step?
- Describe the needState use case, must-haves and budget.
- Run fixed lookups in codePrices, shipping quotes and history come from scripts, not model guesses.
- Check checkoutsWalk each checkout to the final total, test codes, and stop before ordering.
- Gather owner evidenceSummarize long-term owner reports with links.
- Audit the reportRefuse to deliver if a required check is missing.
The prompt
Our own prompt, inspired by u/zawaer on r/SideProject and written to work in Claude Code and Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Research {product_need} with budget {budget}, shipping to {country}. For each candidate shop: delivered total at checkout (stop before ordering), codes tried and results, price history verdict. Summarize owner reviews with links. Do not report a number you did not observe.
Inspired by u/zawaer on r/SideProject: built an AI agent that researches my purchases for me: real delivered price, working codes, what owners actually say. would you use it?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Never place orders or get around bot checks.
- A 'sale' without price history is unverified.
Our take
The architecture is the reusable lesson: scripts for facts, agents for judgment, and a final audit that sends the agent back when a check is missing. Keep the author's rules unchanged, especially never ordering and never evading bot checks. Describe the need clearly, including size, model and must-have features. Run fixed lookups in code for price history and known coupon lists. Walk checkouts only far enough to see shipping and tax, then abandon. Gather owner reviews that mention durability, not only star averages. Require the report to list every check it skipped. Compare two or three retailers before deciding. Prefer self-hosted if you paste account emails into research flows. Delete checkout sessions so abandoned carts do not linger. Do not store payment methods in the research agent. Re-run the delivered-price check the day you buy, since promotions expire. Archive each report with the date so you can see how often prices moved before you bought.
Where the time goes back: Hours of tab-hopping become one report with the real total per shop.
FAQ
Why split code and agents?
Will it buy for me?
Source and credit
Inspired by u/zawaer on r/SideProject. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- built an AI agent that researches my purchases for me: real delivered price, working codes, what owners actually say. would you use it?
- Creator
- u/zawaer on r/SideProject
- Published on
- Original date
- Sep 30, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- 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 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 23, 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.