slug: pagesnap
provider: Pagesnap
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: 2
edges:
- tag: Support
  spec_file: pagesnap-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 createSupportTicket — "Open an accountless support ticket"; POST /v1/support/{ticket_id}/messages
    — "Add a requester message"
  reason: Ticket creation, retrieval and requester messaging is inbound customer contact capture and resolution
    — customer inquiry management. Only residual doubt is whether issues/complaints (.20) would fit better.
- tag: Billing
  spec_file: pagesnap-billing-api-openapi.yml
  capability_id: BC-4250
  capability_id_l1: BC-4250
  capability_name: Subscription Billing & Revenue Management
  confidence: 0.8
  evidence: POST /v1/checkout — "Create a crypto upgrade invoice"; GET /pay/{order_id}/receipt.pdf — "Get
    a PDF payment receipt"; GET /pay/{order_id}/status — "Poll payment status"
  reason: Operations create upgrade invoices, activate the plan on payment, and issue receipts — clearly
    subscription billing and payment collection. Left at L1 because the surface straddles invoicing/receipts
    (.30) and payment authorisation/collection (.40) without favouring either.