slug: apicontext provider: APIContext 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: 15 edges: - tag: Browser Monitors spec_file: apicontext-browser-monitors-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.85 evidence: GET /api/3/monitors/browser/ 'List all Browser Monitors for a project'; POST 'Create a new Browser Monitor'; schema BrowserTestSetupRepr reason: Lifecycle management of synthetic browser monitors that run scheduled checks against live services; the observability sub-capability names 'synthetic monitoring' directly. - tag: Project SLOs spec_file: apicontext-project-slos-api-openapi.yml capability_id: BC-4220.10 capability_id_l1: BC-4220 capability_name: Service Reliability Engineering confidence: 0.85 evidence: '''Get-Project-Slo'' / ''Update-Project-Slo''; schemas ServiceLevelObjectiveBody, THRESHOLDS, METRICS, SloPeriod' reason: Definition and maintenance of service-level objectives with metrics, thresholds and measurement periods — squarely service reliability engineering (SLI/SLO stewardship). - tag: Browser Monitor Statistics spec_file: apicontext-browser-monitor-statistics-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.82 evidence: POST /api/3/monitors/browser/{monitor_id}/stats/performance 'Aggregate performance metrics for a monitor over a window'; schemas PerformanceMeta, MetricAggregate, SessionRow reason: Aggregated performance/resource/session metrics from synthetic browser monitors is squarely synthetic monitoring and metrics analysis, which the observability sub-capability explicitly covers. Some chance it belongs under capacity & performance management, hence not 0.95. - tag: Organization Roles spec_file: apicontext-organization-roles-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /api/2/organizations/{org_id}/roles/ 'Create-Org-Role'; schemas OrgRoleResponse, ProjectRoleListResponse reason: Creation, listing and deletion of organisation roles governing access — role-based access control, i.e. identity and access management. - tag: Project Access spec_file: apicontext-project-access-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /api/2/projects/{project_key_str}/access/ 'Create-Project-Access'; schema CreateProjectAccessBody reason: Grant, update and revoke of access rights to projects — access management over platform resources. - tag: Project Roles spec_file: apicontext-project-roles-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: '''Create-Project-Role'', ''Delete-Project-Role'', schema ProjectRoleResponse' reason: Role definition and lifecycle controlling who can do what in a project — role-based access control. - tag: API Monitor Statistics spec_file: apicontext-api-monitor-statistics-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.78 evidence: POST /api/3/monitors/api/{monitor_id}/stats/performance Aggregate performance metrics for an API monitor over a window reason: Aggregated latency/performance metrics and DNS diagnostics from scheduled external monitors — exactly the synthetic monitoring and metrics strand of Observability Management. Capacity/performance management is a weaker alternative reading. - tag: MCP Monitors spec_file: apicontext-mcp-monitors-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.78 evidence: '''Create a new MCP Monitor'', ''List all MCP Monitors for a project'', schemas McpCallToolStepRepr / McpTestSetupRepr' reason: CRUD over scheduled synthetic monitors that call endpoints and validate responses — this is synthetic monitoring/observability configuration, consistent with the vendor's stated synthetic monitoring platform. - tag: MCP Monitor Statistics spec_file: apicontext-mcp-monitor-statistics-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: POST /api/3/monitors/mcp/{monitor_id}/stats/performance — 'Aggregate performance metrics for an MCP monitor over a window' reason: Operations aggregate latency/availability metrics produced by synthetic monitors, which is observability (metrics and synthetic monitoring) of a running service rather than any business-domain function. - tag: Monitors spec_file: apicontext-monitors-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.75 evidence: '''List all Monitors for a project'', ''Trigger a Monitor to run now''' reason: Listing and on-demand execution of synthetic monitors against external APIs — observability/synthetic monitoring of running services. - tag: Project Synopsis spec_file: apicontext-project-synopsis-api-openapi.yml capability_id: BC-4220.10 capability_id_l1: BC-4220 capability_name: Service Reliability Engineering confidence: 0.75 evidence: 'schemas: ProjectSloResponse, ServiceLevelObjectiveResponse, ThresholdResponse, OrgSynopsisResultCounts' reason: The synopsis surface rolls up service-level objectives and thresholds for monitored APIs, which is the definition and stewardship of SLIs/SLOs under SaaS Platform Operations. - tag: Calls spec_file: apicontext-calls-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: POST /api/2/calls/{call_id}/run run-call-v2; POST /api/2/calls/build/curl build-call-from-curl; schemas CallRunPayload, ConditionsResponse reason: '''Calls'' are the configurable synthetic API requests the platform executes on a schedule against monitored APIs, so this is the core synthetic monitoring surface. Could alternatively be read as test-case management under software quality engineering, so confidence is moderate.' - tag: Insights spec_file: apicontext-insights-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: GET /api/2/insights/{filename}/outliers get-insights-outliers; GET /api/2/insights/rank/history list-insights-rank-history reason: Reports, rankings and latency-outlier analysis derived from the vendor's scheduled external API calls — i.e. analytical output of synthetic monitoring, which the frame places under Observability Management ('metrics, traces, and synthetic monitoring'). Some chance the intended fit is performance management instead. - tag: Results spec_file: apicontext-results-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: GET /api/3/results/{result_id}/screenshot; GET /api/2/results/{result_key_str}/pcap get-result-pcap reason: Retrieval of synthetic call results, screenshots, packet captures and timing synopses is the observability/synthetic-monitoring data surface of the platform. - tag: Stats spec_file: apicontext-stats-api-openapi.yml capability_id: BC-4220.20 capability_id_l1: BC-4220 capability_name: Observability Management confidence: 0.7 evidence: GET /api/2/calls/{call_id}/stats/http_codes get-call-http-codes; .../stats/metrics/{location_id}/ get-call-metrics reason: Pass/fail counts, HTTP code breakdowns and latency quantiles per monitored call and location are production monitoring metrics — observability management.