slug: kard
provider: Kard
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: notifications > Subscriptions
  spec_file: kard-notifications-subscriptions-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.85
  evidence: POST /v2/issuers/{organizationId}/subscriptions  create  Create Subscription ... type_commons_NotificationType
  reason: Despite the homographic tag, these are event-notification subscriptions (keyed by NotificationType)
    for receiving webhook callbacks — webhook & event subscription lifecycle, not commercial subscription
    billing.
- tag: notifications > Notifications
  spec_file: kard-notifications-notifications-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.75
  evidence: POST /v2/issuers/{organizationId}/notifications/{eventId}/replay  replay  Replay Notification
    ... type_notifications_notifications_DeliveryStatus
  reason: Listing emitted events and replaying failed deliveries with a DeliveryStatus schema is outbound
    webhook/event delivery reliability for API consumers, not business-level customer notification.