# Public Status Component Inventory Agent (`jacksu/public-status-component-inventory-agent`) Actor

Extract public status-page component inventories, groups, current component states, provider hints, hashes, and useful-result pricing.

- **URL**: https://apify.com/jacksu/public-status-component-inventory-agent.md
- **Developed by:** [jack su](https://apify.com/jacksu) (community)
- **Categories:** Business, AI
- **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 component inventory 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/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

## Public Status Component Inventory Agent

Turn public vendor status pages into compact service-component inventories for
AI agents, vendor review, dependency mapping, support triage, and sales or
success workflows.

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

- status-page provider hints such as Statuspage, Better Stack, Instatus, or
  Status.io when visible
- overall status text
- component names and current component states
- component groups and status distribution
- non-operational component counts
- focus-component matches
- evidence snippets and source URLs
- stable `componentInventoryHash` and `changeStatus`
- confidence, completeness, missing fields, risk labels, diagnostics, and a
  recommended next action

### Good Fits

- Build a public vendor dependency inventory from status pages.
- Ask whether a vendor exposes API, dashboard, region, webhook, or product
  component states publicly.
- Compare current component inventory with a previous record and avoid paying
  for unchanged results.
- Feed AI agents a compact component map before running deeper incident or
  vendor-risk workflows.

### Not A Fit

- This is not an uptime monitor, SLA verifier, incident-detail scraper,
  vulnerability scanner, private trust-portal downloader, or legal compliance
  certification.
- It does not log in, use cookies, bypass paywalls, render JavaScript, submit
  forms, call private status APIs, probe uptime, or verify official severity.
- For active incident details, use a status/incident signal workflow instead.

### Input

```json
{
  "statusPageUrls": ["https://status.example.com/"],
  "focusComponents": ["API", "Webhooks"],
  "previousInventoryRecords": [],
  "maxComponents": 50,
  "requestTimeoutSecs": 20
}
```

`statusPageUrls` must be public HTTP/HTTPS status 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/",
  "pageTitle": "Example Status",
  "statusPageProvider": "atlassian-statuspage",
  "inventoryPageType": "provider-status-component-list",
  "overallStatus": "operational",
  "componentGroups": [
    {
      "name": "Product Services",
      "componentCount": 2,
      "statusDistribution": {"operational": 2},
      "componentNames": ["API", "Dashboard"]
    }
  ],
  "components": [
    {
      "name": "API",
      "status": "operational",
      "statusText": "Operational",
      "group": "Product Services",
      "evidenceSnippet": "API Operational"
    }
  ],
  "componentCount": 2,
  "statusDistribution": {"operational": 2},
  "matchedFocusComponents": ["API"],
  "componentInventoryHash": "stable-sha256",
  "changeStatus": "new",
  "billableEventName": "useful-status-component-inventory-result"
}
```

### Pricing Behavior

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

- `apify-actor-start`: small run-start event
- `useful-status-component-inventory-result`: charged only for useful public
  component inventory records

The useful event is not charged for failed fetches, private-network inputs,
query-token inputs, unsupported URLs, incident-only pages, generic pages with
too few components, focus-component misses, duplicate URLs, or unchanged
records.

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 pages that list service components. Query parameters, fragments, credentials, path params, private-network hosts, and token-like account paths are rejected.

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

Optional component, product, service, region, or API terms that must appear before the useful result event is charged.

## `previousInventoryRecords` (type: `array`):

Optional previous records from this Actor. If componentInventoryHash is unchanged for the same status page, the result is written without charging the useful event.

## `maxComponents` (type: `integer`):

Maximum component records to return per status page.

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

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

## Actor input object example

```json
{
  "statusPageUrls": [
    "https://www.atlassian.com/status"
  ],
  "focusComponents": [],
  "previousInventoryRecords": [],
  "maxComponents": 50,
  "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-component-inventory-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-component-inventory-agent").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 '{}' |
apify call jacksu/public-status-component-inventory-agent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jacksu/public-status-component-inventory-agent"
        }
    }
}

```

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/Qs1vBiMinnaDhl507/builds/7SHCVnAMOXVIk7rmO/openapi.json