Uplight

Uplight is a Boulder, Colorado energy technology company formed in 2019 from the merger of Tendril and Simple Energy and expanded through the acquisitions of EnergySavvy, FirstFuel, Ecotagious, EEme, and DERMS/VPP provider AutoGrid (closed February 2024). It sells software to electric and gas utilities and retailers in North America, Europe, and Asia rather than to consumers, covering energy efficiency and electrification marketplaces, home energy reports, rate engagement, demand response, distributed energy resource management (DERMS), virtual power plants, and a utility data lake with analytics. In the United States value chain Uplight sits on the utility side of the meter as a vendor and orchestration layer between the utility, its customers, and connected devices, and it publicly states support for OpenADR, IEEE 2030.5, Modbus, DNP3 and other SCADA protocols for DER control. Its API posture is honestly closed — a Developer Platform exists and is marketed to utilities and ecosystem partners, the documentation portal at docs.uplight.com serves a public landing shell but every Documentation and API Reference path redirects to a ReadMe login, and the production gateway at api.uplight.com answers anonymously only with HTTP 401 and a bearer-token error. No consumer usage-data API, no open market data, no downloadable OpenAPI, and no Green Button or ESPI reference could be found. Uplight is a software vendor, not a regulated data holder, so no consumer data mandate applies to it.

Uplight publishes 1 API on the APIs.io network. Tagged areas include Energy, United States, Utilities, Electricity, and Gas.

Uplight’s developer surface includes documentation, API reference, engineering blog, privacy policy, and 18 more developer resources.

19.5/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
1 APIs
EnergyUnited StatesUtilitiesElectricityGasDemand ResponseDERGridVirtual Power PlantDERMSEnergy EfficiencyCustomer Engagement

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 19.5/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 3.2 / 17
Access Clarity 4.9 / 17
Operational Transparency 0.3 / 11
Contract Governance 0.0 / 10
Discoverability 6.5 / 9
Regulatory Posture 4.9 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/. This rating is computed from github.com/api-evangelist/uplight: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Uplight Developer Platform API

Uplight markets a Developer Platform that exposes customer, program, eligibility, enrollment, device, and energy-flexibility data to utilities and ecosystem partners through API...

Security Posture 2

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

Uplight Authentication

http-bearer · 1 scheme

SECURITY

Uplight Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 7

The organization behind the API

Scroll for all 7

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: uplight
url: https://raw.githubusercontent.com/api-evangelist/uplight/refs/heads/main/apis.yml
name: Uplight
kind: company
description: Uplight is a Boulder, Colorado energy technology company formed in 2019 from the merger of Tendril and Simple
  Energy and expanded through the acquisitions of EnergySavvy, FirstFuel, Ecotagious, EEme, and DERMS/VPP provider AutoGrid
  (closed February 2024). It sells software to electric and gas utilities and retailers in North America, Europe, and Asia
  rather than to consumers, covering energy efficiency and electrification marketplaces, home energy reports, rate engagement,
  demand response, distributed energy resource management (DERMS), virtual power plants, and a utility data lake with analytics.
  In the United States value chain Uplight sits on the utility side of the meter as a vendor and orchestration layer between
  the utility, its customers, and connected devices, and it publicly states support for OpenADR, IEEE 2030.5, Modbus, DNP3
  and other SCADA protocols for DER control. Its API posture is honestly closed — a Developer Platform exists and is marketed
  to utilities and ecosystem partners, the documentation portal at docs.uplight.com serves a public landing shell but every
  Documentation and API Reference path redirects to a ReadMe login, and the production gateway at api.uplight.com answers
  anonymously only with HTTP 401 and a bearer-token error. No consumer usage-data API, no open market data, no downloadable
  OpenAPI, and no Green Button or ESPI reference could be found. Uplight is a software vendor, not a regulated data holder,
  so no consumer data mandate applies to it.
image: https://uplight.com/wp-content/uploads/2019/07/cropped-uplight-icon-1-192x192.png
tags:
- Energy
- United States
- Utilities
- Electricity
- Gas
- Demand Response
- DER
- Grid
- Virtual Power Plant
- DERMS
- Energy Efficiency
- Customer Engagement
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: uplight:uplight-developer-platform-api
  name: Uplight Developer Platform API
  description: Uplight markets a Developer Platform that exposes customer, program, eligibility, enrollment, device, and energy-flexibility
    data to utilities and ecosystem partners through APIs. The reference is published on a ReadMe portal at docs.uplight.com,
    but the /developer path 302-redirects to dash.readme.com login, so no operation, schema, scope, or rate limit is publicly
    readable. The production gateway at api.uplight.com is real and reachable (Kong Enterprise 3.10) but returns HTTP 401
    with an "Invalid or no token provided" error to every anonymous request, including /openapi.json, /swagger.json, /v1,
    and /.well-known/openid-configuration. Listed here as a real but fully gated surface; no endpoints are claimed because
    none are documented publicly.
  humanURL: https://docs.uplight.com/
  baseURL: https://api.uplight.com
  tags:
  - Energy
  - Utilities
  - Demand Response
  - DER
  - Customer Engagement
  properties:
  - type: Documentation
    url: https://docs.uplight.com/
  - type: APIReference
    url: https://docs.uplight.com/developer/reference
  - type: Documentation
    url: https://uplight.com/platform/
  - type: Documentation
    url: https://uplight.com/blog/uplights-developer-platform-decisions-made-easy-for-customers-and-utilities/
common:
- type: DomainSecurity
  url: security/uplight-domain-security.yml
- type: Website
  url: https://uplight.com/
- type: Documentation
  url: https://docs.uplight.com/
- type: APIReference
  url: https://docs.uplight.com/developer/reference
- type: About
  url: https://uplight.com/about-us/
- type: Platform
  url: https://uplight.com/platform/
- type: Partners
  url: https://uplight.com/partners/
- type: Blog
  url: https://uplight.com/blog/
- type: BlogRSS
  url: https://uplight.com/blog/feed/
- type: Press
  url: https://uplight.com/press/
- type: Privacy
  url: https://uplight.com/privacy-policy/
- type: PrivacyPolicy
  url: https://uplight.com/privacy-policy/
- type: TermsOfService
  url: https://uplight.com/terms-of-service/
- type: CookiePolicy
  url: https://uplight.com/cookie-policy/
- type: Contact
  url: https://uplight.com/contact-us/
- type: Resources
  url: https://uplight.com/resources/
- type: Compliance
  url: https://uplight.com/resources/integrated-approach-security-privacy-compliance/
- type: Conformance
  url: conformance/uplight-conformance.yml
- type: Lifecycle
  url: lifecycle/uplight-lifecycle.yml
- type: LLMsTxt
  url: llms/uplight-llms.txt
- type: GitHubOrganization
  url: https://github.com/Uplight-Inc
- type: LinkedIn
  url: https://www.linkedin.com/company/uplight
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com