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 is listed with 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.
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 could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
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/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/uplight/"><img src="https://apis.io/badge/uplight/card.svg" alt="Uplight on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Machine-Readable Auth+10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
13 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Uplight markets a Developer Platform that exposes customer, program, eligibility, enrollment, device, and energy-flexibility data to utilities and ecosystem partners through API...
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.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- security
generated: '2026-11-06'
method: derived
image: https://uplight.com/wp-content/uploads/2019/07/cropped-uplight-icon-1-192x192.png
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
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
Uplight API — frequently asked questions
Does Uplight have an API?
Yes. APIs.io lists 1 API from Uplight, including Uplight Developer Platform API.
How do I authenticate with the Uplight API?
Uplight documents its authentication (http-bearer · 1 scheme). The details are profiled on APIs.io as Uplight Authentication.
Is the Uplight API ready for AI agents?
Uplight has a Kin Score of 17.6 out of 100 (emerging) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.