# Asolytics Api > Use the Asolytics Public API for ASO research and automation. Trigger this skill when the agent needs to query app metadata, availability, versions, installs, revenue, rankings, keyword metrics, live search results, recommended keywords, tracked keywords, tracking folders, competitors, projects, balance, or store charts from Asolytics. Also use it when a user wants curl examples, lightweight inte… - **Type:** Skill - **Install:** `agentstack add skill-asolytics-pro-asolytics-app-store-optimization-api-asolytics-api` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [Asolytics-Pro](https://agentstack.voostack.com/s/asolytics-pro) - **Installs:** 0 - **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [Asolytics-Pro](https://github.com/Asolytics-Pro) - **Source:** https://github.com/Asolytics-Pro/asolytics-app-store-optimization-api/tree/main/skills/asolytics-api - **Website:** https://asolytics.pro/ ## Install ```sh agentstack add skill-asolytics-pro-asolytics-app-store-optimization-api-asolytics-api ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Asolytics Public API ## Overview Use this skill to work against the Asolytics Public API safely and efficiently. Prefer the bundled references over re-discovering the API from scratch, and refresh the spec before relying on exact request or response shapes if the docs may have changed. ## Workflow 1. Read [references/api-overview.md](references/api-overview.md) first for auth, base URL, and endpoint families. 2. Read [references/endpoints.md](references/endpoints.md) when you need endpoint-level parameters or request body fields. 3. Read [references/openapi.json](references/openapi.json) only when exact schema details or edge cases matter. 4. Prefer small, cheap requests first because the API is alpha and some endpoints consume tokens. 5. Use `GET /public-api/v1/balance` when token awareness matters before running a wide query. ## Auth Send the personal public API token in the `X-PUBLIC-API-TOKEN` header. Prefer an environment variable such as `ASOLYTICS_PUBLIC_API_TOKEN` instead of pasting secrets into files or commits. If the token is missing, ask the user for it. If they don't have one yet, walk them through getting it: 1. Create a free Asolytics account (or log in): https://app.asolytics.pro/login 2. Open the profile page and copy the public API token: https://app.asolytics.pro/profile 3. Export it locally so it isn't pasted into chats or commits: `export ASOLYTICS_PUBLIC_API_TOKEN=""` Do this before running any write or paid requests. ```bash curl -sS \ -H "X-PUBLIC-API-TOKEN: $ASOLYTICS_PUBLIC_API_TOKEN" \ "https://app.asolytics.pro/public-api/v1/balance" ``` ## Common Patterns ### Catalog Bootstrap Resolve lookup data before building other requests: 1. Countries 2. Locales 3. Devices 4. Categories 5. Clusters 6. Projects This avoids guessing valid `store`, `country_code`, `device`, `category_key`, `cluster_key`, and `project_id` values. ### App Intelligence Use the Applications endpoints for: - current listing metadata - screenshots and media - store availability - version history - installs and revenue history - ranking history Start with the narrowest possible app set because some metadata endpoints bill per returned pair. ### Keyword Workflows Use the Keywords and Recommended Keywords endpoints for: - ranking history - popularity history - latest keyword metrics - live search top 50 - recommended keyword review - async rank tracking jobs with optional webhook callbacks When the user wants automation, prefer plain HTTP calls and return the exact request payload you used. ### Tracking Maintenance Use Tracking Keywords and Tracking Folders for: - listing tracked keywords - adding tracked keywords - deleting tracked keywords by `keyword_ids` - creating folders - renaming folders - adding or removing keywords inside folders Fetch first, mutate second. For delete operations, resolve ids and current contents before issuing the write request. ### Competitors and Charts Use Competitors and Store Charts for: - listing current competitors - marking or unmarking a competitor - retrieving top-500 charts by store, country, cluster, category, and device ## Guardrails - Treat the API as unstable unless the current OpenAPI spec confirms the shape you expect. - Do not hardcode secrets in source files, shell history snippets, or Git commits. - Call out token-related costs when a request fans out across many apps, locales, or keywords. - Prefer read-only endpoints before any state-changing request. - Echo the exact endpoint, query parameters, and JSON body in your answer when the user asks for integration help. ## Staying Up To Date This skill is versioned (see the `version` in the frontmatter above and the `VERSION` file). A newer version may be published on GitHub. When this skill is first invoked in a session, do a lightweight update check (skip silently if offline or if it fails): 1. Read the local version from the `VERSION` file in this skill folder. 2. Fetch the latest published version: `https://raw.githubusercontent.com/Asolytics-Pro/asolytics-app-store-optimization-api/main/skills/asolytics-api/VERSION` 3. If the remote version is greater than the local one, tell the user a new version is available and what changed, then **offer** to update — don't update without asking. 4. If they accept, run `scripts/update.sh` from this skill folder. It backs up the current folder and overlays the latest files from GitHub in place. Then confirm the new version from `VERSION`. Do not check more than once per session, and never block real work on the check. ## Resources - `VERSION`: current skill version, used for the self-update check. - `references/api-overview.md`: fast orientation and usage guidance. - `references/endpoints.md`: generated endpoint inventory grouped by tag. - `references/openapi.json`: raw public OpenAPI snapshot. - `scripts/sync_openapi.py`: refresh the OpenAPI snapshot and regenerate `endpoints.md`. - `scripts/update.sh`: update this installed skill to the latest GitHub version. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [Asolytics-Pro](https://github.com/Asolytics-Pro) - **Source:** [Asolytics-Pro/asolytics-app-store-optimization-api](https://github.com/Asolytics-Pro/asolytics-app-store-optimization-api) - **License:** MIT - **Homepage:** https://asolytics.pro/ Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-asolytics-pro-asolytics-app-store-optimization-api-asolytics-api - Seller: https://agentstack.voostack.com/s/asolytics-pro - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.