slug: kita
provider: Kita
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: Webhooks
  spec_file: kita-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.8
  evidence: POST /api/v1/webhooks  createWebhook  Register a webhook endpoint; GET /api/v1/webhooks/{webhookId}/deliveries  Get
    delivery history; GET /api/v1/webhooks/dlq  Get the dead-letter queue
  reason: Full lifecycle of outbound webhook subscriptions exposed to external developers — registration,
    signing-secret rotation, delivery history, DLQ — which is precisely Webhook & Event Subscription Management
    in the developer-platform capability. Not merely incidental plumbing since the whole tag is the subscription
    surface itself.