Mehul Jalondhara

On the pagination, that one is Myntra’s own behavior, not my wrapper. Myntra’s search is cursor-based internally. Each response hands you back a context token and you pass that token into the next call to get the next page. If you don’t carry that token, Myntra just keeps giving you page 1 on the default sort, which is most likely the page-1 loop those other write-ups are running into. My /search walks that same Myntra cursor, so it pages through properly. You can check it yourself by hitting Myntra’s own search call without the context token and you’ll see it loop too. Using an explicit sort like popularity or price_asc is really just another way around the same Myntra behavior. Good shout on calling it out though, I’ll make the default-loop thing clear in the docs. On coupon_discounted_price, that’s the final price you actually pay after the maximum discount on the product is applied, not a coupon code or cart-minimum thing. I’ll spell the scope out in the docs so it’s not ambiguous. On average_rating, yeah. It should be a number like the prices are, so I’ll normalize it to keep the schema consistent.

Yeah, fair on all of these. The 403s, you're right, that's just the server blocking my request, not an actual robots rule. A 4xx there basically means "no rules, go ahead," so lumping them in with real blocks was sloppy of me. Will reword it. WSJ is the one that actually bugs me. I only counted a block when a site named the bot and did Disallow: /. WSJ flips it: blocks everyone with User-agent: * and then allowlists a few. So my script saw "no named blocks" and called it open, when it's really the opposite. Means I'm undercounting all the default-deny sites, not just WSJ. Gonna rerun it to catch that and fix the numbers. 8 vs 9, yeah that's just a mistake. Text says eight, table has nine because I threw Amazonbot in and forgot to line them up. Will fix. News number is 20 out of 25 sites, so small sample, fair to want that called out. I'll add it. Good catches. Reworking it.