prelaunch-radar/new-shopify-stores-pre-launch-radar
prelaunch-radar--new-shopify-stores-pre-launch-radarDestructive
This tool calls the Actor "prelaunch-radar/new-shopify-stores-pre-launch-radar" and retrieves its output results. Actor description: New Shopify stores, including pre-launch stores behind a password page, detected from public Certificate Transparency logs, with RDAP registration date, niche, country and catalog counts. Also checks any domain for Shopify. Flat JSON for AI agents and MCP. Zero personal data.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | feed = list newly detected Shopify stores. enrich = check your own list of domains (fill 'domains'). Example values: "feed" | feed |
| cursor | No | feed mode only. Leave empty to use 'Detected in the last N days'. Put 'latest' once to get the current position without being charged, or 0 to start from the oldest store in the 30-day feed. Each run returns nextCursor in the OUTPUT record (and a 'cursor' field on every item): pass it to the next run to receive only stores added since, never the same store twice. Filters apply before billing. Stores excluded by your filters are skipped for good. | |
| niches | No | feed mode only. Keep only these niches. Empty = all niches. | |
| status | No | feed mode only. 'pre-launch' = store still behind its password page; 'live' = open storefront. Example values: "any" | any |
| domains | No | enrich mode only. Domains or URLs, one per item, e.g. example.com. Up to maxItems are checked. | |
| maxItems | No | Hard cap on the number of billed results (stores or domains) for this run. Example values: 100 | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| countries | No | feed mode only. ISO 3166-1 alpha-2 codes of the store's country, e.g. US, GB, FR. Empty = all countries. | |
| sinceDays | No | feed mode only, used when 'cursor' is empty. Return stores first detected in the last N days (1 = yesterday and today). Overlapping windows return (and bill) the same stores again: use 'cursor' for scheduled runs. Example values: 7 | |
| maxFeedAgeHours | No | feed mode with a cursor only. If the collector has not refreshed the feed for this long, the run fails without delivering or charging anything, and your cursor stays valid. Example values: 26 | |
| maxCheckAgeHours | No | feed mode only, optional. Keep only stores whose live / pre-launch status was re-checked in the last N hours (see 'status_checked_at'). Empty = no freshness filter. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |