Sense

Sense is a ClimateTech company founded in 2013 that provides home energy intelligence through a high-resolution electrical monitoring device installed in residential electrical panels. The Sense platform captures real-time electricity usage data and uses machine learning to disaggregate power consumption into individual device-level signatures, enabling homeowners to understand exactly which appliances are using electricity and when. The API provides access to real-time power consumption and solar production data via a WebSocket realtime feed, and historical trend data via a REST interface covering daily, weekly, monthly, and annual usage breakdowns. Sense also supports device detection data, grid exchange metrics, and push notifications through integrations including Amazon Alexa. The company pivoted in 2025 to embed its machine learning technology directly into next-generation smart meters deployed by utility partners, expanding its reach to tens of millions of homes without requiring standalone hardware purchases.

Sense publishes 5 APIs on the APIs.io network, including Authentication API, Devices API, History API, and 2 more. Tagged areas include Energy, Home Energy Monitoring, IoT, Smart Home, and Electricity.

The Sense catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Sense’s developer surface includes authentication, documentation, engineering blog, pricing, and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

45.7/100 developing ▬ flat Agent 25/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessFreemiumSelf serve⚡ Free to try

1 APIs

EnergyHome Energy MonitoringIoT Smart Home Electricity SolarDevice DetectionReal-Time Data Climate Tech

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 45.7/100 · developing

Contract Quality 12.2 / 19

Developer Ergonomics 3.6 / 15

Access Clarity 7.5 / 15

Operational Transparency 5.1 / 10

Contract Governance 0.9 / 9

Discoverability 5.1 / 8

Regulatory Posture 3.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/sense: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Sense Realtime API

The Sense Realtime API delivers live electricity usage data via a WebSocket connection, streaming second-by-second power consumption readings for the whole home and identified d...

Sense Authentication API

Authenticate and manage sessions

Sense Devices API

Device-level energy data and device information

Sense History API

Historical energy usage and solar production data

Sense Monitors API

Monitor overview, status, and device detection

Sense Users API

User-level timeline and usage data

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Sense Client Authentication API

OPEN COLLECTION

Sense Client Authentication Devices API

OPEN COLLECTION

Sense Client Authentication History API

OPEN COLLECTION

Sense Client Authentication Monitors API

OPEN COLLECTION

Sense Client Authentication Users API

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Sense Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Sense Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Sense Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Sense Context

8 classes · 39 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Sense API Rules

5 rules · 3 warnings 2 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

Sense Device

7 properties

JSON SCHEMA

Sense Realtime Payload

6 properties

JSON SCHEMA

Sense Usage History

3 properties

JSON SCHEMA

Examples 5

Example request and response payloads for these APIs.

Sense Authenticate Request

2 fields

EXAMPLE

Sense Authenticate Response

4 fields

EXAMPLE

Sense Realtime Payload

6 fields

EXAMPLE

Sense Solar History Response

1 fields

EXAMPLE

Sense Usage History Response

3 fields

EXAMPLE

Security Posture 2

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

Sense Authentication

http · 1 scheme

SECURITY

Sense Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Sense Agentic Access

15 operations · 3 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrg

GitHubOrg

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

aid: sense
name: Sense
description: Sense is a ClimateTech company founded in 2013 that provides home energy intelligence through a high-resolution
  electrical monitoring device installed in residential electrical panels. The Sense platform captures real-time electricity
  usage data and uses machine learning to disaggregate power consumption into individual device-level signatures, enabling
  homeowners to understand exactly which appliances are using electricity and when. The API provides access to real-time power
  consumption and solar production data via a WebSocket realtime feed, and historical trend data via a REST interface covering
  daily, weekly, monthly, and annual usage breakdowns. Sense also supports device detection data, grid exchange metrics, and
  push notifications through integrations including Amazon Alexa. The company pivoted in 2025 to embed its machine learning
  technology directly into next-generation smart meters deployed by utility partners, expanding its reach to tens of millions
  of homes without requiring standalone hardware purchases.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/sense.png
