slug: apiclaw
provider: APIClaw
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: 8
edges:
- tag: APIClaw Billing
  spec_file: apiclaw-apiclaw-billing-api-openapi.yml
  capability_id: BC-4250
  capability_id_l1: BC-4250
  capability_name: Subscription Billing & Revenue Management
  confidence: 0.85
  evidence: '"List Plans", "Billing Checkout", "Admin List Payments", "Admin Assign Plan", "Admin Reset
    Subscription"; schema "PaymentRecord"'
  reason: 'Clearly subscription billing for a flat-rate SaaS: plan catalogue, checkout, payment records,
    per-user plan assignment, limits and subscription reset. Spans plan design, payment collection and
    provisioning, so only the L1 is asserted.'
- tag: SCIM
  spec_file: apiclaw-scim-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.85
  evidence: POST /scim/v2/Groups  Create Group; schemas SCIMUser-Input, SCIMGroup, SCIMServiceProviderConfig
  reason: Full SCIM 2.0 Users/Groups provisioning surface — creation, patching and deletion of user and
    group identities for federated lifecycle management, which is squarely Identity & Access Management
    (joiners-movers-leavers).
- tag: Fine Tuning
  spec_file: apiclaw-fine-tuning-api-openapi.yml
  capability_id: BC-610.60
  capability_id_l1: BC-610
  capability_name: Artificial Intelligence Management
  confidence: 0.8
  evidence: POST /fine_tuning/jobs 'Create Fine-Tuning Job'; schema LiteLLMFineTuningJobCreate, Hyperparameters
  reason: Creating, listing, retrieving and cancelling model fine-tuning jobs with hyperparameters is
    ML model lifecycle/MLOps work, which maps to Artificial Intelligence Management.
- tag: SSO Settings
  spec_file: apiclaw-sso-settings-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.8
  evidence: PATCH /update/sso_settings  Update Sso Settings; schemas SSOConfig, RoleMappings, LitellmUserRoles
  reason: Management of single sign-on configuration, role mappings and default user/team access settings.
    Identity federation and access control administration, i.e. Identity & Access Management; some overlap
    with tenant-level config keeps it below 0.9.
- tag: APIClaw Blogs
  spec_file: apiclaw-apiclaw-blogs-api-openapi.yml
  capability_id: BC-400.70
  capability_id_l1: BC-400
  capability_name: Content Marketing Management
  confidence: 0.78
  evidence: '"Create Blog Post", "Update Blog Post", "List Public Blog Posts"; schemas "_BlogPostOut",
    "_PublicBlogPostListOut"'
  reason: Authoring, editing and public publication of blog posts is editorial content production and
    distribution — Content Marketing Management.
- tag: Model Management
  spec_file: apiclaw-model-management-api-openapi.yml
  capability_id: BC-610.60
  capability_id_l1: BC-610
  capability_name: Artificial Intelligence Management
  confidence: 0.75
  evidence: GET /models  model_list_models_get  Model List; GET /model/deprecations  Model Deprecations;
    GET /public/model_hub  Public Model Hub; schema ModelInfo
  reason: The operations maintain a catalogue of LLM models available through the proxy — listing, inspecting,
    model-hub publication and deprecation — which is AI/ML model lifecycle stewardship (BC-610.60). Not
    a devops/release capability since nothing is built or deployed; the object managed is the model registry
    itself. Confidence held below 0.9 because the surface is read-mostly metadata and could also be read
    as an API catalogue.
- tag: Key Management
  spec_file: apiclaw-key-management-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.7
  evidence: POST /key/generate 'Generate Key Fn'; POST /key/service-account/generate 'Generate Service
    Account Key Fn'; POST /key/regenerate
  reason: Issuance, rotation, listing and revocation of API keys/service-account credentials used by developers
    to call the platform API matches Developer Identity & Credential Management.
- tag: user agent analytics
  spec_file: apiclaw-user-agent-analytics-api-openapi.yml
  capability_id: BC-4280.30
  capability_id_l1: BC-4280
  capability_name: Product Usage Analytics
  confidence: 0.7
  evidence: GET /tag/dau  Get Daily Active Users ... GET /tag/user-agent/per-user-analytics  Get Per User
    Analytics
  reason: Operations compute DAU/WAU/MAU, per-user metrics and tag summaries for client user agents —
    i.e. analytical views of how the platform is actually used. That is Product Usage Analytics; the alternative
    reading (commercial usage metering) is possible, so confidence is moderate.