Documentation
App Revs exposes Apple's public App Store data two ways: a REST API, and an MCP server whose 28 tools call it. 15 of the tools and every stored-data endpoint work without an account.
Introduction
- Keywords: popularity (Apple Ads, monthly, 90 stores), difficulty with its inputs, the top 10, 15 months of history, the 500 most searched per genre.
- Apps: the terms an app ranks for, its competitors from shared terms, chart places in 20 stores, ratings by day, written reviews and their summary.
- Publishers and the store: every app a publisher sells; apps rising by ratings; apps launched lately that already rank.
- Your account (with a key): the apps you follow, their keyword lists per store, nightly positions, this week's movement.
Two ways in, same data: the MCP server at https://api.apprevs.com/mcp for Claude, Cursor, ChatGPT and any MCP client; the REST API at https://api.apprevs.com/api/v1 for everything else.
Authentication
Stored data needs no key. Live App Store lookups, keyword analysis on demand, and anything about your own apps take one. Sign in with Google, open Settings, generate a key; it is shown once.
X-API-Key: ar_live_your_api_keyAuthorization: Bearer ar_live_your_api_keyQuickstart
The public keyword endpoint, no key:
curl "https://api.apprevs.com/api/v1/keywords/habit%20tracker?country=us"Claude Code, with a key, then ask it anything on the site:
claude mcp add --transport http apprevs https://api.apprevs.com/mcp --header "Authorization: Bearer ar_live_..."A script analyzing three terms for an app in the German store:
curl "https://api.apprevs.com/api/v1/keywords/analyze?q=habit%20tracker,streaks,routine&country=de&app_id=6443918070" -H "X-API-Key: ar_live_..."Connect lines for Claude.ai, Cursor and ChatGPT are on the MCP page.
Endpoints
Every endpoint by whether it needs a key. Parameters, examples and response shapes are in the API reference; errors, rate limits and conventions are at the top of it.