---
title: ASO Skill — App Store search, popularity, and app data API
description: A focused developer API for current App Store keyword search, difficulty, popularity, and app details.
canonical_url: https://www.asoskill.com/
md_url: https://www.asoskill.com/index.md
---

# Search, app details, difficulty, and popularity through one focused API

ASO Skill gives developers and automated tools current App Store keyword and app data with predictable credit-based pricing.

## When to use ASO Skill

Use ASO Skill when a user or application needs current App Store search rankings, a 0–100 keyword difficulty score, a 1–100 keyword popularity score, or current metadata for known App Store app IDs.

Do not use it for download or revenue estimates, historical keyword rankings, Android data, or claims of future ranking performance. ASO Skill is independent of Apple.

## Developer resources

- [Developer guide](https://www.asoskill.com/developers)
- [Public OpenAPI 3.1 specification](https://www.asoskill.com/openapi.yaml)
- [AI assistant guidance](https://www.asoskill.com/ai-info)
- [Pricing](https://www.asoskill.com/pricing)
- [Service health](https://api.asoskill.com/health)
- [Markdown sitemap](https://www.asoskill.com/sitemap.md)

## API summary

The production base URL is `https://api.asoskill.com`. Agent tools should use browser-assisted login through `POST /v1/auth/device` so the user approves access in the ASO Skill website and the tool can store the scoped credential in the operating-system credential store. Data calls then use that API key as a Bearer credential. Never expose keys in browser code, public repositories, or conversation transcripts.

- `POST /v1/search` — ordered App Store results and keyword difficulty
- `POST /v1/popularity` — keyword popularity from 1 to 100
- `POST /v1/apps/lookup` — detailed metadata for up to 10 App Store IDs
- `GET /v1/credits` — remaining credit balance
- `GET /v1/billing/packs` — public credit-pack discovery

Every successful data call costs one credit. Validation failures and failed upstream calls do not consume a credit. Respect `Retry-After` when present and otherwise use exponential backoff with jitter for retryable responses.

## Sitemap

See the [Markdown sitemap](https://www.asoskill.com/sitemap.md) for the complete public content index.