App Explorer is where you start. Pick a store, a country and a category, then stack filters until the market fits on one screen. Every row shows downloads and revenue as a range, with a grade beside it. Click through and the detail page tells you what we observed, what we modeled, and when.
What's Included at Launch
One Grammar, Three Places
The chips you click become the URL. The URL uses the same grammar as the REST API, and the same filter catalog feeds the MCP server. So any view you build can leave the dashboard in one click: as a curl command, as TypeScript SDK code, or as a prompt for your agent.
Example request — illustrative, not real data:
curl "https://api.datapussy.com/v1/apps?store=ios&country=US&category=health-fitness&rank[lte]=100&view=concise" \
-H "Authorization: Bearer $DATAPUSSY_API_KEY"
Same filters, same sort, same apps. No re-building the query by hand, no drift between what you saw and what your script fetches.
Provenance on Every Field
Each field on the detail page carries source, kind and observed_at. The kind is one of three words:
- observed — we saw it on a public store page or an official endpoint.
- modeled — our estimate, labeled "Estimate — modeled".
- verified — confirmed by the app's developer through Claim your app, and shown only with their consent.
Downloads and revenue are modeled. They don't come from Apple, Google or the publisher, and we never say they do.
What It Is Not
App Explorer is not a census. At launch it covers roughly 300–500k apps with live signal: apps that sit in a chart or had a ratings change in the last 30 days. Apps outside that set get monthly estimates instead of daily ones. Our history starts when our collection started, and every app page says so. Google Play coverage starts narrower than iOS, because Play has no official batch lookup.
On paid plans, browsing the dashboard doesn't spend credits. Credits pay for API and MCP calls. Cmd-K, keyboard shortcuts and a compact density mode are there when you want to move fast.
