From the field
What people actually struggle with
App store threads are unusually seeded: of the ~140 Reddit and X posts read in August 2026, more than half were builders announcing their own scrapers, one ran the same review-scraper copy through seven subreddits, and one post seeded zero-width spaces at every paragraph break. These five are developers hitting the wall in public.
Deep store ranks are interpolated, not measured
“The paid SERP APIs go deeper, but tools that don't pay for them and still show you 'rank #63' are interpolating, not measuring.” r/androiddev, 11 points
What this page can do about it: That is the honest ceiling and this page will not pretend past it. The rows return the store's own results in the store's own order, as deep as the store exposes them, and treg.to publishes no rank number of its own.
Apple's free endpoint stops answering without notice
“As of this morning (April 16), all my requests to the /search endpoint are returning HTTP 404 Not Found.” r/iOSProgramming, 11 points
What this page can do about it: That is Apple's public iTunes Search endpoint, which is free, undocumented in practice, and not in this catalog. The rows here are a paid provider's store engines, billed only on a successful search, with what the live traffic shows rather than an uptime promise.
Everything is API first except the store itself
“To have to scrape them from the app store pages when everything else is so API first seems like a miss.” X, 19 likes
What this page can do about it: Agreed, and that is the whole reason this row exists. The agent sends a keyword and a country and gets rows; the scraping, the proxies and the markup changes are the provider's problem, at a price printed before the call.
The free endpoint carries none of the numbers you want
“the itunes search api does not give downloads, subscriptions, or any financial metrics, and it does not provide subscription pricing either.” X, 69 likes
What this page can do about it: True, and neither do these rows. Listing price, rating and review count come back; installs and revenue do not exist in any public store response, and no provider on this page can conjure them.
The whole store is bigger than the context window
“welp, even using a 1M token context limit, the data is too large.” r/shopifyDev, 77 points
What this page can do about it: Which is the argument for asking for columns rather than everything. Say which fields a row needs in the prompt, cap the result count, and the agent reads a table instead of drowning in a store dump.
