# Provenance stamped 2026-10-07 (roadmap#943): written by an API Evangelist sweep (dated 2026-05-22 by the file itself), not
# harvested from the provider. `method: generated` so the economics campaign may replace it with a
# dated, verbatim transcription; every figure below is unverified until it does.
# Coverage demoted 2026-10-07 (roadmap#942, PLAN.md Stage A): this file was written by an API Evangelist
# sweep and names no billing unit, meters or pricing category read from the provider — it restates the
# FinOps framework. It is `x-coverage: unmeasured`, and the FOCUS alignment it claimed has been removed.
x-coverage: unmeasured
method: generated
generated: '2026-05-22'
specification: FinOps Framework
specificationVersion: '1.0'
provider: Motional
providerId: motional
publisherName: Motional
serviceCategory: API
created: '2026-05-22'
modified: '2026-05-22'
tags:
- Autonomous Vehicles
- Robotaxi
- Self-Driving
- Hyundai
- Aptiv
- Open Dataset
- nuScenes
- Lidar
- FinOps
- Cost Management
- FOCUS
description: FinOps framework alignment for the Motional API surface. Provides a FOCUS-shaped mapping for cost allocation,
  usage measurement, and unit-economics reporting.
principles:
- name: Visibility
  description: Make API consumption costs visible to engineering, product, and finance teams in near real-time.
- name: Allocation
  description: Tag every chargeable API call with the consuming team, environment, application, and feature so cost can be
    allocated.
- name: Optimization
  description: Continuously evaluate request patterns, caching, batching, and tier selection to reduce cost per useful unit
    of work.
- name: Accountability
  description: Establish budget owners and chargeback / showback flows for each consuming team.
domains:
- name: API Consumption
  description: Per-call and per-quota usage charges across the Motional API surface.
  costDrivers:
  - request_volume
  - tier_selection
  - feature_use
  focusMapping:
    ChargeCategory: Usage
    ChargeClass: Consumption
    ServiceCategory: API
    ServiceSubcategory: Provider API
focusFields:
  required:
  - BillingPeriodStart
  - BillingPeriodEnd
  - ChargeCategory
  - ChargePeriodStart
  - ChargePeriodEnd
  - ProviderName
  - PublisherName
  - InvoiceIssuerName
  - ServiceName
  - ServiceCategory
  - BilledCost
  - EffectiveCost
  - ListCost
  - ContractedCost
  - PricingCategory
  - PricingUnit
  - PricingQuantity
  recommended:
  - SubAccountId
  - SubAccountName
  - ResourceId
  - ResourceName
  - ResourceType
  - Region
  - Tags
notes:
- Reconcile the scaffolded mapping above against Motional's actual invoice / billing model.