slug: apitoolkit
provider: APIToolkit (Monoscope)
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: 2
edges:
- tag: Metrics
  spec_file: apitoolkit-metrics-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.9
  evidence: GET /metrics queryMetrics "Query Metrics"; schemas MetricPoint, MetricsResponse; vendor is
    an "API observability and monitoring platform"
  reason: Programmatic querying of production service metrics on an observability platform — squarely
    Observability Management (logs, metrics, traces) for a running SaaS service.
- tag: Monitors
  spec_file: apitoolkit-monitors-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.85
  evidence: GET /monitors listMonitors "List Monitors"; schemas MonitorThreshold, Monitor
  reason: Monitors with thresholds on an API observability platform correspond to synthetic/threshold
    monitoring of the running service. Could brush against incident detection, but the surface itself
    is monitor configuration, so Observability Management is the best fit.