(app, country, model) for the most recent scan, plus the previous-period values for trend arrows.
Use this endpoint to populate the top of a dashboard. For per-intent breakdown, see GET /intents.
Path parameters
Query parameters
Response
When the app has been bootstrapped but not yet scanned, the response is the same shape but
scoredAt: null, score: 0, label: "poor", sentimentPct: null, intentsCovered: 0.
Reading the score
The score is a single composite gauge. If you want to interpret it:- 80–100 (excellent): AI assistants reliably recommend your app for the intents you care about, near the top of their lists, with positive framing.
- 60–79 (good): You’re a top-of-mind option but not always the first one mentioned. Look at per-intent visibility to find where you’re weak.
- 40–59 (fair): You appear sometimes, often near the end of lists or with neutral language. Significant ASO + content opportunities.
- 0–39 (poor): AI assistants rarely surface you for these intents. Consider whether your intents accurately reflect what you do, and whether your app’s discoverability outside the App Store (web presence, reviews, mentions in content the assistants train on) is enough.
Code examples
Pattern: render gauges for all enabled models side-by-side
Credits
- 2 credits per call.
Errors
See also
- Bootstrap — required before this endpoint returns scored data
- Intents endpoint — per-intent breakdown that drives the score
- Competitors — apps appearing alongside or instead of you
- AI Visibility overview — concept page

