Data sources

Steam only covers the Steam ecosystem, so cross-platform totals must never be presented as global player counts.

• current players
• news
• achievements
• store metadata

Respect Riot policy: no hidden MMR calculators, no unfair advantage tooling, and no exposed API keys.

• League of Legends match history
• ranked context
• TFT data
• Data Dragon assets

OpenDota is community data, not Valve-official. Pages must show sample size and fallback status.

• Dota 2 hero stats
• public match data
• parsed replay data
• community meta signals

This is island and experience analytics, not a full player-profile competitive stats API.

• Fortnite island performance
• engagement metrics
• creator ecosystem trends

This is experience-level Roblox data. It should not be merged into one global Roblox player total.

• active Roblox experience players
• visits
• favorites
• votes
• icons

The current implementation aggregates a top-stream sample. It is a directional hype signal, not a guaranteed full category viewer total.

• most watched games
• viewer momentum
• live stream sample
• hype signals

Some high-value account actions require explicit user authorization and should stay opt-in.

• Destiny 2 profiles
• characters
• manifest data
• inventory-aware tools

Regional namespaces and locale handling must be modeled from day one.

• World of Warcraft profiles
• Diablo data
• game-data namespaces

Account tools must be opt-in and should avoid storing personal inventory data unless required.

• Guild Wars 2 game data
• items
• achievements
• account opt-in tools

Respect game-specific endpoint limits and never expose API tokens in client code.

• Clash Royale cards
• Clash of Clans clans
• Brawl Stars brawlers
• mobile battle logs

Endpoint freshness can vary by region, so source pages should show when data was last checked.

• World of Tanks accounts
• vehicles
• clan data
• World of Warships stats