New Shopify Stores Radar & Shopify Checker (Pre-Launch)

Find new Shopify stores from public Certificate Transparency logs, usually within an hour of their domain's first HTTPS certificate (median 0.4 h, measured on 4,168 stores on 2026-10-05), including stores still behind their password page: 43% of those 4,168 stores showed a password page when first detected. The radar samples the public logs, so it does not catch every new Shopify store.

Want the full raw database directly? Download the full snapshot (4,000+ stores) for $4.99 — one CSV, no subscription, no API.

Built as a tool for AI agents as much as for people: one flat JSON object per store, stable field names, no nested pages to crawl, pay per result.

What it returns

Field	Type	Meaning
store_domain	string	Public domain of the store
store_name	string | null	Storefront name
status	live | pre-launch	pre-launch = password page, not open yet; observed at status_checked_at
status_checked_at	YYYY-MM-DD HH:MM UTC	Last successful check of the status (stores are re-checked about every 12 h)
status_since	YYYY-MM-DD HH:MM UTC	First check that saw the current status
niche	string	One of 16 niches (from public product titles and types), General store or Unknown (no products yet)
country, region, currency	string | null	Store-level settings published by the storefront
products, collections	integer | null	Public catalog counts
ships_to	integer | null	Number of shipping countries
product_types, sample_titles	string | null	Short public catalog preview
domain_registered	YYYY-MM-DD | null	Registration date from the official RDAP registry
first_detected	YYYY-MM-DD	Day the radar first saw the store (feed mode)
cursor	integer	Position of the store in the feed (feed mode); see Only new stores below

In Check my domains mode each row also has input, is_shopify (boolean) and dns_status.

Example item (illustrative values):

{
  "store_domain": "example-store.com",
  "store_name": "Example Store",
  "status": "live",
  "niche": "Health & Supplements",
  "country": "GB",
  "region": null,
  "currency": "GBP",
  "products": 12,
  "collections": 3,
  "ships_to": 41,
  "product_types": "Supplements",
  "sample_titles": "Pre-Workout – Watermelon (380g)",
  "domain_registered": "2026-09-20",
  "first_detected": "2026-09-26",
  "status_checked_at": "2026-10-05 09:40 UTC",
  "status_since": "2026-10-01 14:02 UTC",
  "cursor": 4012
}

Business-level data only: no emails, no phone numbers, no names of people.

Modes

• New stores feed ("mode": "feed") — stores detected in the last 30 days whose domain was registered in the last 30 days. Filter by status, niche, country and status-check age. The collector runs about every 2 hours when the host is up; each run's OUTPUT record shows the feed's age and the collector's longest gap over the last 7 days, and a feed older than maxFeedAgeHours (default 26) stops the run without billing.
• Check my domains ("mode": "enrich") — send domains; get whether each one runs on Shopify, its registration date, status, niche and catalog counts. Useful for automated lead enrichment and CRM clean-up.

For AI agents (MCP, API, x402)

• MCP: add this Actor as a tool in the Apify MCP server (https://mcp.apify.com/?tools=prelaunch-radar/new-shopify-stores-pre-launch-radar) and call it from Claude, ChatGPT, Cursor, CrewAI, LangChain or any MCP client.
• API: POST https://api.apify.com/v2/acts/prelaunch-radar~new-shopify-stores-pre-launch-radar/run-sync-get-dataset-items returns the JSON array directly.
• x402: agents can pay per call without an Apify account.
• Minimal inputs:
  • {"mode": "feed", "cursor": "latest"} — free, returns your starting position
  • {"mode": "feed", "cursor": "4012"} — only the stores added after position 4012
  • {"mode": "feed", "status": "pre-launch", "countries": ["US"], "maxItems": 50}
  • {"mode": "enrich", "domains": ["example.com"]}
• maxItems is a hard cap on billed results, so an agent's spend is bounded before the run.

Only new stores (scheduling)

Use the cursor, not sinceDays, for scheduled runs (Apify Schedules, n8n, Make, Zapier):

1. First run: "cursor": "latest" (nothing billed) or "cursor": "0" (the whole 30-day window).
2. Every run writes nextCursor to its OUTPUT record. Pass it as cursor next time.

Filters apply before billing and the cursor moves past filtered-out stores, so you never pay twice for the same store and never pay for stores you filtered out. If maxItems or your budget stops a run early, nextCursor points right after the last store delivered, so nothing is skipped. If your cursor is older than the 30-day window, OUTPUT.gap is true.

sinceDays still works, but overlapping windows (for example "sinceDays": 1 every day, which covers yesterday and today) deliver and bill the same stores again.

Pricing

Pay per result: you pay for each store delivered (feed) or each domain checked (enrich). Stores filtered out are never billed. Max results caps your spend.

Want the full raw database directly? Download the full snapshot (4,000+ stores) for $4.99.

Free 50-row sample (frozen on 2026-10-05) and stats by country and niche: Hugging Face dataset.

How it's built

Public Certificate Transparency logs (RFC 6962), public DNS records pointing to Shopify, the official RDAP registry, and each store's public /meta.json and /products.json.

LEGAL DISCLAIMER

This dataset is provided for market research, trend analysis, and competitive intelligence purposes only, on an "as-is" and "as-available" basis without warranties of any kind. Records originate exclusively from publicly accessible sources (Certificate Transparency logs, public DNS and RDAP registries, and stores' public storefront metadata); no personally identifiable information (PII) is collected or sold. Independently developed, not affiliated with, authorized, or endorsed by Shopify Inc. By accessing this data, you agree that the provider shall not be liable for any direct or indirect damages resulting from its use; in any event, liability is limited to the purchase price.