canonical: https://jentic.com/apis/asoskill.com/asoskill

# ASO Skill Developer API

The ASO Skill API returns App Store Optimization data for mobile apps: it searches the App Store and calculates keyword difficulty, suggests keyword autocompletions, scores keyword popularity, and looks up detailed metadata for up to ten apps at once. It also exposes account tooling to read the current credit balance and discover or buy credit packs. Every successful data response costs one credit, while rejected requests and failed upstream calls do not, so an agent pays only for results it can use.

## For AI agents

Pull App Store Optimization data: search the App Store with keyword difficulty, get keyword autocomplete and popularity scores, look up app metadata in bulk, and read the connected account's credit balance.

## Scope

Does not handle app publishing, ad bidding, or Google Play data. Use for App Store keyword search, difficulty, popularity, and metadata only.

## Capabilities

- Search the App Store and calculate keyword difficulty for a term
- Suggest App Store keyword autocompletions from a seed query
- Score how popular a given App Store keyword is
- Look up detailed App Store metadata for up to ten apps in one call
- Read the connected account's current credit balance
- Discover available credit packs and start a hosted checkout

## Use cases

### Agent Keyword Research

An AI agent connected through Jentic researches App Store keywords for a new app: it searches for seed terms to read keyword difficulty, pulls autocomplete suggestions to widen the set, and scores each candidate's popularity. The agent returns a ranked shortlist of high-popularity, low-difficulty keywords without the developer touching a dashboard.

Example prompt: Search the App Store for a seed keyword, read its difficulty, fetch autocomplete suggestions, and return the three suggestions with the highest popularity score

### Competitor Metadata Audit

A growth team audits competitor listings by looking up detailed App Store metadata for up to ten apps in a single call. The ASO Skill API returns the structured listing fields the team compares against its own app, so a batch audit is one request rather than ten.

Example prompt: Look up metadata for ten competitor app IDs in one call and return each app's title and listing fields

### Credit-Aware Automation

Because every successful data response costs one credit, a scheduled ASO job checks the account credit balance before it runs and skips or pauses when the balance is low. The ASO Skill API also lists credit packs and starts a hosted checkout, so the workflow can surface a top-up prompt instead of failing mid-run.

Example prompt: Read the current credit balance and, if it is below a threshold, list the available credit packs

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/search` | Search the App Store and calculate keyword difficulty |
| POST | `/v1/autocomplete` | Return App Store keyword autocomplete suggestions |
| POST | `/v1/popularity` | Return a keyword popularity score |
| POST | `/v1/apps/lookup` | Look up metadata for up to ten apps |
| GET | `/v1/credits` | Read the current credit balance |
| GET | `/v1/billing/packs` | Discover available credit packs |

## Key resources

- **Data** — Search, autocomplete, popularity, and app metadata lookups that each cost one credit on success
- **Credits** — Read the connected account's credit balance
- **Billing** — Discover credit packs and start a hosted checkout
- **Authentication** — Browser-assisted agent login and calling-key revocation

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 34 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 84 / 100
- **View full report:** https://jentic.com/apis/asoskill.com/asoskill/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the ASO Skill API by hand means managing a bearer API key, tracking the credit balance each successful call draws down, and handling the browser-assisted device login for agents yourself. Through Jentic you install once, import the ASO Skill API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The ASO Skill API carries each query in the request body, so a rule bounds which operations your agent may call, not which keyword. You choose the operations it may call, so the billing-checkout and credential-revocation operations are not included unless you add them.
- **Credential handling:** Your ASO Skill API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'App Store keyword difficulty' or 'keyword popularity score', and Jentic returns the matching ASO Skill operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Semrush** — Semrush does web search keyword research and difficulty rather than App Store ASO.
- **Ahrefs** — Ahrefs covers web keyword and backlink metrics, a different surface from App Store keyword data.
- **Moz** — Moz adds web domain and keyword authority signals alongside ASO Skill's App Store metrics.

## FAQ

### What authentication does the ASO Skill API use?

The ASO Skill API authenticates data and credit calls with a bearer API key in the Authorization header, per its OpenAPI spec, and the hosted MCP endpoint also accepts an OAuth2 token. A few operations, such as the discovery and health checks and the device-login flow, need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

### Can I find low-competition App Store keywords with the ASO Skill API?

Yes. Search returns keyword difficulty for a term, autocomplete widens a seed into related keywords, and the popularity endpoint scores demand for each one. Combining them lets an agent shortlist keywords that are popular but not heavily contested.

### What are the rate limits for the ASO Skill API?

The OpenAPI spec meters usage by credits rather than stating a fixed request-per-second rate limit: each successful data response costs one credit, and rejected or failed calls cost none. Check https://www.asoskill.com for any throughput limits and current credit pricing.

### Is there an ASO Skill MCP server?

Yes, ASO Skill offers a hosted MCP server reached over an OAuth2 token. You can also connect the ASO Skill API directly through Jentic: your agent gets the full 13-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

### Can I limit what my agent is allowed to do with the ASO Skill API?

Yes. Write a rule that allows only the data operations the agent needs, such as search, autocomplete, and popularity, and leave out the billing-checkout and credential-revocation operations. The agent can then research keywords and read metadata but cannot spend money or revoke the key, and the agent's calls are logged.

### How do I research a keyword's difficulty through Jentic?

Import the ASO Skill API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'App Store keyword difficulty'. Jentic returns the search operation with its input schema so the agent sends the query and reads back the difficulty score. To run it on your own infrastructure, install Jentic One from its GitHub repo.