slug: ok-capsule
provider: OK Capsule
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Transportation & Logistics
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: Fulfillments
  spec_file: ok-capsule-fulfillments-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.75
  evidence: POST /v2/fulfillments  createFulfillment  Creates a fulfillment.  /  GET /v2/orders/{id}/fulfillments  Retrieve
    fulfillments for an order  /  GET /v2/fulfillments/{id}/label  Retrieve a fulfillment signed label
    url.
  reason: Fulfillment records are created against orders and carry shipping labels, which is order fulfilment
    orchestration for the on-demand supplement supply chain. Mapped to Order Fulfilment Management rather
    than a transport-carrier capability because the vendor is a manufacturer/fulfiller, not a carrier;
    the label URL is the only transport-adjacent artefact and is insufficient to justify a T&L-specific
    edge.
- tag: Orders
  spec_file: ok-capsule-orders-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.75
  evidence: POST /v2/orders  createOrder  Creates an order.  /  GET /v2/orders/by-client-order-id/{clientCustomOrderId}  Retrieve
    an order by client custom order ID  /  GET /v2/orders/carts  listOrdersCarts
  reason: Full lifecycle CRUD over customer orders that the platform then manufactures and ships, matching
    order capture and fulfilment orchestration. Sub-capability choice carries some ambiguity (order capture
    vs. broader supply chain execution), hence 0.75.
- tag: Clients
  spec_file: ok-capsule-clients-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: POST /v2/clients createClient "Creates a client."; schemas Client, User
  reason: Clients are the brands/telehealth providers that are this vendor's customers; create/read/update/delete
    of client records is customer master-record management.
- tag: Consumers
  spec_file: ok-capsule-consumers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: 'POST /v2/consumers createConsumer "Creates a consumer."; vendor description: "manage consumers"'
  reason: Full lifecycle CRUD over end-consumer records, explicitly described by the vendor as managing
    consumers — customer data/master record management.
- tag: Integrations Orders
  spec_file: ok-capsule-integrations-orders-api-openapi.yml
  capability_id: BC-520.40
  capability_id_l1: BC-520
  capability_name: Order Fulfilment Management
  confidence: 0.7
  evidence: POST /v2/integrations/orders  createIntegrationOrder  Creates an order. / PUT /v2/integrations/orders/{id}  updateIntegrationOrder
  reason: Order capture and amendment through an integration channel on a platform whose stated purpose
    is to 'programmatically create supplement orders ... and track shipments'. Same order object as the
    main Orders surface, hence order fulfilment; slight discount because the tag is an integration-channel
    variant.
  recovered_from: sweep-20260829T005356Z-edges.json