Smart Home
Providers using this tag (90)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Developing 8 Usable, with meaningful gaps to close
Thin 20 Limited public surface area
Emerging 28 Early or largely undocumented
Minimal 32 Almost no public developer surface
APIs with this tag (9)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Developing 1 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 3 Early or largely undocumented
Companies reaching this through an API (2)
These companies publish an API, specification or operation carrying “Smart Home” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 85 providers in the APIs.io catalog tagged Smart Home, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 58.4 | 58.1 | +0.3 | 85 |
| Contract Governance | 5.7 | 6.3 | -0.6 | 85 |
| Contract Quality | 16.9 | 17.6 | -0.7 | 85 |
| Access Clarity | 23.7 | 26.5 | -2.8 | 85 |
| Developer Ergonomics | 20.3 | 23.2 | -2.9 | 85 |
| Operational Transparency | 10.3 | 13.7 | -3.4 | 85 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 13% | 14% | -1 |
| MCP server (first-party) | 7% | 12% | -5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 16% | 11% | +5 |
| Security | 96% | 98% | -2 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 15% | 14% | +1 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Allegion 59.8
- 2 Tibber 55.8
- 3 Atmospore Pollen Forecasts 53.6
- 4 Clevergy 51
- 5 Lunar Energy 48.3
- 6 Nest 47.8
- 7 Ring 43.8
- 8 Sense 42.6
- 9 Google Nest Smart Device Management 41.5
- 10 Rachio 40.8
- 1 IFTTT 42.1
- 2 ADT 41
- 3 Samsung 38.5
- 4 Atmospore Pollen Forecasts 37.7
- 5 Ring 34.5
- 6 1KOMMA5° 31.5
- 7 Clevergy 30.8
- 8 Allegion 30
- 9 Franklin Whole Home 29
- 10 Tibber 27.3
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.