---
title: X
description: An assistant reading WatchFor through the API or MCP saw less than a person on the dashboard. Now any check run opens in full, redacted like the probe-result…
canonical: https://watchfor.io/changelog/2026-09-22-api-parity-with-dashboard
---

[All updates](/changelog/page/2#2026-09-22-api-parity-with-dashboard) ⚡ Improved Sep 22, 2026 · v 8.2.2

# The API and MCP now tell agents what the dashboard tells you

An assistant reading WatchFor through the API or MCP saw less than a person on the dashboard. Now any check run opens in full, redacted like the probe-result view; a monitor says whether alerts are muted or routed, its last and next check and open incident; the summary counts hosts, fleet health and silent monitors; maintenance windows say if they are active and when they run next; status pages report overall and per-component status; on-call says who is on now and next; notification channels are readable with secrets redacted. Six new MCP tools and a who-is-on-call A2A skill.

## The problem

An assistant connected through the API or MCP saw a monitor's name, type and status, and not much more. Ask it "why did nobody get paged last night?" and it couldn't see that the monitor's alerts were muted, or that no alert rule was routed to anyone.

## What agents can read now

- One check in full. GET /v1/monitors/{id}/checks/{run_id} and the get_check_details tool return what the check saw: headers, timings, TLS, DNS answers and assertions. Secrets are redacted the same way as in the dashboard's check view.

- Monitor state. Whether alerts are muted and until when, whether any rule reaches a person, the last check with its result and location, an estimate of the next one, and the open incident.

- The summary. Hosts online, stale and offline, the same health score as the dashboard, and how many monitors would alert nobody.

- Maintenance windows say whether they're active now and when they run next.

- Status pages give the overall status and each component's status.

- On-call says who is on call now, until when, and who is next.

- Notification channels can be read, with their secrets redacted.

## Example

You ask your assistant "is anything quietly broken?" It calls get_summary , sees silent_monitors: 2 , finds the two monitors with no route, and tells you to add a contact group to them. Before, the honest answer it could give was "all monitors are up".

There are six new MCP tools and a who-is-on-call skill for A2A agents. See the [API overview](/docs/api), the [MCP server](/docs/api/mcp) and [A2A](/docs/api/a2a).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-22-api-parity-with-dashboard · Site guide: https://watchfor.io/llms.txt