I pick tools by whether the workflow actually needs memory, not by how big the proxy pool is, and I look at cost per validated result instead. The real menu is plain http, rotating http, sticky IP http, or a persistent browser context, and a sticky session only gives you IP continuity, not cookies or CSRF tokens or storage. Their probe is weaker than the article claims because a missing reason can still pass with a 200 that isn't actually account data, and the snippet never runs the comparison they're telling people to run. Needing state doesn't mean you have to buy a hosted browser, a local playwright worker or even one cookie jar can cover it, and chromium still gets fingerprinted and challenged anyway. I treat the wire shaped job model as more of a product pitch and trust the state versus throughput rule way more than any buying map