slug: epicdirectories
provider: EpicDirectories
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: API Keys
  spec_file: epicdirectories-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.8
  evidence: POST /v1/api-keys  ApiKeysController_create  Create a new API key ... DELETE /v1/api-keys/{keyId}  ApiKeysController_remove  Revoke/delete
    an API key
  reason: Full lifecycle of API credentials issued to accounts consuming this public data API — issuance
    and stewardship of developer credentials. Some residual chance this is better read as generic IAM,
    hence 0.8.
- tag: Webhooks
  spec_file: epicdirectories-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.7
  evidence: POST /v1/directories/{directoryId}/webhooks — 'Create a webhook for a directory'; 'Fire a
    test ping at the webhook URL (bypasses debounce)'
  reason: Outbound webhook subscription lifecycle (create/update/delete/test delivery) exposed by an 'API-first
    directory data platform' to integrating developers. This is the one place the frame explicitly names
    webhook subscription management rather than treating it as pure plumbing; confidence held moderate
    because webhooks are generic integration machinery.