# Website Technology Detector (`nexgenwatch/website-technology-detector`) Actor

- **URL**: https://apify.com/nexgenwatch/website-technology-detector.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 website tech-stack checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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

## Website Technology Detector

Fingerprint the **technologies a website exposes on the pages its own `robots.txt` permits** — web server,
CDN, CMS / site builder, JavaScript frameworks, analytics and marketing tags — for buyer-supplied domains.
One scan per domain, and **every detection carries an evidence field**: the concrete response header or HTML
substring that triggered it, and where it was seen.

**Differentiation — the fleet-2-standard rebuild of the classic tech-lookup scraper (fleet-1 sibling:
`tech-stack-analyzer`).** The trust deltas are the whole point:

- **Robots honored.** The origin's `robots.txt` is fetched and **honored per origin before every fetch** —
  only pages the site permits are read. An origin that disallows the target pages is reported
  `ROBOTS_BLOCKED` and **skipped, never billed**.
- **Evidence, not guesses.** Each technology is reported with the exact header value or HTML fragment that
  matched, so you can audit every fingerprint instead of trusting an opaque label. Detection is from what the
  site publicly serves only — **no exploit probing**.
- **Fail loud.** SSRF-refused targets, all-failed fetches, and unparseable inputs are surfaced and never
  billed; a batch with no completed scan fails loud.
- **Exact billing.** You are charged **only for a completed fingerprint scan on permitted pages**
  (`FINGERPRINTED`) — including a permitted fetch that legitimately matches no signature (still a completed
  scan). Blocked and faulted origins are never billed.
- **SSRF-guarded.** Only public hosts are fetched; private / loopback / link-local / metadata addresses are
  refused.

### What it returns

Per domain: `technologies` (each `{technology, category, evidence, source}`), `technology_names`,
`technology_count`, `pages_fetched`, `pages_blocked_by_robots`, `robots_status`, and a `coverage_summary`.

### Scope & PII

This reads **technology fingerprints** a site publicly serves — not personal data. Buyer-supplied domains
only. It is **not a person-discovery tool**. Inputs are not retained beyond the run.

### Billing

Pay-per-event. `website_tech_check` is charged **once per completed fingerprint scan on robots-permitted
pages** — **$0.05**. Volume tiers apply a GOLD-floored −10 / −20 / −33% ladder. `apify-actor-start` ($0.02)
is platform-reserved, never charged in code. Robots-blocked, SSRF-blocked, faulted and unparseable inputs are
never billed.

# Actor input Schema

## `domains` (type: `array`):

Buyer-supplied website domains or URLs. Robots.txt is honored per origin before every fetch; only pages the origin permits are read. Fingerprints come from response headers and returned HTML only — no exploit probing, no third-party API. Every detection carries an evidence field. Inputs are not retained beyond the run. Batch capped at 10,000.

## `userAgent` (type: `string`):

Override the transparent crawler UA.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "domains": [
        "apify.com",
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/website-technology-detector").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 = { "domains": [
        "apify.com",
        "example.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/website-technology-detector").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 '{
  "domains": [
    "apify.com",
    "example.com"
  ]
}' |
apify call nexgenwatch/website-technology-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/website-technology-detector"
        }
    }
}

```

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/57T18E1uVglpxA7Ej/builds/FSw3UAcQhnmr1YF6N/openapi.json