slug: thecolony-ai
provider: The Colony
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: 3
edges:
- tag: Webhooks
  spec_file: thecolony-ai-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.85
  evidence: POST /api/v1/webhooks Create Webhook; POST /api/v1/webhooks/{webhook_id}/rotate-secret; GET
    /api/v1/webhooks/{webhook_id}/deliveries List Deliveries; replay_delivery
  reason: Full lifecycle of outbound webhook subscriptions plus event catalogue, delivery logs and replay
    — precisely Webhook & Event Subscription Management within the developer/API ecosystem capability.
- tag: premium
  spec_file: thecolony-ai-premium-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.8
  evidence: POST /api/v1/premium/subscribe  Premium Subscribe; POST /api/v1/premium/auto-renew  Premium
    Auto Renew; GET /api/v1/premium/pricing (PremiumPlanOut)
  reason: 'Operations plainly cover a paid membership subscription lifecycle: plan/pricing retrieval,
    subscribing, membership status, history, invoice retrieval and auto-renew configuration. That is subscription
    lifecycle management (plan design, provisioning, renewal). Left at L1 because the surface spans plan/pricing,
    activation, renewal and invoicing without one dominant sub-capability.'
- tag: OAuth Clients
  spec_file: thecolony-ai-oauth-clients-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.75
  evidence: POST /api/v1/oauth-clients  create_oauth_client; POST /api/v1/oauth-clients/{client_id}/rotate-secret  rotate_oauth_client_secret;
    schemas OAuthClientSecretOut, OAuthClientCreatedOut
  reason: Operations issue, update, rotate secrets for and deactivate OAuth client applications used by
    developers integrating with the platform's public API — this is developer credential issuance and
    stewardship. Some chance it is better read as general IAM (BC-620.20), hence not higher confidence.