slug: treblle
provider: Treblle
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: 1
edges:
- tag: Requests
  spec_file: treblle-requests-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.72
  evidence: 'GET /projects/{projectId}/requests  listRequests  List API Requests ... schemas: ApiRequestDetail,
    ApiRequest; ''retrieve API request logs ... providing real-time observability'''
  reason: The operations retrieve per-request API logs for a monitored service, and the document explicitly
    frames this as real-time observability. That is logs/telemetry making the running service understandable
    in production (Observability Management). Some ambiguity with API consumption analytics, hence 0.72.