specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
provider: Unum
providerId: unum
publisherName: Unum Group
serviceCategory: Insurance
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Insurance
  - Benefits Administration
  - FinOps
  - FOCUS
description: 'FinOps shape for Unum: API access is bundled into a partner or employer benefits contract rather than billed as a developer plan, so a public FOCUS line-item model is not available.'
sources:
  - https://www.unum.com/
notes: No public usage-based billing surface for Unum APIs. Costs are embedded in the underlying group insurance/benefits contract; FinOps observability is not exposed by Unum directly.
billingModel:
  pricingCategory: Bundled with Insurance Contract
  billingFrequency: Per-Contract
  billingCurrency: USD
  chargeCategories:
    - Purchase
focusColumns:
  ServiceName: Unum
  ServiceCategory: Insurance
  ProviderName: Unum
  PublisherName: Unum Group
  InvoiceIssuerName: Unum Group
  BillingCurrency: USD
meters:
  - name: contracted_access
    description: Access provisioned under a partner or employer agreement; not metered as a developer billing line
    unit: varies
    aggregation: count
principles:
  - name: Visibility
    description: API consumption is not surfaced via a public usage API; partners must request usage reports through their Unum account team.
  - name: Allocation
    description: Costs flow through the parent benefits/HRIS contract; allocation happens in the customer's HR/finance system, not in Unum-provided telemetry.
  - name: Optimization
    description: Optimization is contract-driven (benefit design, integration scope) rather than runtime (API call patterns).
  - name: Accountability
    description: Owned by the HR / benefits sponsor inside the customer organization, with the integration partner accountable for technical use.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com