Video streaming on apis.io is led by the pipes, not the streamers

Video streaming on apis.io is led by the pipes, not the streamers

The Video Streaming industry on apis.io has 36 providers and 241 APIs, and this time the member rows add up to the header. The scores are not spread evenly. The four providers in the strong band are a video-infrastructure company, a cloud ingest service, a webinar platform and a surveillance-camera maker. The household streamers are at the bottom. Netflix scores 9.2, Paramount 3.9 and NBC 5.1. The median member scores 18.6, and 13 of the 36 have no API in the catalog at all.

The functional bands

Band Providers (composite)
Video infrastructure Mux 65.8, Amazon Kinesis Video Streams 57.2, Qwilt 41.0
Live and creator tooling WebinarJam 55.8, Restream 35.0
Camera and surveillance video LVT 54.8, AngelCam 48.7
Consumer platforms Spotify 47.0, Roku 37.3
Studios and networks Warner Bros. Discovery 32.3, Comcast 31.7, Netflix 9.2, Paramount 3.9

What the record shows

The developer surface belongs to the companies that sell the pipes. Mux alone has 38 of the industry’s 241 APIs, and it sells ingest, encoding, delivery and analytics to developers as its product. Kinesis Video Streams and Qwilt’s CDN are the same kind of business. The streamers buy this infrastructure. They do not publish it.

Demand and surface point in opposite directions. The industry’s own demand block ranks Netflix, Walt Disney, Disney and Spotify as its top adopters. Of those four, only Spotify publishes a real public API (15 in the catalog). Netflix has one API page and scores minimal. The companies people search for are the ones with the least to offer an integrator.

Membership is tag-driven, and it has drifted. The page says membership “is computed from every provider in the catalog whose tags match this vertical.” That is how Riot Games, Blizzard Entertainment, Picogrid (a defense and public-safety company) and Major League Baseball ended up in video streaming. Disney appears twice. walt-disney is the company, and disney is described as a “community-maintained” database of characters. That is a catalog defect, and it is ours to fix. The community database should not be counted as the studio.

Where to start

If you are building playback, ingest or analytics, start with Mux and Kinesis Video Streams. They are the only two members whose public surface matches the job. If you need live multistreaming, use Restream. For camera feeds, start with AngelCam, which has 29 APIs and scores developing. For a related view, the provisional streaming-video market reads a 41-provider cohort by who integrates with whom.

Takeaway

This industry has the weakest public APIs at exactly the companies with the most demand. That gap belongs to the streamers, and the rubric reports it fairly. Two things are ours to fix. We should tighten the tag rule that pulls game publishers and a defense company into video streaming, and we should stop counting a fan database as the Walt Disney Company. Doing both would make the median an honest number.

Browse the industry at apis.io/industries/video-streaming/.

← The apis.io markets section cannot read integrations for 35 percent of its cohort