Yes Energy

Yes Energy is a Boulder, Colorado power market data company serving the North American wholesale electricity markets — the seven ISOs and RTOs (ERCOT, PJM, MISO, CAISO, SPP, ISO-NE, NYISO) plus Canadian and Western markets. It aggregates, cleans, and enriches nodal locational marginal prices, FTR auction results, transmission and generation outages, real-time generation and flow telemetry, constraints, load, weather, and fuels data, and sells it through DataSignals (a REST API), DataSignals Cloud (Snowflake Secure Data Sharing), DataSignals Lake (bulk load into a customer warehouse), the PowerSignals and QuickSignals analyst front ends, EnCompass modeling, Live Power telemetry, Infrastructure Insights, Position Management, and bid-to-bill Submission Services. It sits in the private, commercial layer of the energy value chain: it does not generate, distribute, or retail electricity and it holds no consumer relationship — it resells and enriches public ISO/RTO market data to traders, IPPs, utilities, and asset developers. Its API posture is honestly closed: the DataSignals REST API is real and confirmed live at https://services.yesenergy.com/PS/rest/, but it answers every anonymous request with HTTP 401 and WWW-Authenticate Basic, and even the product documentation (help.yesenergy.com) redirects through services.yesenergy.com/PS/KnowledgeOwlAuthentication to a customer login. No public developer portal, no self-serve signup, no machine-readable specification, and no free tier are published. Home market is the United States. There is no consumer energy data mandate that applies to Yes Energy — it is not a utility, retailer, or metering agent, so Green Button, ESPI, and the Consumer Data Right are all out of scope — and while the underlying ISO/RTO market data is publicly available at the source, Yes Energy itself publishes none of it openly.

Yes Energy publishes 1 API on the APIs.io network. Tagged areas include Energy, United States, Energy Markets, Electricity, and Grid.

Yes Energy’s developer surface includes authentication, support, documentation, signup flow, pricing, engineering blog, product news, and 17 more developer resources.

23.0/100 emerging ▬ flat Agent 9/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs
EnergyUnited StatesEnergy MarketsElectricityGridMarket DataWholesale PowerISO RTORenewablesTrading

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 23.0/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 4.4 / 17
Commercial Clarity 5.8 / 17
Operational Transparency 1.7 / 11
Governance 0.3 / 10
Discoverability 6.5 / 9
Regulatory Posture 4.3 / 15
Agent readiness — 9/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 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/yes-energy: 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.

Yes Energy DataSignals API

DataSignals is Yes Energy's REST API for automated access to its North American wholesale power market data — nodal prices, transmission, generation, outages, constraints, weath...

Security Posture 2

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

Yes Energy Authentication

http · 1 scheme

SECURITY

Yes Energy Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

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

Learn 1

Tutorials, courses, talks, and written guidance

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 7

The organization behind the API

Scroll for all 7

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: yes-energy
url: https://raw.githubusercontent.com/api-evangelist/yes-energy/refs/heads/main/apis.yml
name: Yes Energy
kind: company
description: 'Yes Energy is a Boulder, Colorado power market data company serving the North American wholesale electricity
  markets — the seven ISOs and RTOs (ERCOT, PJM, MISO, CAISO, SPP, ISO-NE, NYISO) plus Canadian and Western markets. It aggregates,
  cleans, and enriches nodal locational marginal prices, FTR auction results, transmission and generation outages, real-time
  generation and flow telemetry, constraints, load, weather, and fuels data, and sells it through DataSignals (a REST API),
  DataSignals Cloud (Snowflake Secure Data Sharing), DataSignals Lake (bulk load into a customer warehouse), the PowerSignals
  and QuickSignals analyst front ends, EnCompass modeling, Live Power telemetry, Infrastructure Insights, Position Management,
  and bid-to-bill Submission Services. It sits in the private, commercial layer of the energy value chain: it does not generate,
  distribute, or retail electricity and it holds no consumer relationship — it resells and enriches public ISO/RTO market
  data to traders, IPPs, utilities, and asset developers. Its API posture is honestly closed: the DataSignals REST API is
  real and confirmed live at https://services.yesenergy.com/PS/rest/, but it answers every anonymous request with HTTP 401
  and WWW-Authenticate Basic, and even the product documentation (help.yesenergy.com) redirects through services.yesenergy.com/PS/KnowledgeOwlAuthentication
  to a customer login. No public developer portal, no self-serve signup, no machine-readable specification, and no free tier
  are published. Home market is the United States. There is no consumer energy data mandate that applies to Yes Energy — it
  is not a utility, retailer, or metering agent, so Green Button, ESPI, and the Consumer Data Right are all out of scope —
  and while the underlying ISO/RTO market data is publicly available at the source, Yes Energy itself publishes none of it
  openly.'
