How we see in the dark.
Methodology, honest numbers, MCP and agents, and the occasional cat. Written by the people building it.

Why a Cat?
Night vision, a steady stare, daily grooming and a tail shaped like the long tail we model. Our mascot is a working metaphor for how we handle data, and every part of it maps to a promise.
DataPussy Team
Brand

Why Our Homepage Has No Testimonials (Yet)
No quotes, no logo wall, no user counter, no star ratings. Before launch we have no customers to quote, and the rules on fake reviews are clear. Here is what we show instead: receipts.
DataPussy Team
Brand

Give Your AI Agent the App Market Over MCP
The DataPussy MCP server gives your agent 14 curated tools for app-market data, a concise and a detailed view, the cost of every call and OAuth 2.1 sign-in. Here is what it does, how to install it in Claude Code and Cursor, and prompts to start with.
DataPussy Team
Developer experience

What A, B, C and D Mean on a DataPussy Estimate
The band tells you how wide an estimate is. The grade tells you how much to trust the band. Here is what goes into each grade, why some segments get a D by rule, and how grades should change the way you use a number.
DataPussy Team
Methodology

Why Every Number Ships With a Range
A single download figure hides how unsure the model is. Here is how to read P10, P50 and P90, why a wide band is information rather than failure, and how to make decisions with ranges.
DataPussy Team
Methodology

How We Estimate Downloads, Revenue and Ad Spend (Methodology v0)
The three models behind every DataPussy estimate, what we observe and what we model, how grades work, what we refuse to show, and how the method gets versioned. Version 0, and subject to change.
DataPussy Team
Methodology