December 19, 2025
Cart wars: 42 vs 3
Show HN: CommerceTXT – An open standard for AI shopping context (like llms.txt)
AI shopping cheat sheet drops; devs yell 'use JSON' and call out 42 vs 3
TLDR: CommerceTXT proposes a simple file for AI to read store prices, stock, and policies. The crowd pushed back—demanding a [.well-known](https://en.wikipedia.org/wiki/Well-known_URI) location, asking why not use JSON-LD, mocking a “42 vs 3 left” demo mismatch, and challenging its “legal compliance” claim—sparking a lively standards showdown.
Meet CommerceTXT, a plain text “cheat sheet” for AI shoppers that promises real-time stock, prices, reviews, and images without scraping clunky web pages. Sounds neat—until the internet shows up with receipts. The strongest vibe? “Not another root file.” One commenter demanded it live under the well-known URI instead of cluttering site roots, and the thread instantly turned into a mini standards war. Then came the comedy: a demo said “Only 3 left” while the inventory block showed 42. Cue the meme of the day: “42 vs 3.” People joked the file was hallucinating before the AI even touched it. Others rolled their eyes at the whole “LLM-ready” angle, asking why anyone would use a large language model (LLM) to read a structured format when a normal JSON parser does the job faster and cheaper. Another camp asked, “Why not just use Schema.org JSON-LD embedded in pages?” And when the post bragged about “legal compliance” via Schema.org, critics fired back with, “How does compatibility equal compliance?” Despite the eco-friendly pitch (fewer tokens, fewer emissions), the mood was classic Hacker News: split between “interesting idea” and “please, no more files.” CommerceTXT didn’t just launch; it triggered a debate on how AI should shop—and who gets to set the rules.
Key Points
- •CommerceTXT Protocol v1.0.1 is an open standard providing transaction-ready e-commerce context for AI agents.
- •It introduces directives (@INVENTORY, @SUBSCRIPTION, @REVIEWS, @IMAGES) to deliver dynamic, structured data like stock, pricing, reviews, and images.
- •Compared to llms.txt, CommerceTXT is hierarchical, updates with inventory/prices, supports multi-regional data, and maps to Schema.org.
- •Efficiency benchmarks claim large reductions in payload size, token usage, and compute cost versus HTML scraping.
- •A Fractal Architecture guides agents from a Root level deeper only as needed, minimizing token consumption and supporting sustainable AI crawling.