ASO data for indie apps, without the enterprise bloat.
Import any app, refresh keyword rankings, discover competitors, and keep the same workflow available in the dashboard, API, and MCP when you want automation.
Stores supported
2
App Store + Google Play
Workflow surfaces
3
Dashboard, API, MCP
Starting plan
$9.99
Built for indie teams
Core workflow
Everything you need to import apps, inspect keywords, and watch competitors
The product is strongest when it stays obvious. First you import an app. Then you refresh keywords. Then you build a competitor view. Everything else exists to make those three actions easier to repeat.
Import any app in seconds
Start from a bundle ID, package name, URL, or store search and turn it into one clean app record without copy-pasting metadata into spreadsheets.
Track keywords without manual searching
Refresh keyword rankings, keep recent snapshots, and spot movement quickly instead of opening both stores and checking terms one by one.
Find competitors before they outrank you
Auto-discover nearby competitors, compare visible metadata, and build a sharper watchlist before your next update ships.
How it works
From one app import to a usable ASO workflow
Import app
Resolve a real App Store or Google Play listing from search, URL, or app identifier and keep the core metadata in one workspace.
Refresh keywords
Run lightweight checks when you need quick answers or push heavier refreshes to the queue when you want cleaner margins and less waiting.
Discover competitors
Generate a competitor set from tracked keywords, compare app positioning, and keep the same dataset available in API and MCP workflows.
Why developers pay
You are not paying for a wrapper. You are paying for a maintained workflow.
One shared data model
Apps, keywords, competitors, snapshots, and crawl jobs stay aligned across the dashboard, API, and MCP instead of drifting into separate products.
Async refreshes when the work gets heavy
Live checks are there for fast answers, while the expensive store refreshes move behind a worker so users do not sit through slow requests.
Cache and history that still feel useful
Recent ranking snapshots stay visible long enough to compare movement, without turning storage growth into the business model.
Developer access when you need automation
Use the web app for fast answers, then move the same operations into scripts, CI, Claude, or Cursor when you want repeatable workflows.
Dashboard first
Solo dev shipping updates
Import your app, refresh a few core keywords before release, and check whether the competitor set changed after the update.
API first
Growth workflow with scripts
Pull apps, keyword states, and usage through the API so ranking checks and metadata refreshes become part of your own release workflow.
MCP first
Agent-powered ASO research
Let Claude or Cursor inspect tracked apps, call keyword tools, and summarize competitor movement without leaving the environment where you already work.
Developer surfaces
Use the UI when you want answers. Use the API when you want automation.
The same workflow should work in a browser, in your scripts, and inside AI tools. That is why dashboard, API, and MCP are not separate products here.
Dashboard
Use the UI when you want answers
Open one workspace, inspect recent snapshots, and understand what changed without reading raw responses.
API
Use the API when you want automation
Move app import, keyword refresh, competitor discovery, and usage checks into scripts, internal tools, and CI tasks.
MCP
Use MCP when the workflow lives in AI tools
Bring the same ASO context into Claude, Cursor, and agent workflows without building and maintaining a separate integration layer.
Real workflow example
Queue a refresh in the product, read the result anywhere.
POST /api/v1/keywords/refresh
Authorization: Bearer $APPTIDE_API_KEY
{
"applicationIdentifier": "com.openai.chatgpt",
"country": "US",
"language": "en",
"keywords": ["chatgpt", "ai assistant"],
"sync": false
}Pricing
Start small. Upgrade only when refresh volume grows.
The default plan is intentionally small-team friendly. You should not need enterprise buying power to run app import, keyword inspection, competitor discovery, and developer automation.
Sandbox
$0
Explore the docs, sample workflows, and the shape of the product before you wire it into a real app workflow.
Developer
$9.99
Built for solo builders who want real app import, keyword refresh, competitor discovery, and API + MCP access without owning the data stack.
Scale
Custom
Move up when refresh volume, automation depth, or workspace complexity outgrows the indie plan.
FAQ
Questions developers ask before adopting it
Why not build this myself?
Because the hard part is not adding one more wrapper. The hard part is keeping App Store and Google Play data usable over time, with refresh jobs, parsing, limits, history, and a clean workflow surface.
What does the $9.99 plan actually include?
It covers one workspace, tracked keywords, live refresh units, API access, MCP access, and a product shape that works for an indie app workflow instead of an enterprise procurement process.
Do I need to use the API?
No. You can stay in the dashboard if that is enough. The API and MCP exist for developers who want to automate ASO checks or bring them into their own tools.
Does this work for iOS and Android?
Yes. AppTide resolves data from the App Store and Google Play, then normalizes it into one workflow so you do not have to think about two separate toolchains.