slug: notyfi provider: Notyfi 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: notyfi-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 Register an outgoing tracker webhook; POST /api/v1/webhooks/{webhook_id}/rotate-secret Rotate a webhook signing secret; schema WebhookEventType reason: Lifecycle of outbound webhook endpoints, signing secrets and test deliveries maps directly to Webhook & Event Subscription Management. - tag: Keys spec_file: notyfi-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 /api/v1/keys Mint a new API key (the plaintext is returned ONCE, here); DELETE /api/v1/keys/{key_id} Revoke an API key; schema ApiKeyScope reason: Issuance, listing and revocation of scoped API keys for external API consumers is developer credential management within the developer-platform capability. - tag: Billing spec_file: notyfi-billing-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.75 evidence: GET /api/v1/billing Current plan, limits, and tracker usage; POST /api/v1/billing/checkout Create or resume a Stripe-hosted Pro Checkout session; POST /api/v1/billing/portal reason: Plan/limit/usage status plus Stripe checkout and customer-portal sessions is subscription billing and payment collection; evidence spans usage, plan and payment so no single L2 is clearly named.