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: Activision Blizzard providerId: activision-blizzard publisherName: Blizzard Entertainment, Inc. serviceCategory: Gaming / Game Data 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: - Gaming - Battle.net - FinOps - FOCUS description: FOCUS-aligned FinOps scaffold for Activision Blizzard's Battle.net API. There is no Blizzard invoice for non-commercial use; FinOps relevance is restricted to compute/egress costs incurred by the integrating application when polling Battle.net data and to any commercial-licence fee negotiated directly with Blizzard. sources: - https://develop.battle.net/ - https://community.developer.battle.net/ notes: No published commercial billing model. Reconciled flag is false because there is no provider invoice to map to FOCUS columns. billingModel: pricingCategory: Free (Non-Commercial) / Negotiated Commercial Licence billingFrequency: Annual billingCurrency: USD chargeCategories: - Purchase focusColumns: ServiceName: Battle.net API ServiceCategory: Gaming / Game Data ProviderName: Blizzard Entertainment PublisherName: Blizzard Entertainment, Inc. InvoiceIssuerName: Blizzard Entertainment, Inc. BillingCurrency: USD ChargeCategory: Purchase meters: - name: api_request description: Battle.net API request consumed against per-OAuth-client limits. Not directly billed under the free developer tier, but the unit consumers track for cost-of-integration analysis. unit: request aggregation: sum dimensions: - region - game - endpoint - name: commercial_licence description: Annual commercial-licence fee for Battle.net API use, where contracted. unit: year aggregation: sum dimensions: - tier principles: - name: Visibility description: There is no Blizzard usage API. Track outbound calls by OAuth2 client at the consumer's egress / API gateway and watch for 429 responses as the practical "approaching budget" signal. - name: Allocation description: Allocate compute and egress costs of polling Battle.net data to the consuming product (e.g. guild website, leaderboard service, esports backend) rather than to Blizzard. - name: Optimization description: Cache aggressively, prefer scheduled batch refreshes over on-demand calls, share OAuth clients only when limits permit, and use change-aware patterns where exposed. - name: Accountability description: The integrator's engineering team owns rate-limit headroom and any commercial-licence renewal. maintainers: - FN: Kin Lane email: info@apievangelist.com