# Sites in the Woods

> Live uptime and response time for Geeks in the Woods' public sites, checked every minute from the outside. A project of Geeks in the Woods (https://geeksinthewoods.com), made in Alaska.

Everything public on this site, for agents. Pages show live numbers; this file doesn't, so fetch the page or the feed for the current answer.

## Status pages

- [All sites](https://sitesinthewoods.com/): every public site with its status (up, down, or not checked lately), typical time to first byte over the last 24 hours, and uptime over 30 days; the same [as Markdown](https://sitesinthewoods.com/index.md) and [as JSON](https://sitesinthewoods.com/status.json).
- [achurch.ai](https://sitesinthewoods.com/status/achurch-ai) (https://achurch.ai): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/achurch-ai/feed.xml
- [alaskanews.com](https://sitesinthewoods.com/status/alaskanews-com) (https://alaskanews.com): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/alaskanews-com/feed.xml
- [animalhouse.ai](https://sitesinthewoods.com/status/animalhouse-ai) (https://animalhouse.ai): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/animalhouse-ai/feed.xml
- [geeksinthewoods.com](https://sitesinthewoods.com/status/geeksinthewoods-com) (https://geeksinthewoods.com): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/geeksinthewoods-com/feed.xml
- [obviouslynot.ai](https://sitesinthewoods.com/status/obviouslynot-ai) (https://obviouslynot.ai): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/obviouslynot-ai/feed.xml
- [sat-chit-ananda.com](https://sitesinthewoods.com/status/sat-chit-ananda-com) (https://sat-chit-ananda.com): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/sat-chit-ananda-com/feed.xml
- [visualsitemaps.com](https://sitesinthewoods.com/status/visualsitemaps-com) (https://visualsitemaps.com): whether it's up now, time to first byte over 30 days, uptime over 24 hours, 7, 30 and 90 days (or since monitoring began), readers' page load from Chrome when there's enough data, and every outage in the last 90 days. Feed: https://sitesinthewoods.com/status/visualsitemaps-com/feed.xml

## Outage feeds

- [All public sites](https://sitesinthewoods.com/feed.xml): Atom. One entry per outage in the last 90 days, newest first. An entry's title says "<site> is down" while it lasts and "<site> was down for <time>" after; its updated time is the recovery.
- Per site: /status/<slug>/feed.xml, the same entries for one site.

## Data files

- Per site: /status/<slug>/data.json and /status/<slug>/data.csv, the status page's numbers as data, no key needed: daily uptime, response time and failures for the last 90 days, the uptime figures, and the outages (JSON only). CC BY 4.0, credit Sites in the Woods. The same numbers as the page, updated every minute.
- [Prices](https://sitesinthewoods.com/pricing.json): the pricing page's numbers: the bands per site, each named stop's monthly price, price per paid site and limits (null is unlimited), the add-ons, the journey spend cap, and the promises (first site free, 30-day refund, price per site held while subscribed). From the same code as the page and billing.

## Badges

- Per public site: /badge/<slug>.svg (also .png, and .json in the shields.io endpoint schema: schemaVersion, label, message, color, cacheSeconds). Options: show=status,uptime,response,speed; period=24h|7d|30d|90d; theme=auto|light|dark; style=flat|card. Updated every 5 minutes; the snippets' link text names the site and the report ("alaskanews.com uptime report"), and the image's own label has the current numbers. Build one at /status/<slug>/embed.

## Pages

- [About](https://sitesinthewoods.com/about): Sites in the Woods is the monitor Geeks in the Woods built to watch our own websites from the outside, for readers and AI agents alike. Made in Alaska. Updated 2026-11-19.
- [Pricing](https://sitesinthewoods.com/pricing): Pricing: uptime, failing pages, search and agent readiness, and AI agents that try real tasks. Your first site is free; then $10 down to $3 a site. Updated 2026-11-18.
- [Ready for agents](https://sitesinthewoods.com/agents): What a site needs to work for AI agents: llms.txt, an agent card, an OpenAPI description and an MCP server, what the monitor checks, and how to score your own. Updated 2026-11-19.
- [Developers and agents](https://sitesinthewoods.com/developers): Sites in the Woods for developers and AI agents: a quickstart, the JSON API and OpenAPI, the hosted MCP server, skills, limits, errors and the open-source CLI. Updated 2026-11-19.
- [What would we find on your site?](https://sitesinthewoods.com/check): A free look at a site's robots.txt for AI crawlers, its share card and structured data, and the files agents look for, with a report kept at its own address. Updated 2026-11-18.
- [How the free check scores a site](https://sitesinthewoods.com/check/method): Every check the free check scores, with its weight and standard, the grade bands and their words, the cap at D, and what changed in each version of the method. Updated 2026-11-19.
- [Why we built our own](https://sitesinthewoods.com/why): Why Geeks in the Woods built its own site monitor: the kinds of monitoring tools, what none covered for us, and open-source options, ours included. Updated 2026-11-19.
- [Colophon](https://sitesinthewoods.com/colophon): How Sites in the Woods is designed and built: honest numbers, calm colour, server-rendered HTML, one stylesheet, one script, fast pages, made for everyone. Updated 2026-11-19.
- [Terms](https://sitesinthewoods.com/terms): The terms for using Sites in the Woods, the website and AI agent monitor: what the service does, what you agree to, plans and payment, and ending your account. Updated 2026-11-19.
- [Agent skills](https://sitesinthewoods.com/skills): Agent skills: SKILL.md files that teach an agent to check a public site, connect to a team's monitoring with its key, find what's wrong and hold alerts. Updated 2026-11-19.
- [Our scanner](https://sitesinthewoods.com/scanner): How our scanner (site-monitor-scan) and monitor (site-monitor) behave: who starts them, how to recognise, slow or stop them, and what each fix means. Updated 2026-11-19.
- [Contact](https://sitesinthewoods.com/contact): How to reach Geeks in the Woods about Sites in the Woods: help with sites and alerts, billing, security reports, the open-source checks, and when we answer. Updated 2026-11-19.
- [Privacy](https://sitesinthewoods.com/privacy): What Sites in the Woods collects (your email and name, your sites, where alerts go, what we see), who processes it, how long we keep it, and how to delete it. Updated 2026-11-18.


## API

JSON: reads for every key, and writes (dismiss, check again, maintenance windows, pause) for Member and Admin keys on teams with 10 sites or more. Docs: https://sitesinthewoods.com/api/docs (markdown: https://sitesinthewoods.com/docs/api.md). OpenAPI: https://sitesinthewoods.com/openapi.json. Keys: https://sitesinthewoods.com/auth.md. Every data route needs a key from our team, sent as `Authorization: Bearer sm_…`; answers are `{ data, next_steps }`, lists add `limit`, `offset` and `has_more`, and errors are `{ error, message, suggestion, next_steps }`. Requests are limited per key per minute (more sites allow more); over it, a 429 `rate_limited` error says when to retry in `Retry-After`. The data changes once a minute, so poll at most once a minute.

- `GET /api/status`: Every one of the team's sites: its status right now, and the open incidents. Call this first, or on a schedule (at most once a minute, as often as the checks run), to see whether anything is down or warning right now.
- `GET /api/sites`: The team's sites: status, homepage uptime over 1, 7 and 30 days, open incidents. Call this to compare sites or report on uptime over the last day, week or month. It also lists the slugs every other route takes.
- `GET /api/sites/:slug`: One site: its last 7 days (as in the weekly brief), open incidents, domain and TLS expiry. Call this to answer questions about one site: how it did this week, what's wrong with it now, and when its domain or certificate runs out.
  - `slug` (path): site slug, as in /api/sites
- `GET /api/sites/:slug/insights`: One site's daily insights: page weight, security headers, prefetches, page errors, broken links, cache, dead ends. Call this when a site is slow or heavy, or to find what to fix: the daily browser load's page weight, missing security headers, JavaScript errors and broken links.
  - `slug` (path): site slug, as in /api/sites
- `GET /api/sites/:slug/scans`: One site's API recovery scans, newest first: state, how each ended, and findings by weight. Call this to see whether a site has been scanned for dead ends (API errors that don't say how to recover, lists without paging, pages nothing links to) and how the last scan came out. Scans are started from the dashboard by an admin or owner.
  - `slug` (path): site slug, as in /api/sites
  - `limit` (query): page size, clamped to 1–100
  - `offset` (query): rows to skip, at most 1000
- `GET /api/sites/:slug/scans/:id`: One API recovery scan: what it saw, its findings, the fixes and what changed since the last scan. Call this for a scan's results: findings by weight with the places on the site, three to five fixes in words and as a block for a coding agent, and new, fixed and still-open findings since the previous scan. It never includes text from the scanned site.
  - `slug` (path): site slug, as in /api/sites
  - `id` (path): scan id, as in /api/sites/{slug}/scans
- `GET /api/sites/:slug/maintenance`: One site's maintenance windows: on now, scheduled, and the last 30 days. Call this to see whether a site is in a maintenance window (its alerts held, its uptime not counting that time) and when the next one is. Windows are started from the dashboard or a deploy calling the site's maintenance URL (POST <url>/start?minutes=30, POST <url>/end), which the dashboard shows to admins.
  - `slug` (path): site slug, as in /api/sites
- `GET /api/sites/:slug/map`: One site's structure from its sitemaps: sections, new and removed pages, what fails. Call this to see where a site is changing or breaking without crawling it: every path with pages under it, with new and removed pages in the window, pages that fail, broken links and sitemaps that miss pages. Add ?section= for one section's pages. Our sites only (competitors' sitemaps aren't read).
  - `slug` (path): site slug, as in /api/sites
  - `range` (query): the window for new and removed pages
  - `section` (query): a section path such as "/c" to list its pages
- `GET /api/sites/:slug/events`: What changed on one site: incidents opened and resolved, code pushes, maintenance, new pages. Call this to find what changed before a number moved (clicks fell, pages got slower): the site's timeline, newest first, the same events the dashboard draws on its charts. Page through with limit and offset.
  - `slug` (path): site slug, as in /api/sites
  - `range` (query): the window
  - `limit` (query): page size, clamped to 1–200
  - `offset` (query): rows to skip, at most 1000
- `GET /api/incidents`: Incidents, open now or recent; open outages and slowdowns carry the likely cause. Call this to see what went wrong and why: open and recent incidents, newest first, with the likely cause on open outages and slowdowns. Page through with limit and offset.
  - `state` (query): open: open now; recent: newest first, open or closed
  - `site` (query): site slug
  - `limit` (query): page size, clamped to 1–100
  - `offset` (query): rows to skip, at most 1000
- `GET /api/domains`: The team's domains: registration expiry, registrar, nameservers, status. Call this to check renewals: which domains expire soon, who the registrar is, and whether nameservers or registry locks changed.
- `POST /api/incidents/:id/dismiss`: Dismiss an open incident as noise. Hides it from the open lists for the whole team; it never alerts again and closes without a message. Not every kind can be dismissed (409).
  - `id` (path): incident id, as in /api/incidents
- `POST /api/incidents/:id/undismiss`: Bring back a dismissed incident. Undoes a dismiss: the incident shows and alerts again.
  - `id` (path): incident id, as in /api/incidents
- `POST /api/incidents/:id/recheck`: Check an incident again now. The monitor checks it again within 30 seconds, after a fix, instead of waiting for the next scheduled check. Not every kind can be checked again (409).
  - `id` (path): incident id, as in /api/incidents
- `POST /api/sites/:slug/maintenance/start`: Start a maintenance window on a site now. Call this before a deploy: alerts for the site are held (checks still run) until the window ends, after `minutes` (default 30, at most 24 hours) or when you end it. Starting again replaces the open window.
  - `slug` (path): site slug, as in /api/sites
- `POST /api/sites/:slug/maintenance/end`: End a site's maintenance windows now. Call this after a deploy: alerts for the site go out again from now. Ending with no window on answers `ended: 0`.
  - `slug` (path): site slug, as in /api/sites
- `POST /api/sites/:slug/pause`: Pause a site's checks. Stops every check of the site, keeping its history, until it's resumed. Nothing alerts while it's paused.
  - `slug` (path): site slug, as in /api/sites
- `POST /api/sites/:slug/resume`: Resume a paused site's checks. Starts the site's checks again within a minute.
  - `slug` (path): site slug, as in /api/sites
## MCP

https://sitesinthewoods.com/mcp is a hosted MCP server (Streamable HTTP; protocol 2026-07-28 and the 2025 revisions) with one tool per API route, named by the route's operation id, returning the route's own JSON: reads for every key, and the writes (dismiss, check again, maintenance windows, pause) for Member and Admin keys on teams with 10 sites or more. Send the same key as the API: `Authorization: Bearer sm_…`, kept in the `SITES_IN_THE_WOODS_API_KEY` environment variable rather than typed into a command. Listing the tools needs no key; without one, a call returns an error result saying how to get one. Its card: https://sitesinthewoods.com/mcp/server-card. Docs: https://sitesinthewoods.com/api/docs#mcp.

Claude Code:

```
claude mcp add --transport http sites-in-the-woods https://sitesinthewoods.com/mcp --header "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY"
```

Cursor (~/.cursor/mcp.json):

```
{
  "mcpServers": {
    "sites-in-the-woods": {
      "url": "https://sitesinthewoods.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SITES_IN_THE_WOODS_API_KEY}"
      }
    }
  }
}
```

VS Code (.vscode/mcp.json):

```
{
  "inputs": [
    {
      "type": "promptString",
      "id": "sites-in-the-woods-key",
      "description": "Sites in the Woods API key",
      "password": true
    }
  ],
  "servers": {
    "sites-in-the-woods": {
      "type": "http",
      "url": "https://sitesinthewoods.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:sites-in-the-woods-key}"
      }
    }
  }
}
```

Tools:

- `status`: wraps `GET /api/status`. Every one of the team's sites: its status right now, and the open incidents.
- `sites`: wraps `GET /api/sites`. The team's sites: status, homepage uptime over 1, 7 and 30 days, open incidents.
- `sites_by_slug`: wraps `GET /api/sites/{slug}`. One site: its last 7 days (as in the weekly brief), open incidents, domain and TLS expiry.
- `sites_by_slug_insights`: wraps `GET /api/sites/{slug}/insights`. One site's daily insights: page weight, security headers, prefetches, page errors, broken links, cache, dead ends.
- `sites_by_slug_scans`: wraps `GET /api/sites/{slug}/scans`. One site's API recovery scans, newest first: state, how each ended, and findings by weight.
- `sites_by_slug_scans_by_id`: wraps `GET /api/sites/{slug}/scans/{id}`. One API recovery scan: what it saw, its findings, the fixes and what changed since the last scan.
- `sites_by_slug_maintenance`: wraps `GET /api/sites/{slug}/maintenance`. One site's maintenance windows: on now, scheduled, and the last 30 days.
- `sites_by_slug_map`: wraps `GET /api/sites/{slug}/map`. One site's structure from its sitemaps: sections, new and removed pages, what fails.
- `sites_by_slug_events`: wraps `GET /api/sites/{slug}/events`. What changed on one site: incidents opened and resolved, code pushes, maintenance, new pages.
- `incidents`: wraps `GET /api/incidents`. Incidents, open now or recent; open outages and slowdowns carry the likely cause.
- `domains`: wraps `GET /api/domains`. The team's domains: registration expiry, registrar, nameservers, status.
- `incidents_by_id_dismiss`: wraps `POST /api/incidents/{id}/dismiss`. Dismiss an open incident as noise.
- `incidents_by_id_undismiss`: wraps `POST /api/incidents/{id}/undismiss`. Bring back a dismissed incident.
- `incidents_by_id_recheck`: wraps `POST /api/incidents/{id}/recheck`. Check an incident again now.
- `sites_by_slug_maintenance_start`: wraps `POST /api/sites/{slug}/maintenance/start`. Start a maintenance window on a site now.
- `sites_by_slug_maintenance_end`: wraps `POST /api/sites/{slug}/maintenance/end`. End a site's maintenance windows now.
- `sites_by_slug_pause`: wraps `POST /api/sites/{slug}/pause`. Pause a site's checks.
- `sites_by_slug_resume`: wraps `POST /api/sites/{slug}/resume`. Resume a paused site's checks.

## Skills

A `SKILL.md` for each job, indexed with digests at https://sitesinthewoods.com/.well-known/agent-skills/index.json (installing them: https://sitesinthewoods.com/skills):

- [sites-in-the-woods-status](https://sitesinthewoods.com/.well-known/agent-skills/sites-in-the-woods-status/SKILL.md): Check whether a website that Sites in the Woods monitors in public is up, and see its recent outages, uptime and response times, from its public status page, data file and outage feed. Use when someone asks if one of these public sites is down, had an outage, or how reliable or fast it has been. Read-only, with no account or key. Not for a team's own private sites (use sites-in-the-woods-health with the team's key), and not for whether some other site or service is down (google.com, AWS, a site of your own): only sites on Sites in the Woods' public list.
- [sites-in-the-woods-connect](https://sitesinthewoods.com/.well-known/agent-skills/sites-in-the-woods-connect/SKILL.md): Set up an agent's access to a team's Sites in the Woods website monitoring: get an API key from the team's admin, keep it in an environment variable, add the hosted MCP server to Claude Code, Cursor or VS Code, and check the connection. Use when working with a team's Sites in the Woods monitoring for the first time, or when another Sites in the Woods skill can't reach its tools or gets a 401. Not for public status pages, which need no key (use sites-in-the-woods-status), and not for setting up other monitoring or alerting services (Pingdom, UptimeRobot, Datadog) or other MCP servers.
- [sites-in-the-woods-health](https://sitesinthewoods.com/.well-known/agent-skills/sites-in-the-woods-health/SKILL.md): Find out what's wrong with a team's websites and why, using the team's Sites in the Woods API key or MCP server: what's down now, open incidents with their likely causes, uptime, and domains or TLS certificates about to expire; and, with a Member or Admin key, ask for a check again or dismiss an incident as noise. Use when a team that monitors its sites with Sites in the Woods asks whether their sites are OK, what broke and why, or when a domain or certificate it watches expires. Not for a domain or certificate question without a Sites in the Woods account (a registrar, a one-off SSL check), maintenance windows or pausing a site (use sites-in-the-woods-maintenance), or public sites without a key (use sites-in-the-woods-status).
- [sites-in-the-woods-maintenance](https://sitesinthewoods.com/.well-known/agent-skills/sites-in-the-woods-maintenance/SKILL.md): Hold a team's Sites in the Woods alerts during a deploy or planned work with a maintenance window, end it, or pause and resume a site's checks, using the team's API key or MCP server. Use when someone says they're deploying or doing maintenance and wants alerts held, wants alerts back on, or wants a site's monitoring paused or resumed. Not for reading what's wrong (use sites-in-the-woods-health).
