OPOWER

Opower is a customer engagement and energy efficiency cloud platform for utilities, now delivered as Oracle Utilities Opower after Oracle acquired the company in 2016. The platform analyzes hundreds of billions of smart-meter reads to power home energy reports, bill forecasting and comparison, usage disaggregation, neighbor comparisons, personalized tips, high-bill alerts and thresholds, and multi-channel customer notifications for utilities such as PG&E, Exelon and National Grid. For developers, Oracle Utilities Opower exposes a RESTful Digital Self Service - Energy Management API and an Integration Hub GraphQL API, both secured with OAuth 2.0 client-credentials, letting utilities integrate customer, utility-account, usage, billing, disaggregation, and notification data into their own digital self-service channels.

OPOWER publishes 2 APIs on the APIs.io network. Tagged areas include Company, Energy, Utilities, Energy Efficiency, and Customer Engagement.

OPOWER’s developer surface includes documentation, API reference, getting-started guide, support, changelog, authentication, sandbox, and 11 more developer resources.

🌐 Visit website 📡 Source on GitHub

22.9/100 emerging ▬ flat Agent 15/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

AccessSelf serve

2 APIs 1 MCP Servers

CompanyEnergyUtilitiesEnergy EfficiencyCustomer EngagementSmart MeterUsage DataOracle

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 22.9/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 10.0 / 17

Commercial Clarity 0.0 / 17

Operational Transparency 1.7 / 11

Governance 1.3 / 10

Discoverability 6.5 / 9

Regulatory Posture 3.5 / 15

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 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/opower: 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 2

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

Oracle Utilities Opower REST API (Digital Self Service - Energy Management)

RESTful API for viewing and managing Opower customer, utility-account, usage, billing, disaggregation, neighbor-comparison, tips, threshold and notification data. HTTP/REST with...

Oracle Utilities Opower GraphQL API (Integration Hub)

GraphQL API delivered through the Oracle Utilities Opower Integration Hub for querying Opower platform data. OAuth 2.0 secured.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

ChangeLog

ChangeLog

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: opower
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/opower.png
name: OPOWER
description: Opower is a customer engagement and energy efficiency cloud platform for utilities, now delivered as Oracle Utilities
  Opower after Oracle acquired the company in 2016. The platform analyzes hundreds of billions of smart-meter reads to power
  home energy reports, bill forecasting and comparison, usage disaggregation, neighbor comparisons, personalized tips, high-bill
  alerts and thresholds, and multi-channel customer notifications for utilities such as PG&E, Exelon and National Grid. For
  developers, Oracle Utilities Opower exposes a RESTful Digital Self Service - Energy Management API and an Integration Hub
  GraphQL API, both secured with OAuth 2.0 client-credentials, letting utilities integrate customer, utility-account, usage,
  billing, disaggregation, and notification data into their own digital self-service channels.
url: https://raw.githubusercontent.com/api-evangelist/opower/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Energy
- Utilities
- Energy Efficiency
- Customer Engagement
- Smart Meter
- Usage Data
- Oracle
apis:
- name: Oracle Utilities Opower REST API (Digital Self Service - Energy Management)
  description: RESTful API for viewing and managing Opower customer, utility-account, usage, billing, disaggregation, neighbor-comparison,
    tips, threshold and notification data. HTTP/REST with JSON, OAuth 2.0 client-credentials auth, versioning carried in the
    URL path (e.g. customer-data-v2, usage-v1, notification-contact-v1).
  humanURL: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/
  baseURL: https://cxapi.opower.com
  tags:
  - REST
  - Usage
  - Billing
  - Notifications
  properties:
  - type: APIReference
    url: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/rest-endpoints.html
  - type: GettingStarted
    url: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/QuickStart.html
- name: Oracle Utilities Opower GraphQL API (Integration Hub)
  description: GraphQL API delivered through the Oracle Utilities Opower Integration Hub for querying Opower platform data.
    OAuth 2.0 secured.
  humanURL: https://docs.oracle.com/en/industries/energy-water/integration-hub/graphql-user-guide/index.html
  baseURL: https://cxapi.opower.com
  tags:
  - GraphQL
  - Integration
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: http://www.opower.com
- type: DeveloperPortal
  url: https://docs.oracle.com/en/industries/utilities/opower-platform/
- type: Documentation
  url: https://docs.oracle.com/en/industries/energy-water/digital-self-service/
- type: APIReference
  url: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/rest-endpoints.html
- type: GettingStarted
  url: https://docs.oracle.com/en/industries/energy-water/digital-self-service/restapi/QuickStart.html
- type: Support
  url: https://support.oracle.com/
- type: ChangeLog
  url: https://docs.oracle.com/en/cloud/saas/readiness/energy-and-water-all.html
- type: ChangeLog
  url: changelog/opower-changelog.yml
- type: Authentication
  url: authentication/opower-authentication.yml
- type: Conventions
  url: conventions/opower-conventions.yml
- type: ErrorCatalog
  url: errors/opower-problem-types.yml
- type: Lifecycle
  url: lifecycle/opower-lifecycle.yml
- type: Sandbox
  url: sandbox/opower-sandbox.yml
- type: Conformance
  url: conformance/opower-conformance.yml
- type: DataModel
  url: data-model/opower-data-model.yml
- type: MCPServer
  url: mcp/opower-mcp.yml
- type: LLMsTxt
  url: llms/opower-llms.txt
- type: DomainSecurity
  url: security/opower-domain-security.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 12
  pass: local-v1