slug: polar-sh
provider: Polar
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: 5
edges:
- tag: Subscriptions
  spec_file: polar-sh-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.82
  evidence: PATCH /subscriptions/{id}  subscriptions:update  Update Subscription; DELETE /subscriptions/{id}  subscriptions:revoke  Revoke
    Subscription
  reason: Operations span in-life modification and revocation of subscriptions, clearly Subscription Lifecycle
    Management; no single L2 fits since both modification and cancellation are covered.
- tag: Webhooks
  spec_file: polar-sh-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.82
  evidence: POST /webhooks/endpoints  webhooks:createEndpoint  Create Webhook Endpoint
  reason: Lifecycle management of outbound webhook endpoint subscriptions exposed to integrating developers
    maps directly to Webhook & Event Subscription Management in the developer-platform capability.
- tag: Customers
  spec_file: polar-sh-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.78
  evidence: GET /customers/  customers:list  List Customers; POST /customers/  customers:create  Create
    Customer; GET /customers/{id}/state
  reason: CRUD over customer records plus a consolidated customer state read — maintenance of the customer
    master record. Mapped to Customer Data Management rather than any billing sub-capability.
- tag: License Keys
  spec_file: polar-sh-license-keys-api-openapi.yml
  capability_id: BC-4240.70
  capability_id_l1: BC-4240
  capability_name: Entitlement Enforcement
  confidence: 0.72
  evidence: POST /license-keys/validate  licenseKeys:validate  Validate License Key; POST /license-keys/activate  licenseKeys:activate  Activate
    License Key
  reason: Issuance, activation and validation of license keys is runtime resolution and enforcement of
    what a paying customer may use — Entitlement Enforcement.
- tag: Benefits
  spec_file: polar-sh-benefits-api-openapi.yml
  capability_id: BC-4240.10
  capability_id_l1: BC-4240
  capability_name: Plan & Entitlement Design
  confidence: 0.7
  evidence: 'POST /products/{id}/benefits  products:updateBenefits  Update Product Benefits; schemas:
    Benefit, BenefitCreate'
  reason: In Polar, 'benefits' are the entitlements attached to a product/plan that a purchaser receives
    — not employee benefits. Defining benefits and binding them to products matches Plan & Entitlement
    Design. Moderate confidence because the surface is thin and overlaps entitlement enforcement.