image: https://www.yesenergy.com/hubfs/Favicon.png
tags:
- Energy
- United States
- Energy Markets
- Electricity
- Grid
- Market Data
- Wholesale Power
- ISO RTO
- Renewables
- Trading
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.19'
apis:
- aid: yes-energy:datasignals-api
  name: Yes Energy DataSignals API
  description: 'DataSignals is Yes Energy''s REST API for automated access to its North American wholesale power market data
    — nodal prices, transmission, generation, outages, constraints, weather, and fuels — covering real-time and 15+ years
    of history, with time-series and object endpoints intended for Excel, Python, R, and system integration. The service host
    is live and confirmed at https://services.yesenergy.com/PS/rest/, which returns HTTP 401 with `WWW-Authenticate: Basic
    realm="Realm"` to anonymous callers; HTTP Basic credentials are issued only to paying subscribers. The endpoint reference
    and code examples live in the customer knowledge base at help.yesenergy.com, which 302-redirects to the services.yesenergy.com
    customer login, so no endpoint list, no scopes, and no machine-readable specification could be verified anonymously. Nothing
    beyond the base path and auth scheme is recorded here because nothing beyond that is publicly observable.'
  humanURL: https://www.yesenergy.com/products/datasignals
  baseURL: https://services.yesenergy.com/PS/rest/
  tags:
  - Energy Markets
  - Market Data
  - Electricity
  - Wholesale Power
  - Time Series
  properties:
  - type: Documentation
    url: https://www.yesenergy.com/products/datasignals
  - type: Documentation
    url: https://www.yesenergy.com/datasignals-20
  - type: Documentation
    url: https://www.yesenergy.com/solutions/it-data-scientist
  - type: Authentication
    url: https://services.yesenergy.com/PS/rest/
common:
- type: DomainSecurity
  url: security/yes-energy-domain-security.yml
- type: Authentication
  url: authentication/yes-energy-authentication.yml
- type: Conventions
  url: conventions/yes-energy-conventions.yml
- type: Lifecycle
  url: lifecycle/yes-energy-lifecycle.yml
- type: Conformance
  url: conformance/yes-energy-conformance.yml
- type: Packages
  url: packages/yes-energy-packages.yml
- type: LLMsTxt
  url: llms/yes-energy-llms.txt
- type: Website
  url: https://www.yesenergy.com/
- type: Products
  url: https://www.yesenergy.com/products
- type: Support
  url: https://www.yesenergy.com/support
- type: Documentation
  url: https://help.yesenergy.com/
- type: SignUp
  url: https://www.yesenergy.com/demo
- type: Contact
  url: https://www.yesenergy.com/contact
- type: Pricing
  url: https://www.yesenergy.com/packages
- type: StatusPage
  url: https://status.yesenergy.com/
- type: Blog
  url: https://www.yesenergy.com/blog
- type: BlogRSS
  url: https://www.yesenergy.com/blog/rss.xml
- type: News
  url: https://www.yesenergy.com/news
- type: About
  url: https://www.yesenergy.com/about
- type: PrivacyPolicy
  url: https://www.yesenergy.com/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/yes-energy/
- type: YouTube
  url: https://www.youtube.com/@yes-energy
- type: Partners
  url: https://www.yesenergy.com/partners/snowflake
- type: DataMarketplace
  url: https://app.snowflake.com/marketplace/providers/GZSOZ71OEK/Yes%20Energy
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com