# Provenance stamped 2026-10-07 (roadmap#943): written by an API Evangelist sweep (dated 2026-06-14 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-06-14'
specification: FinOps Framework
specificationVersion: '1.0'
provider: GMX
providerId: gmx
publisherName: GMX
serviceCategory: API
created: '2026-06-14'
modified: '2026-06-14'
tags:
  - DeFi
  - Perpetual Exchange
  - DEX
  - Trading
  - Leverage
  - Liquidity Pools
  - GLP
  - GM Tokens
  - GLV
  - Arbitrum
  - Avalanche
  - Web3
  - FinOps
  - Cost Management
  - FOCUS
description: >-
  FinOps framework alignment for the GMX API surface. As of June 2026, GMX's
  public API surfaces (Oracle API, GraphQL, Integration API) carry no direct
  monetary charges. The primary indirect cost of using GMX APIs is on-chain
  gas consumption when executing trades or liquidity actions via the GMX
  contracts on Arbitrum or Avalanche. This document provides a FOCUS-shaped
  mapping for tracking any infrastructure, gas, and operational costs associated
  with building on GMX APIs.
principles:
  - name: Visibility
    description: >-
      Make all API consumption costs (infrastructure, gas, third-party RPC
      node fees) visible to engineering, product, and finance teams.
  - name: Allocation
    description: >-
      Tag every chargeable on-chain interaction and RPC call with the
      consuming team, environment, application, and feature so cost can
      be allocated accurately.
  - name: Optimization
    description: >-
      Continuously evaluate request patterns, caching (GMX recommends
      caching oracle snapshots), batching, and network selection (Arbitrum
      vs Avalanche fee differences) to minimize total cost per useful
      unit of work.
  - name: Accountability
    description: >-
      Establish budget owners and chargeback/showback flows for each team
      consuming GMX API data or triggering on-chain transactions.
domains:
  - name: API Consumption
    description: >-
      HTTP calls to the GMX API, Oracle API, and GraphQL endpoints. Currently
      no direct monetary charge; cost is operational infrastructure only.
    costDrivers:
      - request_volume
      - rpc_node_provider_fees
      - egress_bandwidth
    focusMapping:
      ChargeCategory: Usage
      ChargeClass: Consumption
      ServiceCategory: API
      ServiceSubcategory: Provider API
  - name: On-Chain Gas
    description: >-
      Ethereum/Arbitrum/Avalanche gas fees incurred when executing trades,
      managing liquidity positions, or relaying orders via GMX contracts.
      This is the primary real monetary cost when integrating with GMX.
    costDrivers:
      - transaction_count
      - gas_price
      - contract_complexity
      - network_congestion
    focusMapping:
      ChargeCategory: Usage
      ChargeClass: Consumption
      ServiceCategory: Blockchain
      ServiceSubcategory: Gas Fees
  - name: RPC Infrastructure
    description: >-
      Third-party RPC node provider costs (e.g., Alchemy, QuickNode, Infura)
      for reading on-chain state when using the GmxSdk (SDK v1) in RPC mode.
    costDrivers:
      - rpc_call_volume
      - archive_node_usage
      - tier_selection
    focusMapping:
      ChargeCategory: Usage
      ChargeClass: Consumption
      ServiceCategory: API
      ServiceSubcategory: Infrastructure 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:
  - GMX's REST and GraphQL APIs are free to call; primary integration cost
    is gas for on-chain actions and optional RPC node provider fees.
  - Reconcile scaffolded mappings against actual infrastructure invoices and
    any future monetization of the GMX API surface.