DataPussy is API-first. The dashboard is one client among several, and it doesn't get anything the API can't give you. A single contract defines every resource, every filter and every estimate, and the REST API, the OpenAPI spec, the SDK and the MCP server are all generated from it.
REST v1
- Resources: apps (with estimates, rankings, countries, versions, in-app purchases, reviews and changes), companies, charts, ads, videos, keywords, screens, watchlists, alerts, webhooks, events, exports, meta and usage.
- App ids look like
app_…, and the API also acceptsios:123andgp:com.example.app. - Filters as
field[op]=value, or a JSON body onPOST /v1/apps/search. fields,expandandviewto get exactly the shape you need.- Cursor pagination pinned to a
snapshot_id, so pages don't shift under you mid-scan. - Errors as RFC 9457 problem details, with a type you can switch on.
Idempotency-Keyon writes, so a retry never does the work twice.dry_runto price a request andmax_creditsto cap it.X-Credits-*andRateLimit-*headers on every response.p10andp90in every view, including the concise one.
Example request and response headers — illustrative, not real data:
curl -X POST "https://api.datapussy.com/v1/apps/search?dry_run=true&max_credits=200" \
-H "Authorization: Bearer $DATAPUSSY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"filters": {"store": "ios", "country": "US", "category": "health-fitness"}, "view": "concise"}'
# HTTP/1.1 200 OK
# X-Credits-Estimated: 50
# X-Credits-Remaining: 2950
Webhooks and Events
Watchlists and alerts can deliver to email or to your endpoint. Webhook deliveries are signed with HMAC following the Standard Webhooks spec and retried on failure. Every event also lands in GET /v1/events, so a deploy or an outage on your side never means a lost change.
The MCP Server
The MCP server exposes 14 tools, written by hand on top of the same operations as the API:
apps_search— filter and sort apps with the same grammar as the API.apps_get— one app: metadata, current estimates and provenance.apps_timeseries— rank, ratings and estimate history over time.charts_get— a store chart for a country, category and date.ads_search— ads by app, country or date (Beta).videos_search— short-form videos linked to apps as mentions (Beta).creators_search— creators derived from our corpus, with attribution confidence (Beta).keywords_analyze— keyword popularity and our own difficulty index.reviews_query— review aggregates and velocity, with review text marked untrusted.screens_search— store screenshots analyzed into structured data (Beta).changes_list— what changed: prices, versions, metadata, ranks and availability.watchlists_manage— create and edit watchlists. The only tool that writes.meta_reference— countries, categories, charts, the filter catalog and method versions.account_usage— your plan, credits left and rate limits.
Each tool returns structuredContent with an outputSchema, plus the cost and the cursor. Results come in a concise view, light on tokens, or a detailed one with full provenance. Both keep P10 and P90. Text written by third parties, such as reviews and ad copy, is marked as untrusted so your agent doesn't take instructions from it. Sign-in uses OAuth 2.1 with PKCE, and the server speaks MCP revision 2026-07-28 with negotiation for older clients.
Plans at Launch
- Free — $0, 250 credits a month, 10 requests a minute. No card.
- Indie — $29 a month or $290 a year, 3,000 credits, 60 requests a minute.
- Team — $99 a month or $990 a year, 15,000 credits, 5 seats, 300 requests a minute.
- Packs that never expire — 5k credits for $59, 25k for $225, 100k for $700.
API keys start with purr_live_. The CLI is called purr too: purr apps search runs the same query as the API. Refunds within 14 days, and canceling takes two clicks.
