Strava is adding an $11.99 monthly fee for developer API access and moving public profiles and fitness club listings behind authentication to combat AI scraping
Context & Ripple Effects
Strava had already tightened its API terms in 2024, barring third parties from using its data in AI models and making cross-app fitness-data aggregation harder. The new access controls extend that shift from contractual limits to paid and authenticated access.
The company has also been building premium, AI-led coaching capabilities and acquired Runna in 2025, making control over activity data and the user relationship more strategically important than broad third-party distribution.
First-order effects
- Developers that rely on Strava’s API now face a recurring access cost, while public-profile and club-listing access requires authentication rather than anonymous retrieval.
- Strava gains a stronger technical and commercial boundary around data that could otherwise be collected at scale for AI systems or reused by third-party services.
Second-order effects
- Fitness apps, wearable platforms, and aggregation tools with Strava integrations may need to absorb the fee, pass it to customers, narrow Strava-linked features, or prioritize alternative data sources.
- The authentication requirement raises friction for services built around discovering athletes, clubs, or activity communities from public Strava pages, reinforcing Strava as the gatekeeper for those interactions.
Third-order effects
- If this pattern persists, fitness platforms may increasingly treat user activity graphs as controlled inputs for their own premium and AI products rather than interoperable ecosystem data.
- The move points to a more fragmented fitness-data market, where interoperability depends less on open public surfaces and more on paid, policy-governed platform access.
The trend: Consumer platforms are converting formerly open data and developer surfaces into authenticated, monetized channels as AI scraping raises the value and risk of proprietary user data.