# App Revs

> App Revs is an iOS App Store optimization tool built on Apple's public data: keyword
> popularity (Apple Ads scale) and difficulty, an app's search positions and genre chart
> places, daily ratings, written reviews, release history, publishers and their apps.
> No download or revenue estimates. Public pages read stored data; live App Store calls
> and per-account features need a signed-in user or an API key.

## Site
- [Home](https://apprevs.com/) : Search any iOS app, open its page.
- [App page](https://apprevs.com/us/app/389801252) : `/{country}/app/{track_id}`: keywords the app ranks for, competitors, charts, ratings history, releases, reviews.
- [Keyword page](https://apprevs.com/us/keyword/calorie-counter) : `/us/keyword/{slug}`: popularity, 15 months of demand, difficulty, the top 10 apps, the searches those apps share. One page per US head term (about 7,500).
- [Keywords by genre](https://apprevs.com/us/keywords) : `/us/keywords/{genre}`: each genre's 500 most searched terms with popularity, difficulty, the #1 app, brand searches marked.
- [Developer page](https://apprevs.com/us/developer/1322881000) : `/{country}/developer/{artist_id}`: a publisher and every app they sell in the store.
- [New apps that rank](https://apprevs.com/tools/new-apps) : Apps released lately that already sit in a search's top 200 or on a genre chart.
- [Rising apps](https://apprevs.com/tools/rising-apps) : Apps gaining App Store ratings fastest over the last days, from Apple's own counts.
- [Most searched keywords](https://apprevs.com/tools/most-searched) : Top 500 search terms per category and month for 90 storefronts, 15-month history.
- [App Store localizations](https://apprevs.com/tools/localizations) : Default and additional metadata languages for each of the 175 storefronts.
- [Guides](https://apprevs.com/guide) : Fifteen chapters on how App Store search ranks, with this week's numbers from the US store, plus six playbooks (validate an idea, first ten keywords, launch week, localize in a day, competitor reviews, popularity 5): what decides a result, popularity and difficulty, finding and writing keywords, screenshots as metadata, localizations, ratings, growth without downloads, measuring a release.
- [Storefronts](https://apprevs.com/countries) : All 175 storefronts and what is read for each: keyword popularity months, charts, ratings scan, metadata language.
- [Dashboard](https://apprevs.com/app) : Sign in with Google to follow apps as projects, track keyword lists per store, claim a publisher, connect an App Store Connect key.
- [Settings](https://apprevs.com/app/settings) : Generate or revoke an API key.
- [Docs](https://apprevs.com/docs) : Keys, quickstart, endpoints at a glance. [MCP server](https://apprevs.com/docs/mcp): connect lines per client, every tool with its parameters, a real call and answer. [API reference](https://apprevs.com/docs/api): every endpoint with parameters, examples and response shapes.
- [Agent skill](https://apprevs.com/SKILL.md) : Instructions for agents: keys, endpoints, MCP.

## MCP server
`https://api.apprevs.com/mcp` (Streamable HTTP). Stored-data tools work without a key;
live and account tools need `Authorization: Bearer ar_live_...`.
`claude mcp add --transport http apprevs https://api.apprevs.com/mcp --header "Authorization: Bearer ar_live_..."`

## API
Base URL: `https://api.apprevs.com/api/v1`. Agents send `X-API-Key: ar_live_...`; the web
app sends `Authorization: Bearer <firebase_id_token>`. Keys are made at
[Settings](https://apprevs.com/app/settings) after a Google sign-in and shown once.
- [API reference](https://apprevs.com/docs/api) : Every endpoint, parameters and response shapes (also as markdown: https://raw.githubusercontent.com/onlyoneaman/ios-reviews/main/docs/API.md).

Public, stored data:
- `GET /keywords/{term}?country=us&app_id=` : popularity, difficulty, top 10, related terms, the app's position.
- `GET /apps/{track_id}/keywords?country=us` : keywords the app ranks for, and its genre charts.
- `GET /apps/{track_id}/competitors?country=us` : apps sharing its keyword top 10s.
- `GET /apps/{track_id}/charts` : every genre chart place across 20 stores, with the week's movement.
- `GET /apps/{track_id}/positions` : top-10 search terms per store where it was checked.
- `GET /apps/{track_id}/rating-history?country=us&days=30` : daily rating and count, releases, reviews per day.
- `GET /apps/{track_id}/reviews/summary?country=us` : star split of stored written reviews.
- `GET /developers/{artist_id}?country=us` : a publisher's apps with ratings, chart places and dates.
- `GET /apps/new?country=us&days=30&genre=` : recently released apps that already rank.
- `GET /apps/rising?country=us&days=7&genre=` : apps gaining ratings fastest, gained and percent per app.
- `GET /most-searched?country=us&month=&genre=&q=` : Apple Ads top terms per genre and month (100 rows anonymous).
- `GET /storefronts` : coverage per storefront (popularity month, charts, ratings scan, default language).

Signed in (`X-API-Key`):
- `GET /apps/search?q=&country=us&limit=10` : live App Store search.
- `GET /apps/lookup/{track_id}?country=us` : full record, cached 12h.
- `GET /keywords/analyze?q=a,b,c&country=us&app_id=` : analyze up to 25 keywords now.
- `GET /keywords/{term}/history?country=us` : monthly popularity per genre.
- `POST /apps/{track_id}/keywords/scan` : find and analyze candidate keywords for an app.
- `GET /apps/{track_id}/overview?country=us` : keywords, the app it loses to, next steps.
- `GET /apps/{track_id}/reviews?country=us&limit=50` : written reviews with the rating distribution.
- `GET /projects`, `GET|POST /keywords/tracked`, `DELETE /keywords/tracked/{id}` : your projects and keyword lists.
- `GET /me/week` : this week for every app you follow.

## Notes
- `country` is a lowercase ISO-3166 alpha-2 code (`us`, `gb`, `in`); default `us`.
- `track_id` is the numeric App Store id (`389801252` = Instagram); `artist_id` the numeric developer id.
- Popularity is Apple Ads' 5-100 scale for the month; difficulty is 0-100 from the strength of the top 10.
- No rate limits are enforced; live lookups are cached, be reasonable. Keep API keys out of client code and logs.