BetterStack Status Page Scraper

Get any company's BetterStack (Better Uptime) status page as clean resource JSON: name, monitored status and availability. One click, no required fields, no LLM.

What it does

BetterStack (Better Uptime) is a fast-growing status-page and uptime-monitoring platform used by developer-tool companies like Render and Clerk — public by design so customers can check live status without contacting support. This actor reads any company's public BetterStack status page and returns every monitored resource as clean JSON: name, resource type, current status and availability. Give it a company's BetterStack subdomain (render) and get its live status board.

Why this one:

• Official public JSON:API — no HTML parsing, no proxies
• Includes availability score and resource type, not just a status label
• Works on any company's BetterStack page, one actor
• No LLM anywhere — deterministic output, predictable costs, no hallucinated fields
• Clean by default — canonical URLs (tracking parameters stripped), parsed numbers, merged duplicates

Quick start (no code)

1. Click Try for free / Start — every field has a working default, nothing is required.
2. (Optional) change query to what you need.
3. Open the Dataset tab when the run finishes → export as JSON, CSV or Excel.

Input

Field	Required	Default	Description
query	no	render	BetterStack (Better Uptime) status-page subdomain. Find it in the status page URL: <subdomain>.betteruptime.com.
maxResults	no	20	Maximum clean results (capped at 500)
enrich	no	false	Deterministic enrichment per record — see below
monitor	no	false	Compare with the previous run, flag NEW records only

Example input:

{
  "query": "render",
  "maxResults": 50
}

Output

Real example record (from a live run):

{
  "id": "5482129",
  "title": "Render: Background Workers",
  "url": "https://render.betteruptime.com",
  "seller": "Render",
  "description": "All background workers hosted on Render.",
  "status": "not_monitored",
  "availability": 1.0,
  "resource_type": "Monitor",
  "last_status_day": "2026-08-02",
  "record_type": "resource",
  "completeness": 0.5
}

The final _summary row carries run totals (total_clean, deduped, enriched); in monitor mode a _changes row lists keys new since the last run.

Field reference

Field	Meaning
id	Resource ID (stable, deduplication key)
title	Resource's public display name
seller	Company display name
description	Resource explanation, when the company sets one
status	Current monitored status
availability	Fraction of time reported available (0–1)
resource_type	Underlying monitor type, e.g. Monitor, Heartbeat
price / price_text	Parsed numeric value + original text, when the source publishes one
completeness	0–1 filled-fields score (with enrich)

Use cases

• Vendor reliability tracking — monitor the uptime of dev tools and infra you depend on.
• Status-change alerts — schedule with monitor mode; change-alert fires when a resource's entry changes.
• Availability benchmarking — compare availability across a portfolio of vendors over time.
• Dashboards — pull multiple vendors' current status into one internal board.
• AI agents — live 'is vendor X having issues right now?' answers via MCP.

Enrichment (optional, charged only when it produces something)

Set enrich: true and every record additionally gets: e-mail addresses extracted from the description (when present), the canonical domain of the record's URL, and a completeness score (0–1, how many core fields are filled). Deterministic — the same input always yields the same output — and you are only charged for records that actually got enriched. Records where enrichment adds nothing are free.

Monitor mode — change alerts on a schedule

Set monitor: true and the actor compares the current run with the previous one (per-actor named storage) and flags only NEW records. Combine with Apify Schedules for a daily/hourly watch: the _changes summary row lists what appeared since the last run, and the change-alert event is charged per new record only — an unchanged run costs you almost nothing.

Use it from your code

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("EnezLi/betterstack-scraper").call(run_input={  "query": "render",  "maxResults": 50 })
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_API_TOKEN>' });
const { defaultDatasetId } = await client.actor('EnezLi/betterstack-scraper').call({  "query": "render",  "maxResults": 50 });
const { items } = await client.dataset(defaultDatasetId).listItems();
console.log(items);

curl

curl -X POST "https://api.apify.com/v2/acts/EnezLi~betterstack-scraper/run-sync-get-dataset-items?token=<YOUR_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{  "query": "render",  "maxResults": 50 }'

Use it with AI agents (MCP)

This actor is agent-ready: it appears in Apify's AGENTS / MCP servers catalog, so any MCP-capable assistant (Claude, custom agents, LangGraph tools) can discover and call it with a one-line tool call — zero required fields means an agent can run it safely with defaults. Connect your agent to the Apify MCP server and ask for live data in natural language.

Pricing — Pay-Per-Event, start is free

Event	When charged
Actor start	Free ($0) — try it with one click
result	Per clean result returned
enrichment	Only per record that actually got enriched
change-alert	Monitor mode: per NEW record since the previous run

No subscription, no minimum. Volume discounts apply automatically through Apify account tiers (up to −44% on GOLD). Typical run cost example: 20 results ≈ a few cents total — you can predict your bill from the numbers above before you run.

Is this legal?

This actor collects publicly available data only — the same information any visitor sees in a browser, via public endpoints. It does not bypass logins, collect private personal data, or store credentials. You are responsible for using the output in compliance with the source site's terms and the laws that apply to you (e.g. GDPR when the output contains personal data).

Support & feedback

Found a bug, need another field, or want a variant for a related platform? Open an issue on the Issues tab — issues are monitored and answered, and frequently-requested fields get added to the standard output. The actor is maintained as part of a scraper family built on one shared, tested core (bugs fixed once are fixed everywhere).

Changelog

• 0.1 (2026-07) — initial public release: search, dedup, optional enrichment, monitor mode, PPE pricing.

Limitations (honest ones)

Reads BetterStack's official public JSON:API; pages with no published resources return zero rows. Status-report/incident history is not included yet (current resource status only).

FAQ

How do I find a company's BetterStack subdomain?

Open the company's status page; if it's on BetterStack the URL looks like render.betteruptime.com — the first part is the subdomain to use.

Why did I get zero resources for a valid company?

Some companies configure a status page but keep resources unpublished/hidden — the page still resolves but exposes nothing via the public feed. Nothing is charged for a zero-result run.

Does this include incident history?

This actor returns the current resource list and status. Full incident/status-report history is a planned add-on — open an issue if you need it.

Do I need an API key or account on the source platform?

No. The actor uses public endpoints — you only need your Apify account.

Does it use AI / an LLM?

No. The core is fully deterministic: same input, same output, no hallucinations, no per-token costs.

Can I run it on a schedule?

Yes — use Apify Schedules; combine with monitor mode to pay only for what's new.

What's the maximum number of results?

500 per run (memory-safe cap). Run multiple queries or schedule runs for more.

How is my bill calculated?

Only from the events in the Pricing table — start is free, and there is no subscription.