I came up in sports when the data was a stat line in the morning paper and the fan experience was a hot dog, a bad seat, and a prayer that your team didn’t blow a lead in the ninth. I worked marketing for four professional sports teams. I spent time at a sports licensee where we turned logos into revenue and merchandise into identity. I ran campaigns at an integrated marketing agency where the brief was always the same: reach the fan, hold the fan, convert the fan.
Back then, we did it with instinct, hustle, and a lot of expensive guesswork. A good promotion was something you felt in your gut before you proved it in a report. Today’s era is one in which “SuperStat” Harvey Pollack would have been unstoppable at creating new categories for teams, leagues, coaches, GMs, players, and, most of all, fans to noodle nonstop over. (Personal note: Pollack was The Philadelphia Wings statistician 1974-75, in addition to his role with the Philadelphia 76ers. Working games with Harvey was an education every minute.)
What I heard from the CTOs of the NBA, MLB, and NHL at SBJ Tech Week last week in New York was the world I always knew was coming. These are organizations that have spent decades building digital infrastructure, and now that infrastructure is paying off at a scale none of us in the old-school sports marketing trenches could have imagined. Pitch tracking. Immersive camera arrays. AI running across workflows in real time. The fan experience isn’t a campaign anymore. It’s a system.
That’s exactly why I built DevLocker.dev.
Because the leagues have the infrastructure. Most developers and sports tech builders don’t know where to start. DevLocker.dev is the on-ramp: a curated, daily-updated directory of the APIs, MCP Servers, and datasets that power this world. The MLB Stats API. The NHL API. The NBA API. ESPN endpoints. Sports betting data feeds. SportsData.io. All of it organized, vetted, and accessible.
But here’s what nobody is talking about yet, and should be.
The APIs and MCP Servers sitting in DevLocker.dev aren’t just tools for scoreboard apps and fantasy sports platforms. They are untapped engines for things the industry hasn’t built yet. Consider what’s possible.
A sponsorship activation engine that listens to live game-state data and triggers contextual brand moments automatically: a comeback in the fourth quarter fires a specific ad unit, a no-hitter in progress unlocks a real-time fan offer. The data is available. Nobody has connected those dots at scale.
A merchandise demand prediction model that correlates player performance APIs with purchasing behavior, so a licensee knows to produce more jerseys before the hot streak becomes a headline. I spent years at a licensee making those calls by feel. The data to make them by science exists today.
A cross-sport audience overlap tool built for sponsors trying to reach fans who follow multiple leagues, using publicly available roster, attendance, and engagement datasets to find the white space between the NBA playoff viewer and the MLB casual fan. That product doesn’t exist. It could be built in weeks.
An accessibility layer using play-by-play APIs to deliver real-time descriptive audio experiences for visually impaired fans at home, without requiring a broadcast partner. The data streams are live. The application is not.
AI agents built on MCP Servers that sit inside a team’s front office workflow and surface contract comparable data, injury history patterns, or opponent tendencies before a coaching staff meeting. Agentic AI needs data pipelines to be useful. Those pipelines are already in the directory.
The leagues figured out that technology is the connective tissue between the game and the fan. DevLocker.dev is the connective tissue between the builder and the tools.
I’ve spent my career at that intersection, in the stadium, in the boardroom, in the agency, and at the licensee. The ideas were always there. Now, for the first time, so are the tools. All in one place, ready to build on.
The only question is who builds first.
Andy Abramson is the founder and CEO of Comunicano and the curator of DevLocker.dev, a daily-updated directory of sports APIs, MCP Servers, and datasets for the sports developer and AI community.