slug: postalform-com
provider: PostalForm
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: 4
edges:
- tag: Webhook Endpoints
  spec_file: postalform-com-webhook-endpoints-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.82
  evidence: POST /api/v1/webhook-endpoints createWebhookEndpoint "Configure a customer webhook endpoint
    for status events"; "rotateWebhookEndpointSecret"
  reason: Operations create, list, disable and re-key outbound customer webhook endpoints — this is lifecycle
    management of webhook/event subscriptions exposed to integrating developers, which the frame models
    explicitly as BC-4270.80 rather than any mail/postal business capability.
- tag: Webhook Events
  spec_file: postalform-com-webhook-events-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.8
  evidence: GET /api/v1/webhook-events "List customer webhook events for the workspace"; POST .../replay
    "Queue a customer webhook event for replay"; schemas WebhookDeliveryAttempt, CustomerWebhookEventType
  reason: Event listing and replay with delivery-attempt schemas is outbound event delivery reliability
    for the public API ecosystem, matching Webhook & Event Subscription Management; the Letter/MailOrderStatus
    schemas are just payload types, not the capability performed here.
- tag: API Keys
  spec_file: postalform-com-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.7
  evidence: GET /api/v1/api-keys "List API key prefixes and status"; POST /api/v1/api-keys/rotate "Rotate
    a test or live API key"
  reason: Listing and rotating customer-facing API keys for the public SDK API is issuance and stewardship
    of developer credentials, which the frame explicitly carves out as Developer Identity & Credential
    Management. Moderate confidence because credential endpoints are often pure plumbing, but here they
    are the self-service developer credential surface of a public API.
- tag: Credits
  spec_file: postalform-com-credits-api-openapi.yml
  capability_id: BC-4250.40
  capability_id_l1: BC-4250
  capability_name: Payment Collection & Dunning
  confidence: 0.7
  evidence: GET /api/v1/credits/balance "Get prepaid credit balance"; GET /api/v1/credits/payment-methods
    "List saved live billing payment methods"; POST /api/v1/credits/checkout-session "Create a prepaid
    credit top-up checkout session"
  reason: Prepaid balance, saved payment methods, auto-refill thresholds and top-up checkout sessions
    constitute payment-method management and collection of funds for consumption-based service usage,
    matching Payment Collection & Dunning within subscription billing. Some ambiguity vs usage metering/rating,
    hence 0.7.