Public Status Component Inventory Agent avatar

Public Status Component Inventory Agent

Pricing

from $5.00 / 1,000 useful status component inventory results

Go to Apify Store
Public Status Component Inventory Agent

Public Status Component Inventory Agent

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

Pricing

from $5.00 / 1,000 useful status component inventory results

Rating

0.0

(0)

Developer

jack su

jack su

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

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

{
"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

{
"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.