slug: activefence
provider: ActiveFence
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: activefence-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.7
  evidence: POST /v3/apikeys 'Generate New API Key'; GET /v3/apikeys 'List API Keys'; DELETE /v3/apikeys/{id}
    'Delete API Key'
  reason: Operations issue, enumerate and revoke API keys that integrating developers use to call api.alice.io.
    That is issuance and stewardship of developer credentials for a public API, i.e. Developer Identity
    & Credential Management. It is arguably generic plumbing, hence moderate confidence rather than high.
- tag: WonderBuild
  spec_file: activefence-wonderbuild-api-openapi.yml
  capability_id: BC-620
  capability_id_l1: BC-620
  capability_name: Cybersecurity Management
  confidence: 0.7
  evidence: '**WonderBuild**: Red teaming and security assessment tools for AI applications; POST /redteam/assessments/run/{id}
    ''run assessment'''
  reason: Operations list, run and clone red-team assessments against AI applications — adversarial security
    testing of a system under test. That sits under Cybersecurity Management; the evidence does not clearly
    distinguish Vulnerability Management from Threat Detection & Response, so no L2 is asserted.