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: Riot Games
providerId: riot-games
publisherName: Riot Games, Inc.
serviceCategory: Gaming Developer Platform
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: true
tags:
  - Riot Games
  - Gaming
  - Developer API
  - FinOps
  - FOCUS
description: >-
  The Riot Games Developer API is free; there is no Riot-issued invoice for API consumption.
  FinOps treatment for consumers therefore focuses on the indirect cost of consuming and
  storing Riot data (compute, storage, egress on the consumer's own cloud) and the policy
  cost of staying compliant with Riot's developer terms.
sources:
  - https://developer.riotgames.com/docs/portal
  - https://developer.riotgames.com/policies.html
billingModel:
  pricingCategory: Free
  billingFrequency: None
  billingCurrency: USD
  chargeCategories:
    - Adjustment
focusColumns:
  ServiceName: Riot Games Developer API
  ServiceCategory: Gaming Developer Platform
  ProviderName: Riot Games
  PublisherName: Riot Games, Inc.
  BillingCurrency: USD
meters:
  - name: api_requests
    description: >-
      Requests consumed against Riot's developer API; not billed by Riot but useful for
      forecasting consumer-side infrastructure cost.
    unit: request
    aggregation: sum
    dimensions:
      - region
      - api
      - key_tier
  - name: rate_limit_breaches
    description: >-
      Count of 429 responses; an operational signal that limits or method-call patterns need
      tuning, not a billable line.
    unit: response
    aggregation: count
    dimensions:
      - region
      - rate_limit_type
principles:
  - name: Visibility
    description: >-
      Track Riot API consumption from the client side (request log, 429 rate, retry queue
      depth); Riot does not publish a usage or billing API.
  - name: Allocation
    description: >-
      Allocate the consumer-side infrastructure cost of running Riot integrations
      (compute/storage/egress) to the product team that owns the integration, not to
      undifferentiated platform cost.
  - name: Optimization
    description: >-
      Cache match and account data to stay under per-region method limits; coalesce repeated
      summoner/match lookups; request a production-key raise before scaling the request rate
      itself.
  - name: Accountability
    description: >-
      The product owner of the consumer application owns adherence to Riot's developer
      terms; budget concerns are limited to consumer-side infra and staff cost.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com