Fandom Sports Media (FDM.C) tweaks the in-game data API from Valorant

Fandom Sports Media (FDM.C) started developing its application programming interfaces (APIs) for in-game data from Valorant today, according to a press release.

Previously the company had finished developing APIs for League of Legends, DOTA 2, and CS:GO. Data acquired through the company’s API’s have given them the ability to produce prediction models and pattern recognition required for the platform’s launch.

“The dynamic capabilities of the Fandom platform is enabling the Company to remain nimble and pivot to emerging popular game titles. As gamers’ tastes and preferences mature and evolve, Fandom will remain at the forefront of those expanding preferences while reducing risk arising from changing trends whilst simultaneously growing our predictive coverage universe,” said David Vinokurov, CEO and president of Fandom Esports.

The company uses machine learning to determine the appropriate amount of actionable data, and therefore give their players the opportunity to interact in nearly real time with live streaming content in both the all ages prediction and regulated wagering verticals.

Fandom prefers neural networks that incorporate machine learning to person dependent limited predictions for their models.  This increases speed while decreasing the margin for error, while is what helps keep their pattern recognition using data contextualization tech separate from what’s already out there. Their successes with API’s an direct to publisher integration have given them the impetus required to further develop API’s and integrate Riot Games’ Esports title Valorant.

Valorant has been popular with streamers since it was released in June. Despite some bugs in the code, it’s been the recipient of favourable news and various professional esports players have started playing it regularly after Riot Games announced the Valorant Ignition Series competitive circuit, which commenced in June 2020.

—Joseph Morton

More on

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments