IoT and robotics is a substantial vertical in the catalog — 177 providers, 812 APIs — and it’s where the physical world grows a programmable control plane. The interesting thing about walking it is how many of the biggest surfaces belong to telecom carriers: connecting the device is still the foundational problem, and the companies that solved connectivity are the ones with the deepest APIs.
The bands
| Band | What it does | Providers on apis.io |
|---|---|---|
| Cellular IoT connectivity | SIMs, networks, device data | Orange Business (35 APIs), Vodafone (27), Verizon (17), Soracom (18) |
| Robotics & edge AI | Fleets, control, inference | Viam (14), Quantum Machines (13) |
| Devices, sensors & data | Readings, wearables, telemetry | Eaton (12), ThingSpeak (12), Fitbit (12) |
What’s shifted recently
- Connectivity became a platform, not a pipe. Soracom’s surface is the clearest example — SIM management, a managed data store, remote access, and cloud-integration adapters all exposed as APIs. The carriers followed: Orange, Vodafone, and Verizon now expose IoT connectivity management programmatically rather than through account managers.
- Robotics went API-first and gRPC-native. Viam models a robot as a set of component and service APIs — arms, cameras, motion planning, ML inference — with a gRPC contract shared across every SDK. That’s a genuinely modern take on a domain that used to mean bespoke firmware.
- The edge got a data plane. ThingSpeak, Eaton, and wearables like Fitbit show the pattern: capture readings at the device, sync to the cloud, expose them as a queryable time-series API. The sensor is dumb; the intelligence lives in the platform around it.
Where to start
- The IoT and Robotics industry page ranks all 177 providers.
- For connectivity as a platform, study Soracom.
- For a modern robotics contract, trace Viam.
The takeaway
IoT’s structure in the catalog tells a clear story: connectivity is the mature, deep layer (owned largely by carriers), robotics is the fast-modernizing one, and the device-data plane is where the long tail lives. Read the counts as a maturity gradient — the closer an API gets to the raw physical device, the younger and thinner the contract still tends to be.