# Build a Website Technology Inventory with Evidence

**Use case:** 

Inspect two public example websites for supported CMS, ecommerce, analytics and framework signals. Replace the URLs with your existing client list. Each match includes public technical evidence for review; JavaScript is not executed.

## Input

```json
{
  "urls": [
    "https://www.wordpress.org/",
    "https://www.shopify.com/"
  ],
  "maxResults": 10
}
```

## Output

```json
{
  "url": {
    "label": "url",
    "format": "link"
  },
  "title": {
    "label": "title",
    "format": "text"
  },
  "technologyNames": {
    "label": "technologyNames",
    "format": "text"
  },
  "technologyCount": {
    "label": "technologyCount",
    "format": "text"
  },
  "comparison": {
    "label": "comparison",
    "format": "text"
  },
  "checkedAt": {
    "label": "checkedAt",
    "format": "text"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Website Tech Stack Detector with Evidence Actor is ready to run with the inputs already set for "Build a Website Technology Inventory with Evidence". [Sign up or log in](https://console.apify.com/create-task-from-example/DPySk0RmLWyw6jtOc) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Build a Website Technology Inventory with Evidence" task

The Website Tech Stack Detector with Evidence Actor will start running based on the input automatically. You can also change all the input fields, like website urls and maximum total output rows, to match your specific use case.

### 3. Receive the "Build a Website Technology Inventory with Evidence" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as url, title, technologynames, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Build a Website Technology Inventory with Evidence" task via API](https://apify.com/kirozhang/website-tech-stack-evidence.md).

## FAQ

### Does this find companies or contact details?

The technology inventory task checks URLs you supply. It does not discover companies, collect employee contacts or prove that a company pays for a detected technology.

### Does no match mean a technology is absent?

No. The inventory checks supported signatures in returned server HTML and selected headers. Client-only, consent-gated or unsupported technologies may not appear.

### How much does the default example cost?

The two-URL inventory can return up to two rows. At $0.003 per delivered check, its Actor result charges are at most $0.006. See the current Pricing tab.

## About this Actor

This example demonstrates how to use [Website Tech Stack Detector with Evidence](https://apify.com/kirozhang/website-tech-stack-evidence.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/kirozhang/website-tech-stack-evidence.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/kirozhang/website-tech-stack-evidence.md

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`).