A monitor keeps one real browser on your site around the clock. It either explores the site all the time or runs a journey, such as home, product, add to cart, at a fixed interval. It records how long pages take and tells you when something breaks or gets slow. The examples use the made-up site example.com, and the values in them are invented to show the shape of an answer.

A monitor uses one browser, so the domain does not need to be verified.

create_monitor

Starts a monitor. An agent offers one after a tuning session, or when you ask to be told if the checkout stops working.

  • Inputs: give url to explore the site continuously, or journey_id to run a journey every every_minutes, which is 5, 15, 30 or 60 (15 if left out). alert_emails lists up to 10 addresses that get alerts. webhook_url also posts alerts to an https webhook that takes Slack-style messages. thresholds set what counts as slow: page_load_seconds (3 if left out), step_ms for any journey step (5000 if left out) and steps for single steps by name. note says what the monitor is for.
  • Returns: the monitor: its monitor_id, state, what it runs, credits_per_day, the alert addresses and thresholds, a live_url on speed.supervisor.com, what was charged and the balance after it.
  • Alerts: you are alerted when a journey fails two rounds in a row, when the 95th percentile of the last hour’s page loads or journey steps is over a threshold, and when the monitor recovers.
  • Cost and effect: a monitor is paid with credits per day, and the first day is charged when it is created. An exploring monitor has a flat daily price, and a journey monitor is priced by its rounds a day. The answer gives the price as credits_per_day. A monitor that cannot pay for its next day stops. An organization can have at most 20 monitors. It sends real traffic, so the agent should ask you first. A journey should pass dry_run_journey before it is monitored.

Example

“Watch the checkout journey every 15 minutes and email me if it breaks.”

{
  "monitor_id": "33333333-4444-4555-8666-777777777777",
  "url": "https://example.com/",
  "domain": "example.com",
  "state": "running",
  "runs": { "journey_id": "44444444-5555-4666-8777-888888888888", "name": "add to cart", "version": 2, "every_minutes": 15 },
  "credits_per_day": 3,
  "alert_emails": ["owner@example.com"],
  "thresholds": { "page_load_seconds": 3.0, "step_ms": 5000 },
  "credits_charged": 3,
  "next": "The first round runs within a few minutes, then every 15 minutes. get_monitor shows each step."
}

list_monitors

Lists your organization’s monitors, including the ones made in the web app on speed.supervisor.com. An agent calls it to see at a glance whether anything is wrong, or to find a monitor’s id.

  • Inputs: url, to list only one site’s monitors. It can be left out.
  • Returns: monitors, each with what it runs, its state (running, paused or stopped), its daily price, the last round of a journey (passed, or failed and at which step), the last hour (page loads, average and 95th percentile load time, errors) and problems: what is failing or slow right now, since when.
  • Cost and effect: free. It only reads.

Example

“Is anything wrong on my sites right now?”

{
  "monitors": [
    {
      "monitor_id": "33333333-4444-4555-8666-777777777777",
      "domain": "example.com",
      "state": "running",
      "last_round": { "at": "2026-11-16T10:30:00Z", "ok": false, "failed_step": "Add to cart" },
      "last_hour": { "page_loads": 16, "avg_load_time": 1.1, "p95_load_time": 2.4, "errors": 2 },
      "problems": [{ "kind": "failing", "step": "Add to cart", "since": "2026-11-16T10:15:00Z" }]
    }
  ]
}

get_monitor

Reads one monitor’s results over the last hours or days. An agent uses it to find when a problem began, which journey step is slow, and whether the trend is getting worse.

  • Inputs: monitor_id is required. hours is how far back to look, from 1 to 168 (24 if left out). days, from 1 to 365, adds the day-by-day history. Set charts to false to leave the images out.
  • Returns: page loads in the window (count, and the average, median and 95th percentile of total, server and browser time), the same by the hour, current problems and the alerts sent. A journey monitor adds its last rounds, each step’s runs, failures and timings, and the latest failure with a screenshot link. With days, history gives each day a rating (good, ok, slow or down), its load times, errors, a score and a link to that day on the web.
  • Images: charts by the hour and, with days, by the day.
  • Cost and effect: free. It only reads.

Example

“When did the cart start failing, and how slow has the site been this week?”

{
  "monitor_id": "33333333-4444-4555-8666-777777777777",
  "state": "running",
  "window_hours": 24,
  "page_loads": { "count": 384, "total": { "avg": 1.1, "p50": 0.9, "p95": 2.4 } },
  "steps": [{ "name": "Add to cart", "count": 96, "failed": 3, "avg_ms": 820, "p95_ms": 1900 }],
  "last_failure": { "step": "Add to cart", "url": "https://example.com/cart", "at": "2026-11-16T10:30:00Z" },
  "history": { "daily": [{ "date": "2026-11-15", "rating": "good", "avg_load_time": 1.0 }] }
}

update_monitor

Changes a monitor that was created by an agent. An agent uses it to change who is alerted, to make the thresholds stricter or looser, to pause the monitor, or to send a test alert so you see what an alert looks like.

  • Inputs: monitor_id is required. Then any of: every_minutes (journey monitors), alert_emails (replaces the whole list), thresholds (replaces them), webhook_url (an empty value removes it), paused and test_alert.
  • Returns: the monitor after the change, and changed, the list of what changed.
  • Cost and effect: free. A paused monitor uses no browser and costs nothing while it is paused. A monitor made in the web app is changed there, not here.

Example

“Send a test alert so I can see how it arrives.”

{
  "monitor_id": "33333333-4444-4555-8666-777777777777",
  "state": "running",
  "alert_emails": ["owner@example.com"],
  "changed": ["test_alert"]
}

delete_monitor

Stops a monitor that was created by an agent. An agent uses it when you no longer need the monitor.

  • Inputs: monitor_id.
  • Returns: the id of the stopped monitor.
  • Cost and effect: the browser stops and no further days are charged. The results stay readable with get_monitor for 7 days. A monitor made in the web app is stopped there.

Example

“Stop watching the old campaign page.”

{
  "deleted": "33333333-4444-4555-8666-777777777777",
  "note": "Its results stay readable with get_monitor for 7 days (hourly totals longer)."
}