# Website Technology Evidence API (`soilair/website-technology-evidence-api`) Actor

Identify technology signals in public website HTML and headers with inspectable evidence. Small original ruleset, no paid lookup keys or browser.

- **URL**: https://apify.com/soilair/website-technology-evidence-api.md
- **Developed by:** [Salih Can Kurnaz](https://apify.com/soilair) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 website observations

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 Technology Evidence API

Identify technology signals in public website HTML and headers with inspectable evidence. Small original ruleset, no paid lookup keys or browser.

### Quick start

```json
{
  "urls": [
    "https://www.python.org/"
  ]
}
```

Run the Actor; download the default dataset as JSON, CSV or Excel. Check the OUTPUT record for source failures and partial completion. Example sources can change or become unavailable.

### Behavior and limitations

Examines only server-returned UTF-8 HTML asset URLs, generator meta tags, selected element IDs and HTTP headers. Each detected signal includes its matched evidence. The original bounded rule set covers WordPress, WooCommerce, Shopify, Next.js, jQuery, Bootstrap, Google Tag Manager, Google Analytics, Webflow, Wix, Squarespace, HubSpot, Drupal, Joomla, Hugo, Gatsby, Cloudflare, Vercel and Express. Names represent observed signatures, not proof of active use or ownership. False positives and missed tools are possible. No detection of hidden infrastructure, version inference, vulnerability scanning, active ports or JavaScript execution. An accessible HTML page with no matching signals returns an empty technologies list and is a billable observation. This is not a comprehensive BuiltWith/Wappalyzer replacement or a full website audit.

Each row includes its source URL and UTC observedAt timestamp. Successful sources continue when another source fails; OUTPUT.errors describes failures. If every source fails, the run fails with diagnostic output. Budget-limited output reports PARTIAL_BUDGET and complete=false. Nothing is inferred deleted or available from a missing row.

### Pricing

$0.002 per successful website observation ($2 per 1,000), plus a $0.005 Actor-start event for the default 256 MB run. Failed sources incur no result event; the start event can still apply. Higher memory can increase the number of start events under Apify's rules. Check the effective Store pricing before running.

### Access and resource bounds

Maximum 20 input targets, queried sequentially; five redirects; 2 MiB decoded response; approximately 100 seconds fetch budget. Public HTTP(S), ports 80/443 only. DNS addresses are validated and pinned per connection; embedded credentials and private addresses are rejected. Website HTML respects robots.txt: 404/410 allow access, disallow/block/unavailable policies produce source errors. Published RDAP API endpoints follow registry policies and notices; each domain query is paced with a one-second delay. They do not require a website robots endpoint. No proxy, bypass, external API key, paid upstream service or browser is used. Respect source terms and do not use registry data for spam or high-volume harvesting. Some registries or sites block automated clients; those targets are not bypassed.

### API and automation

POST https://api.apify.com/v2/actors/soilair~website-technology-evidence-api/runs with your own Apify authorization header and the example JSON. Poll the run ID and retrieve its defaultDatasetId. Configure schedules in Apify Console if needed; this Actor does not create schedules or call other Actors.

### Data and support

Inputs and outputs remain in your Apify run storage under the platform's retention settings. Requests go only to public input targets and redirects/robots policies, plus the official IANA bootstrap and its registry endpoints for RDAP. No separate analytics or customer-data endpoint is used. Do not supply secrets. Developed with AI assistance and verified using fixtures and public-source smoke runs; arbitrary sites are not guaranteed compatible. Send a run ID and expected behavior through the issue tab without credentials.

# Actor input Schema

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

Between 1 and 20 public targets. Duplicate normalized targets are queried once.

## Actor input object example

```json
{
  "urls": [
    "https://www.python.org/"
  ]
}
```

# Actor output Schema

## `results` (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": [
        "https://www.python.org/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("soilair/website-technology-evidence-api").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": ["https://www.python.org/"] }

# Run the Actor and wait for it to finish
run = client.actor("soilair/website-technology-evidence-api").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": [
    "https://www.python.org/"
  ]
}' |
apify call soilair/website-technology-evidence-api --silent --output-dataset

```

## MCP server setup

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

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/INmHh4cGnCTVb3qhm/builds/ECYv7825p4zvXP0Wk/openapi.json