StackScope

Delete one of the customer's watches by id, from list_watches. Deliveries stop immediately. Free.

Set up a standing watch that delivers newly discovered matching sites on a schedule. Narrow it by technology, keyword, category, country, distance from a place or whether the site publishes a contact route; a completely unfiltered watch needs a plan that allows the every-site stream. Free to create, but delivered sites count against the monthly site allowance, and plans limit how many watches, technologies and keywords you may have. A webhook watch returns its signing secret exactly once when it is created.

A bulk export of matching sites, up to 5,000 at once, for building a list or loading into a spreadsheet. Same filters as find_sites. Ask for csv output if the result is going into a file. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call and needs no export. Counts one site from the monthly allowance for each site not already returned to you this period, so this is the call most likely to ask you to confirm first.

Find newly launched sites matching any combination of technology, category, country, distance from a place, date range and contact availability. This is the main search tool. For example: sites in the UK built with WordPress that launched this week and have a contact email, or Shopify shops within 30 miles of Bristol. Each site carries its town, and its distance when near is given. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call. Counts one site from the monthly allowance for each site not already returned to you this period; you may be asked to confirm before a large result is returned.

The catalogue of technologies we track, with how many sites use each. Use this to find the exact technology name to pass to the other tools. Counts no site allowance.

Everything known about one website: when it launched, what it is, and the technologies detected on it. Give a domain such as example.com (a full URL works too). Returns found: false if the site is not in the corpus. When found, counts one site from the monthly allowance.

Counts and shares, not a list: for the sites matching a filter, how many use each technology, grouped by kind (payments, analytics, hosting, cms...). Answers any question of the form 'how many', 'what share', or 'which X do sites using Y use' in one call, for example 'what payment providers do Ghost sites use'. Use this BEFORE find_sites or export_sites for those questions; exporting rows and counting them costs hundreds of lookups for the same answer. Same filters as find_sites. Counts one Explore slice and no site allowance.

Sites detected using one specific technology, newest first. Use find_sites instead when combining a technology with a country, category or contact filter. For counts, shares or 'which X do these sites use', call stack_breakdown instead; it answers in one call. Counts one site from the monthly allowance for each site not already returned to you this period.

Weekly adoption of one technology over the whole period we have data for, counted across every site in the corpus, with notes marking anything that changed how it is measured. Same population as list_technologies, so the two can be compared. Counts no site allowance.

What this connection can do and how much allowance is left: the plan, the permissions granted, and how many more distinct sites may be returned before the monthly allowance is used up. Calls themselves are not capped. Free. Worth calling before a large query.

The customer's watches, including inactive watches and their current status. A watch can deliver new matching sites by email, Slack or webhook as they are discovered, or keep matches in the account portal. Free.