# Website Screenshot Evidence API (`nexgenwatch/website-screenshot-evidence-api`) Actor

Captures a headless-Chromium screenshot of each URL as a hashed evidence bundle — the image plus its final URL, HTTP state, capture timestamp, browser build, and SHA-256. A batch evidence API, not an interactive browser. Only a completed bundle bills.

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

## Pricing

from $33.50 / 1,000 screenshot 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/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

## Website Screenshot Evidence API

Captures a headless-Chromium screenshot of each URL as a hashed evidence bundle — the image plus its final URL, HTTP state, capture timestamp, browser build, and SHA-256. A batch evidence API, not an interactive browser.

### What you submit

`urls` — page urls. Page URLs to capture as evidence. Per URL: a screenshot image artifact (stored in the run key-value store), final URL, HTTP state, capture timestamp, headless browser build, SHA-256 of the image bytes, and render warnings. Only a completed evidence bundle bills; a URL blocked (robots/SSRF/403/429/5xx) or unreachable is delivered as an unbilled status, never a broken-site verdict.

### The runtime source gate (per submitted target)

You choose the targets, so the source contract is enforced at run time, per origin, before any page is read:

- **robots.txt** fetched once per origin and honored; no robots / 404 = permitted, a disallowed path or unavailable robots file = **BLOCKED**.
- **SSRF guard** — every host is resolved and must be public; private, loopback, link-local, reserved and cloud-metadata addresses are refused before a socket opens.
- **HTTP** — `403` / `429` / `5xx` = **BLOCKED**; DNS / timeout / connection faults = **UNREACHABLE**.

A **BLOCKED** or **UNREACHABLE** target is delivered as an unbilled status row — never a broken-site verdict, and never charged.

### Output & billing

One row per target. A complete evidenced verdict carries `outcome: answer` and is the only billable outcome; blocked / unreachable / unparseable / rejected targets carry that status and are not billed (push-then-charge — failures can only undercharge).

### Pricing

| Event | Price (USD) | When it fires |
| --- | --- | --- |
| `apify-actor-start` | $0.02 | once when the run starts (reserved; never charged in code) |
| `screenshot_check` | $0.05 | once per **complete evidenced verdict** delivered (blocked / unreachable / unparseable / rejected never bill) |

Volume tiers reduce the per-verdict price as usage grows: $0.05 → $0.045 → $0.04 → $0.0335.

### Why this and not the obvious alternative

batch evidence artifact with content hashes — a per-URL screenshot bundle you can archive/verify, NOT fleet-1's interactive Playwright browser MCP (no interactive tools, no live session).

# Actor input Schema

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

Page URLs to capture as evidence. Per URL: a screenshot image artifact (stored in the run key-value store), final URL, HTTP state, capture timestamp, headless browser build, SHA-256 of the image bytes, and render warnings. Only a completed evidence bundle bills; a URL blocked (robots/SSRF/403/429/5xx) or unreachable is delivered as an unbilled status, never a broken-site verdict.

## `viewport` (type: `string`):

desktop (1280x800), mobile (390x844), or full (1280 wide, full-page).

## `maxUrls` (type: `integer`):

Hard cap on captures (bounds compute + billing).

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

Override the transparent crawler UA.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/",
    "https://www.iana.org/",
    "http://169.254.169.254/latest/"
  ],
  "viewport": "desktop",
  "maxUrls": 10,
  "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
}
```

# 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 = {
    "urls": [
        "https://example.com/",
        "https://www.iana.org/",
        "http://169.254.169.254/latest/"
    ],
    "viewport": "desktop",
    "maxUrls": 10,
    "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/website-screenshot-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://example.com/",
        "https://www.iana.org/",
        "http://169.254.169.254/latest/",
    ],
    "viewport": "desktop",
    "maxUrls": 10,
    "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/website-screenshot-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://example.com/",
    "https://www.iana.org/",
    "http://169.254.169.254/latest/"
  ],
  "viewport": "desktop",
  "maxUrls": 10,
  "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
}' |
apify call nexgenwatch/website-screenshot-evidence-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/website-screenshot-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/oDIYXVRZ4iOf2YZTl/builds/PMJs2yfNSPsVgblfe/openapi.json