slug: betteruptime
provider: Better Uptime
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Monitors
  spec_file: betteruptime-monitors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: POST /monitors createMonitor Create a monitor; "programmatic access to manage uptime monitors"
  reason: Uptime monitor lifecycle is synthetic monitoring of the running service — Observability Management.
- tag: Incidents
  spec_file: betteruptime-incidents-api-openapi.yml
  capability_id: BC-4220.30
  capability_id_l1: BC-4220
  capability_name: Incident Response Management
  confidence: 0.82
  evidence: GET /incidents listIncidents List incidents; vendor is an "uptime monitoring and incident
    management platform"
  reason: Incidents here are production outage incidents detected by monitoring, which is Incident Response
    Management rather than ITSM ticketing or customer complaints.
- tag: Heartbeats
  spec_file: betteruptime-heartbeats-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.78
  evidence: POST /heartbeats createHeartbeat Create a heartbeat; "heartbeat monitoring for scheduled jobs"
  reason: Heartbeat check configuration is active/synthetic monitoring of running services, i.e. Observability
    Management on a SaaS platform-operations frame.