For humans and agents
Everything the dashboard does is reachable programmatically. One API key, four ways in.
CLI
Manage monitors from your terminal, and `statusas run` executes scenarios from a YAML file — monitoring as code.
statusas monitors list
statusas monitors apply --dry-run
statusas runAPI
Typed HTTP endpoints with an OpenAPI spec. The same key works everywhere, and every mutation lands in the audit log.
const { monitor } = await statusas.monitor.v1
.MonitorService.createHTTPMonitor({
name: "API health",
url: "https://api.example.com/health",
});MCP server
Let Claude, ChatGPT or Cursor run your monitoring. OAuth sign-in, permissions scoped to the key. The same tools power the dashboard's AI assistant and the Slack agent, and agents read your status page as Markdown or through llms.txt.
{
"mcpServers": {
"statusas": {
"url": "https://api.statusas.lt/mcp"
}
}
}Terraform
Describe monitors and status pages in HCL and keep them in version control beside the rest of your infrastructure.
resource "statusas_http_monitor" "api" {
name = "API Health Check"
url = "https://api.example.com/health"
periodicity = "5m"
regions = ["vno", "kun", "fra"]
status_code_assertions {
target = 200
comparator = "eq"
}
}Start monitoring in five minutes
One URL, one email address — and you will hear about the next outage from us, not from a customer.