Most app-intelligence tools give you one number. We give you three, plus a grade, plus the receipts. Every download, revenue and ad-spend figure on DataPussy is labeled "Estimate — modeled", because that's what it is. It doesn't come from Apple, Google or the publisher.
The Shape of an Estimate
An estimate is an object, not a scalar. You get the same fields in the dashboard, the API, the MCP server, webhooks and exports.
Example — illustrative, not real data:
{
"metric": "downloads_30d",
"p10": 40000,
"p50": 55000,
"p90": 76000,
"grade": "B",
"kind": "modeled",
"label": "Estimate — modeled",
"method_version": "v0",
"inputs_used": ["top_free_rank", "category_curve", "review_velocity"],
"provisional": false,
"lower_bound": false,
"suppressed": false,
"as_of": "2026-11-01"
}
p10,p50,p90— the band and its middle. There's roughly a 10% chance the real value is below P10 and a 10% chance it's above P90.grade— A to D. How far to trust the band.kind— observed, modeled or verified.method_version— which version of the methodology produced this number.inputs_used— the signals that went in. Fewer inputs, wider band, lower grade.provisional— true for the last 72 hours, which can still move.lower_bound— true when we can only see part of the total, such as revenue earned on the web.suppressed— true when we hide the point estimate.as_of— the date the estimate describes.
p10 and p90 are in every view, including the concise one your agent reads. Ranges don't get dropped to save tokens.
What We Won't Show
How We Check Ourselves
Ground truth comes from two places: developers who connect RevenueCat or Stripe through Claim your app, and partner apps that get free access in exchange for sharing real figures. We test leave-one-out: an app's public estimate is never built from its own private data unless the developer agrees to show it.
Once a month we publish an accuracy bulletin. It reports how often the real value landed inside our P10–P90 band, segment by segment, with a minimum cell size so no segment is judged on a handful of apps. At launch, iOS estimates ship as "calibrated on N apps", with N stated on the methodology page and grades of C or D wherever the evidence is thin.
The methodology itself is public and versioned. When a model changes, the version changes, and the changelog says what moved and why. If you think an estimate about your own app is wrong, the dispute form is open to verified developers.
