# Public Website Tech Stack Signal Agent (`jacksu/public-website-tech-stack-signal-agent`) Actor

Detect public website technology, tracking, marketing, commerce, payment, CDN, and frontend stack signals from visible HTML evidence.

- **URL**: https://apify.com/jacksu/public-website-tech-stack-signal-agent.md
- **Developed by:** [jack su](https://apify.com/jacksu) (community)
- **Categories:** Business, Automation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 useful tech stack results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Public Website Tech Stack Signal Agent

Detect public website technology and tracking-stack signals from visible HTML evidence: frontend frameworks, CMS hints, analytics, ad pixels, tag managers, marketing automation, forms, chat tools, commerce platforms, payment hints, CDN/script hosts, and source snippets.

This Actor is built for AI sales agents, market research, technographic segmentation, competitive intelligence, and website QA workflows that need a compact evidence record without running a browser or scraping private platforms.

### What It Returns

- Detected technologies with category, evidence type, evidence text, evidence URL, and confidence context.
- Category summaries for analytics, ad pixels, tag managers, frontend frameworks, CMS, marketing automation, chat/support, commerce, payment, CDN, and scheduling/forms.
- Script hosts and evidence snippets that explain why each tool was detected.
- Optional focus-tool matches, diagnostics, change status, and a stable `stackHash`.

### Pricing Behavior

The Actor uses pay-per-event pricing and only charges the useful result event when it finds useful public technology-stack evidence.

It does not charge the useful event for:

- invalid or private-network URLs;
- failed fetches;
- pages with no technology signals;
- focus-tool misses;
- unchanged records when you pass a previous `stackHash`.

`apify-default-dataset-item` is intentionally not used.

### Safety

- Public HTTP/HTTPS pages only.
- Private-network hosts, credentials, query strings, fragments, path parameters, and token-like account paths are rejected.
- JavaScript is not executed.
- External scripts, iframes, APIs, and pixels are not fetched; only visible HTML references are recorded.
- Output is evidence-based and does not infer hidden backend systems.

### Example Input

```json
{
  "startUrls": [
    "https://www.example.com/"
  ],
  "focusTools": [
    "HubSpot",
    "React"
  ],
  "requestTimeoutSecs": 20
}
```

### Best Use Cases

- Qualify companies by public technographic evidence before sales outreach.
- Identify websites using specific marketing, analytics, commerce, or payment tools.
- Monitor stack changes without paying for unchanged results.
- Feed AI agents structured evidence instead of raw HTML.

# Actor input Schema

## `startUrls` (type: `array`):

Public HTTP/HTTPS page URLs. Query parameters, fragments, credentials, path params, private-network hosts, and token-like account paths are rejected.

## `focusTools` (type: `array`):

Optional tool or stack terms that must appear in detected evidence for the useful event to be charged, such as HubSpot, Shopify, Stripe, React, Google Analytics, or Meta Pixel.

## `previousStackRecords` (type: `array`):

Optional previous records from this Actor. If the stable stackHash is unchanged, the result is written without charging the useful event.

## `requestTimeoutSecs` (type: `integer`):

Maximum time in seconds to wait for the public page response.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.apify.com/"
  ],
  "focusTools": [],
  "previousStackRecords": [],
  "requestTimeoutSecs": 20
}
```

# Actor output Schema

## `datasetId` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jacksu/public-website-tech-stack-signal-agent").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jacksu/public-website-tech-stack-signal-agent").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jacksu/public-website-tech-stack-signal-agent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jacksu/public-website-tech-stack-signal-agent"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Zda0lFUzeTDI1TtrK/builds/amGDySBiiEL1lO0U2/openapi.json