website-monitor git:20260813.48597a3A

Immutable. This exact content is served forever at /api/v1/blob/e858d34df667fb41.

---
name: website-monitor
description: "Monitor any website for content changes, availability, performance, and security status. Combines page scraping, screenshot comparison, SSL monitoring, and security header checks for comprehensive website health and change detection."
---

# Website Monitor

Monitor any website for content changes, availability, performance, and security status. Combines page scraping, screenshot comparison, SSL monitoring, and security header checks for comprehensive website health and change detection. Read [the API map](references/sandbase-api-map.md) before selecting a capability.

## Call SandBase capabilities

For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`.

## Available Tools

- `firecrawl_scrape`
- `context_dev_capture_screenshot`
- `strale_ssl_check`
- `strale_header_security_check`
- `strale_website_health`
- `strale_page_speed_test`

## Workflow

1. Understand the user's research question, target, and context.
2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema.
3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments.
4. Synthesize findings into a clear, evidence-backed answer.
5. Cite sources, note evidence gaps, and separate observations from interpretations.

## Guidelines

- Always call `sandbase_describe_tool` before using any capability.
- Cite sources and preserve attribution (URLs, usernames, dates, metrics).
- Separate factual observations from analysis and recommendations.
- If data is unavailable, note the gap and continue with available evidence.
- Read-only research only. Never take actions on platforms.