Skip to content
perstatDocs

Documentation

What the product does today, in its own register: concrete numbers, real limits, and gaps named out loud.
Start hereAPI reference

These docs cover the product as it is, not as it is planned. Where a capability does not exist yet, the page says so and the changelog carries it when it lands. REST and MCP are separate interfaces: scoped API keys read seven REST endpoints; permitted writes run through MCP and are checked against scope and current role. The public OpenAPI contract is curated and machine-readable, not the complete internal API. For MCP, the connected server’s tools/list is authoritative for the available catalogue.

How monitoring worksFrom a single check to a confirmed state: intervals, regions, and why one failing probe is not an outage.
Quorum and regionsSix regions, one per inhabited continent, and the threshold that decides when a wobble becomes an alarm.
Host agentsWatch what a probe cannot reach: disks, services, certificates, and the machine's own view of itself.
API and MCPDrive Perstat from your own tooling, or let an agent read and change monitors through MCP.