Sites in the Woods

Everything an agent needs, in one place.

Everything here works for a person at a terminal and for an AI agent acting for one. The docs and the files are public; a team's data needs a key from that team.

Quickstart

  1. Sign in (an emailed code, no password) and add a site; an admin creates a key on the team's API keys page. It's shown once.
  2. Keep it in the environment, never in a command or a chat: export SITES_IN_THE_WOODS_API_KEY=sm_…
  3. Ask for your sites' status:
curl -H "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY" https://sitesinthewoods.com/api/status

Every answer is {"data": …} with next_steps, the calls that usually come next.

The API

Reference
Every route, parameter and field, also as Markdown; the OpenAPI 3.1 description to download; the API catalog (RFC 9727).
Keys and roles
How keys work: viewer keys read; dismiss, check again, maintenance windows, pause need a member or admin key, on teams with 10 sites or more. Each operation in the OpenAPI names the lowest role it needs.
Errors
RFC 9457 problem details (application/problem+json), each with a code to branch on, what went wrong, what to do, and next_steps. Every code.
Limits
Requests a minute per key, by the team's sites: 60 on the free site, 300 from 2 sites, 1,000 from 25. Writes: 10 in 10 seconds. Every keyed answer carries RateLimit-Policy and RateLimit (IETF draft 11) with what's left; a 429 says when to retry.
Retries
Writes are idempotent: repeating one changes nothing more, so retrying after a timeout is safe.

Versioning

The API is unversioned and changes only by adding routes and fields; one that has to go is announced at least 90 days ahead, on its responses, with Deprecation (RFC 9745) and Sunset (RFC 8594) headers and a Link to /developers#versioning (rel="deprecation").

The MCP server

https://sitesinthewoods.com/mcp: one tool for each API route, with the same key. Its docs, server card and the AI catalog say what it offers. Add to Cursor (the key still comes from your environment).

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}"
      }
    }
  }
}

Agent skills

Indexed, with digests, at /.well-known/agent-skills/index.json; installing them. They're also in our public repository: npx skills add geeks-accelerator/sites-in-the-woods. That repository is an Agent Plugin and a Claude Code plugin marketplace too (/plugin marketplace add geeks-accelerator/sites-in-the-woods), with an AGENTS.md for coding agents.

Files for agents

Open source

agent-ready-uptime is the checks this service runs, with a small self-hosted runner: npx agent-ready-uptime init https://your.site, then npx agent-ready-uptime watch. MIT, on npm. Our agent and search readiness audit scores a site once: npx readiness-audit your.site.

For your coding agent

Paste this:

Read https://sitesinthewoods.com/llms.txt and https://sitesinthewoods.com/developers.md to learn Sites in the Woods' API and MCP server. My key is in the SITES_IN_THE_WOODS_API_KEY environment variable; never print it. Tell me which of my sites are down right now and which had outages in the last 7 days.

Without a key, an agent can still read every public status page: https://sitesinthewoods.com/llms.txt lists them.

Last updated .