url: https://raw.githubusercontent.com/api-evangelist/sense/refs/heads/main/apis.yml
created: '2026-06-13'
modified: '2026-06-13'
specificationVersion: '0.23'
tags:
- Energy
- Home Energy Monitoring
- IoT
- Smart Home
- Electricity
- Solar
- Device Detection
- Real-Time Data
- Climate Tech
tags_raw:
- Energy
- Home Energy Monitoring
- IoT
- Smart Home
- Electricity
- Solar
- Device Detection
- Real-Time Data
- ClimateTech
apis:
- aid: sense:sense-realtime-api
  name: Sense Realtime API
  description: The Sense Realtime API delivers live electricity usage data via a WebSocket connection, streaming second-by-second
    power consumption readings for the whole home and identified devices. The feed includes current wattage draw, solar production
    output when applicable, grid import and export values, and the real-time on/off status of machine-learning identified
    devices. Clients authenticate using a bearer token obtained from the Client API and connect to the secure WebSocket endpoint
    parameterized with the monitor ID.
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://sense.com
  baseURL: wss://clientrt.sense.com/monitors
  tags:
  - Energy
  - WebSocket
  - Real-Time
  - Solar
  - IoT
  properties:
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: StatusPage
    url: https://status.sense.com
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
- aid: sense:sense-authentication-api
  name: Sense Authentication API
  description: Authenticate and manage sessions
  humanURL: https://sense.com
  baseURL: https://api.sense.com/apiservice/api/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/sense-authentication-api-openapi.yml
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: GitHubOrg
    url: https://github.com/scottbonline/sense
  - type: StatusPage
    url: https://status.sense.com
  - type: Blog
    url: https://blog.sense.com
  - type: LinkedIn
    url: https://www.linkedin.com/company/senseenergy
  - type: X
    url: https://x.com/sense
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
- aid: sense:sense-devices-api
  name: Sense Devices API
  description: Device-level energy data and device information
  humanURL: https://sense.com
  baseURL: https://api.sense.com/apiservice/api/v1
  tags:
  - Devices
  properties:
  - type: OpenAPI
    url: openapi/sense-devices-api-openapi.yml
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: GitHubOrg
    url: https://github.com/scottbonline/sense
  - type: StatusPage
    url: https://status.sense.com
  - type: Blog
    url: https://blog.sense.com
  - type: LinkedIn
    url: https://www.linkedin.com/company/senseenergy
  - type: X
    url: https://x.com/sense
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
- aid: sense:sense-history-api
  name: Sense History API
  description: Historical energy usage and solar production data
  humanURL: https://sense.com
  baseURL: https://api.sense.com/apiservice/api/v1
  tags:
  - History
  properties:
  - type: OpenAPI
    url: openapi/sense-history-api-openapi.yml
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: GitHubOrg
    url: https://github.com/scottbonline/sense
  - type: StatusPage
    url: https://status.sense.com
  - type: Blog
    url: https://blog.sense.com
  - type: LinkedIn
    url: https://www.linkedin.com/company/senseenergy
  - type: X
    url: https://x.com/sense
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
- aid: sense:sense-monitors-api
  name: Sense Monitors API
  description: Monitor overview, status, and device detection
  humanURL: https://sense.com
  baseURL: https://api.sense.com/apiservice/api/v1
  tags:
  - Monitors
  properties:
  - type: OpenAPI
    url: openapi/sense-monitors-api-openapi.yml
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: GitHubOrg
    url: https://github.com/scottbonline/sense
  - type: StatusPage
    url: https://status.sense.com
  - type: Blog
    url: https://blog.sense.com
  - type: LinkedIn
    url: https://www.linkedin.com/company/senseenergy
  - type: X
    url: https://x.com/sense
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
- aid: sense:sense-users-api
  name: Sense Users API
  description: User-level timeline and usage data
  humanURL: https://sense.com
  baseURL: https://api.sense.com/apiservice/api/v1
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/sense-users-api-openapi.yml
  - type: Website
    url: https://sense.com
  - type: Documentation
    url: https://help.sense.com
  - type: GitHubOrg
    url: https://github.com/scottbonline/sense
  - type: StatusPage
    url: https://status.sense.com
  - type: Blog
    url: https://blog.sense.com
  - type: LinkedIn
    url: https://www.linkedin.com/company/senseenergy
  - type: X
    url: https://x.com/sense
  - type: Plans
    url: plans/sense-plans-pricing.yml
  - type: RateLimits
    url: rate-limits/sense-rate-limits.yml
  - type: FinOps
    url: finops/sense-finops.yml
common:
- type: AgenticAccess
  url: agentic-access/sense-agentic-access.yml
- type: DomainSecurity
  url: security/sense-domain-security.yml
- type: Authentication
  url: authentication/sense-authentication.yml
- type: Website
  url: https://sense.com
- type: Documentation
  url: https://help.sense.com
- type: GitHubOrg
  url: https://github.com/scottbonline/sense
- type: LinkedIn
  url: https://www.linkedin.com/company/senseenergy
- type: Blog
  url: https://blog.sense.com
- type: Pricing
  url: https://sense.com/homes/buy-monitor/
- type: StatusPage
  url: https://status.sense.com
- type: X
  url: https://x.com/sense
- type: Plans
  url: plans/sense-plans-pricing.yml
- type: RateLimits
  url: rate-limits/sense-rate-limits.yml
- type: FinOps
  url: finops/sense-finops.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/sense"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/sense/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/sense/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.