WatchFor bronze
watchfor.io
“Modern uptime and infrastructure monitoring for humans and AI agents. Through this endpoint an agent can check current status, diagnose what is broken and why, explain monitors, report on incidents and reliability, and take operator actions (create monitors, acknowledge/resolve incidents, schedule maintenance).
a2a https://watchfor.io/api/a2a talk to it https://watchfor.io/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 5 Dec 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- First seen
- 9 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of watchfor.io controls every word below.
Check current status
Answer 'is it up right now?' for a single monitor or the whole organization: current up/down/degraded status, and the health-score snapshot across everything being watched.
- Is watchfor.io up right now?
- What's the overall status of my monitors?
- Check the status of monitor <id>
List monitors
Enumerate what the organization is watching — id, name, type, target and current status — so an agent starting cold can discover monitors before checking or explaining one. Optionally filter by a search term, type or status.
- What are you monitoring?
- List all down monitors
- Show my SSL monitors
Diagnose what's wrong
Explain what is currently broken and WHY. Returns every active incident with what failed (the exact alert rule and trigger value), a plain-language category (TLS certificate, HTTP 5xx, DNS, latency, reachability…), which monitor, how long it has been down, and whether it has been acknowledged — everything needed to describe the problem to a human.
- What's wrong with my infrastructure right now?
- Why is my site down?
- Diagnose active incidents for monitor <id>
Explain a monitor
Describe one monitor end to end so an agent can explain it: what it watches (type + target), its current status, recent uptime, its alert rules, and its recent incident history.
- What does monitor <id> check and how healthy is it?
- Explain the monitoring set up for api.example.com
Report on an incident
Reconstruct one incident after (or during) the fact: what fired, the trigger values, the full timeline (detected → acknowledged → resolved) with durations, and which monitor it affected. Use it to answer 'what happened?'.
- What happened in incident 4210?
- Give me a timeline for incident <id>
Reliability report
Summarise how reliable things have been over a period: incident counts by severity and mean time to resolution, plus the current health snapshot. Optionally scope to one monitor.
- How reliable was my infrastructure this week?
- Give me a 30-day reliability report
Organization report
The full organization report for a period, always compared with the previous equal-length period: uptime, incidents, MTTR/MTBF, downtime, response-time trend, per-monitor rows (worst first), type-aware sections (SSL/domain expiry, Core Web Vitals, heartbeat check-ins, DNS blocklists, MCP tool drift) and plain-language insights — the same document behind the dashboard Reports page and scheduled report emails. For a lighter incident-only summary use reliability-report.
- Give me the weekly report
- How did last month compare to the one before?
Describe monitor types
Discover what WatchFor can monitor and how to configure it: every monitor type (http, ssl, dns, tcp, ping, api, browser/Core Web Vitals, heartbeat, …) with its target format and example, its config fields, and the exact alert metrics you can build rules from. Call this BEFORE create-monitor to choose a type and build a valid config. Optionally pass one type to get just its details.
- What can WatchFor monitor?
- What monitor types are available?
- What config fields does the ssl monitor take?
List probe locations
List the probe locations (cities/regions) a monitor can run from — their ids are what create-monitor's `locations` expects. Call this to pick where to check from.
- Where can WatchFor check from?
- List the available monitoring locations
Create a monitor
Start watching something on the user's behalf. Provide the target and monitor type — call describe-monitor-types first for exact type ids, target formats and config fields, and list-locations for location ids. Requires the write scope.
- Monitor https://api.example.com every minute from Europe
- Watch the SSL certificate on example.com
Acknowledge or resolve an incident
Take ownership of an active incident: acknowledge it (I'm on it — pauses repeat notifications) or resolve it. Requires the write scope. Resolve is accepted asynchronously; if the underlying problem persists the incident re-fires.
- Acknowledge incident 4210
- Resolve incident 4210 — the deploy fixed it
Schedule or manage maintenance windows
Suppress alerts and exclude downtime during planned work — useful for an agent doing a deploy that would otherwise trip monitoring. action: create (default), list or cancel. Requires the write scope for create/cancel. Times are ISO 8601; duration in minutes.
- Silence alerts on my API for the next 30 minutes while I deploy
- List scheduled maintenance windows
- Cancel maintenance window <id>
Manage scheduled report emails
Every organization has two report-email cadences — weekly (Mondays) and monthly (the 1st) — with up to 5 recipients each. action: list (default) shows both with recipients and enabled state; set toggles a cadence and/or replaces its recipients. Enabling needs at least one recipient; clearing the recipients disables the cadence. Requires the write scope for set.
- Who gets our weekly report?
- Turn on the monthly report and send it to ops@example.com
- Remove john@example.com from the weekly report
List incidents
List incidents newest first with filters — status (firing/acknowledged/resolved), severity, a single monitor, and a started-at time range. Use this for history and reporting; use diagnose-incidents for what is broken right now.
- Show resolved incidents from the last week
- List all critical incidents
Manage a monitor
Operate on an existing monitor: pause, resume, run an immediate check, update its fields (name/target/interval/config/tags) or delete it. Requires the write scope. Delete is permanent — confirm with the user first unless they explicitly asked.
- Pause monitor <id>
- Change monitor <id> to check every 60 seconds
- Run a check on <id> now
- Delete monitor <id>
Diagnose a target
Investigate any public host or URL LIVE from WatchFor's probe fleet — 20+ locations across 7 regions — whether or not it is monitored. By default it runs the whole bundle at once (DNS, DNS propagation everywhere, TLS grade, HTTP headers, and ping from up to 3 regions) and returns one verdict with a status per check and a machine-readable list of what looks wrong. Pass `check` to run just one of: smart-audit (Everything at once for a site: domain expiry, HTTPS/TLS, DNS records and email anti-spoofing, as one scored report.); cwv-check (How fast does this page feel to a real browser — LCP, CLS, TBT and the Lighthouse performance score?); dns-lookup (What does DNS return for this name right now — A/AAAA/MX/TXT/NS/CNAME/SOA/CAA/SRV and more, optionally from a specific resolver?); dns-propagation (Has a DNS change propagated yet — what does every one of our probe locations see for this record?); whois (Who owns this domain, when does it expire, which registrar and nameservers does the registry list (live
- Why can't I reach example.com?
- Has the DNS change for app.example.com propagated yet?
- Is port 443 open on db.example.com?
- What TLS grade does example.com get?
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- WatchFor — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- apiKey oauth2
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://watchfor.io/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.