Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Sense website screenshot

Sense

Sense is a Cambridge, Massachusetts energy-intelligence company that builds a residential energy monitor and machine-learning platform for real-time whole-home electricity disaggregation. The Sense Monitor installs in a home electrical panel, samples voltage and current at one million times per second, and uses signature-based machine-learning models to identify individual appliances and loads behind a single point of measurement. The Sense iOS, Android, and web apps surface device-level usage, always-on load, solar production, time-of-use cost, and goal tracking to homeowners. For utilities and grid operators, Sense embeds its disaggregation software into next-generation AMI 2.0 smart meters through partnerships with meter manufacturers such as Landis+Gyr, providing grid-edge visibility, fault detection, load-management, demand-response, and virtual-power-plant enablement. Sense also runs a partner program for smart-device integration with thermostats, EV chargers, heat pumps, and home-service providers. Sense has not released an official public developer API; community developers maintain reverse-engineered, unofficial clients in Python, Node.js, and Home Assistant against an undocumented and unsupported endpoint. Sense's revenue model is hardware sales of the consumer monitor and licensing of its disaggregation software to utilities and meter OEMs.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Sense the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sense scores 7.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 7.6/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.9 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Sense

Each block below is one kind of artifact we hold for Sense. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Sense Energy Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Sense — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 1

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/sense-energy · machine-readable index on apis.io