# Website Tech Stack Detector with Evidence (`lygos/website-tech-sales-intelligence`) Actor

Low-cost Wappalyzer and BuiltWith alternative for bulk technology detection with confidence scores, optional evidence, DNS controls, and TLS details.

- **URL**: https://apify.com/lygos/website-tech-sales-intelligence.md
- **Developed by:** [Alejandro Schulten](https://apify.com/lygos) (community)
- **Categories:** Developer tools, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Website Tech Stack Detector with Evidence

Bulk website technology detection for Apify with the signal behind each result. Each successful dataset row contains the detected stack, confidence scores, optional evidence, company metadata, public social profiles, DNS email controls, and TLS details.

### Why this Actor

- One input: a list of public website URLs.
- No API keys or paid upstream providers.
- Optional evidence from HTML, scripts, headers, DNS, and explicit dependency inference instead of unexplained labels.
- Compact JSON suitable for CRM enrichment, market research, competitor monitoring, MCP, and automation.
- HTTP-only execution keeps platform costs low and predictable.

### Input

```json
{
  "urls": [
    { "url": "https://example.com" },
    { "url": "https://shopify.com" }
  ],
  "crawlPages": 0,
  "minimumConfidence": 50,
  "includeEvidence": false,
  "concurrency": 3,
  "timeoutSeconds": 15
}
```

Set `crawlPages` to `1` through `3` when contact and company-page enrichment matters more than speed. JavaScript rendering is intentionally disabled in the MVP to keep execution cost and failure rates low.

### Verified output example

The Actor writes one charged dataset item per successfully analyzed domain. Failed or blocked URLs are recorded in the uncharged `OUTPUT` summary.

This abbreviated result was produced from `https://stripe.com/` with `crawlPages: 0`, `minimumConfidence: 50`, and `includeEvidence: true` on September 30, 2026. The omitted fields contain company metadata, public social profiles, DNS controls, and TLS certificate details from the same run.

```json
{
  "inputUrl": "https://stripe.com/",
  "finalUrl": "https://stripe.com/",
  "status": 200,
  "technologyCount": 7,
  "technologies": [
    {
      "name": "Google Workspace",
      "categories": ["mail-provider"],
      "version": null,
      "confidence": 94.5,
      "inferred": false,
      "evidence": [
        {
          "source": "dns-mx",
          "subject": "MX",
          "match": "aspmx.l.google.com",
          "reliability": 0.9
        }
      ]
    },
    {
      "name": "Next.js",
      "categories": ["js-framework", "backend-framework"],
      "version": null,
      "confidence": 93.5,
      "inferred": false,
      "evidence": [
        {
          "source": "html",
          "subject": "html",
          "match": "id=\"__NEXT_DATA__\"",
          "reliability": 0.55
        },
        {
          "source": "script-src",
          "subject": "script[src]",
          "match": "/_next/static/chunks/",
          "reliability": 0.8
        }
      ]
    },
    {
      "name": "Nginx",
      "categories": ["web-server"],
      "version": null,
      "confidence": 88,
      "inferred": false,
      "evidence": [
        {
          "source": "header",
          "subject": "server",
          "match": "nginx",
          "reliability": 0.88
        }
      ]
    },
    {
      "name": "Amazon Route 53",
      "categories": ["devops"],
      "version": null,
      "confidence": 85,
      "inferred": false,
      "evidence": [
        {
          "source": "dns-ns",
          "subject": "NS",
          "match": "awsdns",
          "reliability": 0.85
        }
      ]
    },
    {
      "name": "Node.js",
      "categories": ["runtime"],
      "version": null,
      "confidence": 79.5,
      "inferred": true,
      "evidence": [
        {
          "source": "implied",
          "subject": "Next.js",
          "match": "Next.js"
        }
      ]
    },
    {
      "name": "React",
      "categories": ["js-framework", "ui-framework"],
      "version": null,
      "confidence": 79.5,
      "inferred": true,
      "evidence": [
        {
          "source": "implied",
          "subject": "Next.js",
          "match": "Next.js"
        }
      ]
    },
    {
      "name": "Amazon Web Services",
      "categories": ["hosting"],
      "version": null,
      "confidence": 72.3,
      "inferred": true,
      "evidence": [
        {
          "source": "implied",
          "subject": "Amazon Route 53",
          "match": "Amazon Route 53"
        }
      ]
    }
  ],
  "company": {
    "companyName": "Stripe",
    "about": "Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes."
  },
  "social": {
    "x": ["stripe"],
    "linkedin": ["stripe"],
    "github": ["stripe"]
  },
  "security": {
    "dns": {
      "spf": true,
      "dmarc": true,
      "caa": true,
      "dmarcPolicy": "reject",
      "dkim": true
    },
    "certInfo": {
      "issuer": "DigiCert, Inc.",
      "protocol": "TLSv1.3"
    }
  }
}
```

Technology and website output can change over time. The example is a verified snapshot, not a hard-coded fixture or accuracy guarantee.

### Pricing

Pay per event with platform usage included:

| Event | Price |
|---|---:|
| `apify-default-dataset-item` | USD 0.020 per successful website |
| `apify-actor-start` | USD 0.00005 per run |

Apify keeps 20% and subtracts platform execution costs. Free-plan users do not generate developer revenue, although Apify covers their platform usage.

### Local development

```bash
npm install
npm test
npm run check
npm start
```

Local input can be placed in `storage/key_value_stores/default/INPUT.json`.

### Operational limits

- Maximum 500 unique URLs per run.
- Only public HTTP(S) URLs on ports 80 and 443 are accepted.
- Local, private, loopback, link-local, and other non-public addresses are rejected.
- Detection depends on what the target serves to the Apify worker. Geo-targeting and bot defenses can change results.
- Static HTTP analysis misses technologies injected only after JavaScript execution.
- Low-confidence HTML patterns can produce false positives. Raise `minimumConfidence` for stricter datasets and inspect `evidence` before using a detection for automated decisions.
- Technology-spend values are heuristic lower-bound signals, not verified vendor invoices or company expenditure.

Technology detection is powered by the MIT-licensed `opentechalyzer` package. This Actor provides hosted execution, bulk input, cost controls, result normalization, Apify datasets, scheduling, API access, MCP discovery, and agentic payments.

# Actor input Schema

## `urls` (type: `array`):

Public HTTP or HTTPS websites to analyze.

## `crawlPages` (type: `integer`):

Crawl likely contact and company pages for richer enrichment. Higher values take longer.

## `includeEvidence` (type: `boolean`):

Include the matched header, cookie, HTML, or script signal for every technology.

## `minimumConfidence` (type: `integer`):

Exclude technology detections below this confidence score.

## `concurrency` (type: `integer`):

Number of websites analyzed at once.

## `timeoutSeconds` (type: `integer`):

Maximum time allowed for each individual network request.

## Actor input object example

```json
{
  "urls": [
    {
      "url": "https://example.com"
    }
  ],
  "crawlPages": 0,
  "includeEvidence": false,
  "minimumConfidence": 50,
  "concurrency": 3,
  "timeoutSeconds": 15
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `dataset` (type: `string`):

No description

## `summary` (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 = {
    "urls": [
        {
            "url": "https://example.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lygos/website-tech-sales-intelligence").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 = { "urls": [{ "url": "https://example.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("lygos/website-tech-sales-intelligence").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 '{
  "urls": [
    {
      "url": "https://example.com"
    }
  ]
}' |
apify call lygos/website-tech-sales-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lygos/website-tech-sales-intelligence"
        }
    }
}
```

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/crajuxYV42pDK2vrP/builds/zrPBRrwWmp0uScGUu/openapi.json