# Public Status Page & Incident Signal Agent (`jacksu/public-status-incident-signal-agent`) Actor

Summarize public status pages into overall status, component hints, incidents, maintenance windows, impact terms, evidence URLs, and change hashes.

- **URL**: https://apify.com/jacksu/public-status-incident-signal-agent.md
- **Developed by:** [jack su](https://apify.com/jacksu) (community)
- **Categories:** Developer tools, Business, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 useful status signal 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/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

## Public Status Page & Incident Signal Agent

Turn public SaaS status pages or public incident pages into compact operational-risk signals for AI agents, vendor review, customer support triage, sales research, and monitoring workflows.

The Actor fetches public HTTP/HTTPS pages with lightweight requests and returns one source-linked record per input page:

- overall status, such as `operational`, `degraded`, `partial_outage`, `major_outage`, or `maintenance`
- component/status hints
- active and recent incident snippets
- maintenance-window hints
- impact terms such as outage, degraded performance, latency, errors, or maintenance
- matched focus components
- evidence URLs
- stable `incidentHash` and `changeStatus`
- confidence, completeness, missing fields, and diagnostics

### How To Use It

For a first-pass status signal, provide public status or incident page URLs and
leave focus components empty:

```json
{
  "statusPageUrls": ["https://status.openai.com/"],
  "focusComponents": [],
  "previousIncidentRecords": [],
  "maxIncidents": 10,
  "requestTimeoutSecs": 20
}
```

For targeted checks, add `focusComponents` such as `API`, `dashboard`,
`database`, `payments`, `login`, or a named product area. If focus components
are supplied, useful-result charging requires at least one matched component or
service term in the public status evidence.

For repeat monitoring, pass previous dataset records from this Actor in
`previousIncidentRecords`. If the incident hash is unchanged, the record is
written as `changeStatus: "unchanged"` without the useful event charge.

### Good Fits

- Check whether a public vendor status page currently shows operational issues.
- Feed AI agents a small evidence-backed status signal before contacting customers or escalating support.
- Compare a current status page result with a previous record and avoid paying for unchanged results.
- Review public incident pages during vendor diligence without running a broad crawler.

### Not A Fit

- This is not an SLA verifier, uptime monitor, vulnerability scanner, private trust-portal downloader, or legal compliance certification.
- It does not log in, use cookies, bypass paywalls, render JavaScript, submit forms, or crawl private systems.
- It does not guarantee official availability or incident severity. It organizes public page evidence.

### Example Input

```json
{
  "statusPageUrls": ["https://status.openai.com/"],
  "focusComponents": ["API"],
  "previousIncidentRecords": [],
  "maxIncidents": 10,
  "requestTimeoutSecs": 20
}
```

`statusPageUrls` must be public HTTP/HTTPS pages. URLs containing credentials, path parameters, query parameters, fragments, localhost, private-network hosts, `.local` names, or token-like account paths are rejected.

### Output

```json
{
  "status": "ok",
  "inputUrl": "https://status.example.com",
  "finalUrl": "https://status.example.com",
  "siteOriginUrl": "https://status.example.com",
  "changeStatus": "new",
  "pageTitle": "Example Status",
  "overallStatus": "degraded",
  "overallStatusText": "Dashboard Degraded Performance",
  "components": [
    {
      "name": "API",
      "status": "operational",
      "evidenceSnippet": "API Operational"
    }
  ],
  "componentCount": 1,
  "activeIncidents": [
    {
      "title": "Investigating API elevated errors",
      "status": "investigating",
      "impact": "degraded",
      "date": "2026-06-10",
      "summarySnippet": "Investigating API elevated errors - Degraded performance - Jun 10, 2026"
    }
  ],
  "recentIncidents": [],
  "incidentCount": 1,
  "maintenanceHints": [],
  "maintenanceCount": 0,
  "impactTerms": ["degraded performance", "degraded", "errors", "incident"],
  "matchedFocusComponents": ["API"],
  "incidentHash": "stable-sha256",
  "previousIncidentHash": "",
  "evidenceUrls": ["https://status.example.com"],
  "confidenceScore": 0.86,
  "completenessScore": 0.93,
  "diagnostics": []
}
```

### Pricing Behavior

The intended Apify pricing model is pay-per-event:

- `apify-actor-start`: small run-start event
- `useful-status-signal-result`: charged only for useful public status/incident signal records

The useful event is not charged for failed fetches, private-network inputs, query-token inputs, unsupported URLs, unchanged records, pages without useful public status evidence, or focus-component misses.

Do not configure `apify-default-dataset-item` for this Actor.

### Safety

- Public HTTP/HTTPS pages only.
- Same-site redirects only.
- HTML/text response size is capped at 3 MB, including gzip decompression.
- Credentials, query strings, fragments, path params, sensitive account paths, token-like path segments, localhost, private IPs, non-global IPs, and `.local` hosts are rejected or redacted.
- Error messages are generic and do not persist exception details.

# Actor input Schema

## `statusPageUrls` (type: `array`):

Public HTTP/HTTPS status page or incident page URLs. First run creates operational-risk status signal records; later runs can compare against previousIncidentRecords. Query parameters, fragments, credentials, path params, and private-network addresses are rejected.

## `focusComponents` (type: `array`):

Optional service/component names to require in the status evidence, such as API, dashboard, database, login, or payments. Leave empty for a first-pass status signal. When supplied, useful-result charging requires at least one match.

## `previousIncidentRecords` (type: `array`):

Previous dataset records from this Actor for repeat monitoring. Leave empty for a first-pass audit. If the incident hash is unchanged, the result is diagnostic and does not charge the useful event.

## `maxIncidents` (type: `integer`):

Maximum active or recent incident snippets to return per page. Lower this for compact triage; increase it for broader incident context.

## `requestTimeoutSecs` (type: `integer`):

Maximum time in seconds to wait for each public status page.

## Actor input object example

```json
{
  "statusPageUrls": [
    "https://status.openai.com/"
  ],
  "focusComponents": [],
  "previousIncidentRecords": [],
  "maxIncidents": 10,
  "requestTimeoutSecs": 20
}
```

# Actor output Schema

## `datasetId` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jacksu/public-status-incident-signal-agent").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("jacksu/public-status-incident-signal-agent").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jacksu/public-status-incident-signal-agent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=jacksu/public-status-incident-signal-agent",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/L2QV8sJMGDIusF5C5/builds/B8YvtO21xwX8nX17X/openapi.json