slug: hilt-so provider: Hilt 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: 6 edges: - tag: Webhooks spec_file: hilt-so-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.88 evidence: POST /v1/webhooks/endpoints Create webhook endpoint; POST /v1/webhooks/deliveries/{delivery_id}/replay Replay a webhook delivery; GET /v1/webhooks/events List emitted webhook events reason: Endpoint lifecycle, signed test events, delivery listing and replay are exactly outbound webhook subscription and delivery-reliability management. - tag: Support spec_file: hilt-so-support-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.85 evidence: POST /v1/support/tickets Create support ticket; GET /v1/support/tickets/{ticket_id} Ticket thread; POST /v1/support/tickets/{ticket_id}/message Add message to ticket reason: Ticket creation, listing and threaded messaging is inbound customer contact capture and resolution — customer inquiry management. - tag: API Keys spec_file: hilt-so-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/keys create_key_v1_keys_post Create Key; DELETE /v1/keys/{key_id} revoke_key_v1_keys__key_id__delete Revoke Key; schemas KeyUsageSummary, KeyActivityItem reason: Issuance, listing and revocation of API keys used by developers integrating with the Hilt Pay API — Developer Identity & Credential Management. Key usage summaries hint at consumption governance, hence slight ambiguity on the sub-capability. - tag: Integrations spec_file: hilt-so-integrations-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.78 evidence: POST /v1/integrations/zapier/hooks Subscribe a Zapier REST Hook; GET /v1/integrations/events List emitted events for integrations; schemas WebhookEndpoint, WebhookDelivery, IntegrationWebhookCapabilities reason: Operations subscribe/unsubscribe outbound REST hooks and list emitted events for integrators — outbound webhook/event subscription lifecycle on the developer platform, not a domain business function. - tag: Billing spec_file: hilt-so-billing-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.75 evidence: POST /v1/billing/checkout/stripe Create Stripe Checkout; GET /v1/billing/summary Get Billing Summary; schemas StripeInvoiceHistoryResponse, BillingPlanCardResponse reason: 'This is the vendor''s own recurring-plan billing: Stripe checkout and customer billing portal, plan card, invoice history and billing summary — subscription billing and revenue management. Spans payment collection and invoicing/statement views, so L1 only.' - tag: Memberships spec_file: hilt-so-memberships-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.75 evidence: GET /v1/memberships/renewal-intelligence Renewal cohorts, reminders, and reporting; POST /v1/memberships/{membership_id}/gift Gift extra access time to a member; GET /v1/memberships/{membership_id}/reactivation Get renewal and reactivation links reason: Memberships here are recurring paid access grants with periods, renewal, reactivation, gifting and access delivery — subscription/entitlement lifecycle management. Evidence spans renewal, modification and entitlement delivery, so L1 only.