NAESB website screenshot

NAESB

The North American Energy Standards Board (NAESB) is the non-profit, industry-consensus standards development organization formed in 1994 that writes the business practice standards for the North American wholesale and retail natural gas and electricity markets, organized into four quadrants — Wholesale Electric (WEQ), Retail Electric (REQ), Wholesale Gas (WGQ) and Retail Gas (RGQ). Headquartered in Houston, Texas, its home market is the United States (with Canadian and Mexican participation). NAESB sits upstream of every utility, ISO/RTO and energy-data platform in the value chain: it authors REQ.21 Energy Services Provider Interface (ESPI), the standard that is the basis of every Green Button implementation in North America, and it operates the NAESB Electric Industry Registry (EIR) that underpins electronic tagging across the wholesale electric market. Its API posture is deliberately split and must not be overstated. NAESB is not a data holder and no consumer-data mandate applies to it; the Green Button standard it publishes is adopted by US utilities purely voluntarily, with no federal obligation behind it. The specifications themselves are copyright-protected and paywalled — $8,000/year membership, $2,000 per quadrant version, or $250 per individual standard — with only a free, view-only, three-business-day evaluation waiver for non-members. The single genuinely open artifact is the set of ESPI XML schemas, released under Apache 2.0 as a documented one-time exception to the NAESB Copyright Policy and downloadable anonymously after a one-click terms-of-use acknowledgement. The one real API NAESB operates, the EIR webRegistry SOAP service administered by OATI, is closed: it requires a paid registry subscription and a digitally signed X.509 certificate issued by an NAESB-Authorized Certification Authority, and its endpoint could not even complete a TLS handshake anonymously. Open standard schemas, closed standards text, closed registry API, no consumer data and no open market data of its own.

NAESB publishes 2 APIs on the APIs.io network. Tagged areas include Energy, United States, Standards, Utilities, and Electricity.

NAESB’s developer surface includes documentation, tooling, pricing, support, authentication, changelog, and 23 more developer resources.

37.1/100 thin ▬ flat Agent 19/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessPaidFree trial
2 APIs
EnergyUnited StatesStandardsUtilitiesElectricityGasGreen ButtonSmart MeteringEnergy MarketsGrid

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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/.
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/naesb: 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 2

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

NAESB REQ.21 Energy Services Provider Interface (ESPI)

The NAESB REQ.21 ESPI Model Business Practices define the data exchange protocol for transferring retail energy usage information from a utility (Data Custodian) to a Third Part...

NAESB Electric Industry Registry (EIR) webRegistry Web Services

The NAESB Electric Industry Registry is the central repository of registry information used by the North American wholesale electric industry for electronic tagging; it replaced...

Security Posture 2

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

Naesb Authentication

mutualTLS/oauth2 · 2 schemes

SECURITY

Naesb Domain Security

TLSv1.2 · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: naesb
url: https://raw.githubusercontent.com/api-evangelist/naesb/refs/heads/main/apis.yml
name: NAESB
kind: company
description: 'The North American Energy Standards Board (NAESB) is the non-profit, industry-consensus standards development
  organization formed in 1994 that writes the business practice standards for the North American wholesale and retail natural
  gas and electricity markets, organized into four quadrants — Wholesale Electric (WEQ), Retail Electric (REQ), Wholesale
  Gas (WGQ) and Retail Gas (RGQ). Headquartered in Houston, Texas, its home market is the United States (with Canadian and
  Mexican participation). NAESB sits upstream of every utility, ISO/RTO and energy-data platform in the value chain: it authors
  REQ.21 Energy Services Provider Interface (ESPI), the standard that is the basis of every Green Button implementation in
  North America, and it operates the NAESB Electric Industry Registry (EIR) that underpins electronic tagging across the wholesale
  electric market. Its API posture is deliberately split and must not be overstated. NAESB is not a data holder and no consumer-data
  mandate applies to it; the Green Button standard it publishes is adopted by US utilities purely voluntarily, with no federal
  obligation behind it. The specifications themselves are copyright-protected and paywalled — $8,000/year membership, $2,000
  per quadrant version, or $250 per individual standard — with only a free, view-only, three-business-day evaluation waiver
  for non-members. The single genuinely open artifact is the set of ESPI XML schemas, released under Apache 2.0 as a documented
  one-time exception to the NAESB Copyright Policy and downloadable anonymously after a one-click terms-of-use acknowledgement.
  The one real API NAESB operates, the EIR webRegistry SOAP service administered by OATI, is closed: it requires a paid registry
  subscription and a digitally signed X.509 certificate issued by an NAESB-Authorized Certification Authority, and its endpoint
  could not even complete a TLS handshake anonymously. Open standard schemas, closed standards text, closed registry API,
  no consumer data and no open market data of its own.'
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: paid
  onboarding: application-approval
  trial: true
  try_now: false
  public: false
  label: Paid membership or per-document purchase · Registry API requires accredited certificate
  confidence: high
  source:
  - https://www.naesb.org/ESPI_Standards.asp
  - https://www.naesb.org//misc/naesb_matl_order_espi_standards.pdf
  - https://www.naesb.org//misc/NAESB_Nonmember_Evaluation.pdf
  - https://www.naesb.org/pdf4/eir_webregistry_technical_guide_v6.1_1018.pdf
  generated: '2026-07-27'
  method: manual
image: https://www.naesb.org/images/naesb-logo.jpg
tags:
- Energy
- United States
- Standards
- Utilities
- Electricity
- Gas
- Green Button
- Smart Metering
- Energy Markets
- Grid
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
enrichment:
  round: '2026-07-27'
  note: 'Contract discovery upgraded this repo. The prior round recorded that the EIR webRegistry endpoint could not complete
    a TLS handshake anonymously. That was a trust-chain failure, not a handshake failure: the server certificate is issued
    by OATI''s private webCARES Server Issuing CA and does not chain to a public root. Once that is accounted for, the host
    answers, the full 30-operation WSDL is served to anonymous callers, and the service returns a well-formed SOAP refusal
    ("Please present a valid certificate that is associated with a NAESB EIR user") rather than nothing at all. The WSDL is
    now harvested verbatim and is this provider''s real machine-readable contract.'
apis:
- aid: naesb:naesb-espi-green-button
  name: NAESB REQ.21 Energy Services Provider Interface (ESPI)
  description: The NAESB REQ.21 ESPI Model Business Practices define the data exchange protocol for transferring retail energy
    usage information from a utility (Data Custodian) to a Third Party with the Retail Customer's authorization. ESPI is the
    industry-consensus standard that is the basis of every Green Button implementation in North America and is the standard
    endorsed by the Green Button Alliance. NAESB publishes the standard; it does not operate an ESPI endpoint — each Data
    Custodian utility hosts its own, so there is no NAESB base URL. The Atom/XML payload schemas (NAESBespiSchema.xsd and
    retailcustomer.xsd, v3.3 and v4.0) are released under the Apache License 2.0 as a one-time exception to the NAESB Copyright
    Policy and are harvested here verbatim. The narrative Model Business Practices themselves are copyright-protected and
    must be purchased or obtained through NAESB membership. The v4.0 schema encodes an OAuth 2.0 authorization model directly
    — ApplicationInformation carries authorizationServerAuthorizationEndpoint, authorizationServerTokenEndpoint, authorizationServerRegistrationEndpoint,
    GrantType, TokenEndPointMethod, scope and OAuthError.
  humanURL: https://www.naesb.org/ESPI_Standards.asp
  tags:
  - Green Button
  - ESPI
  - Energy Usage
  - Smart Metering
  - Authentication
  - Retail Electric
  tags_raw:
  - Green Button
  - ESPI
  - Energy Usage
  - Smart Metering
  - OAuth
  - Retail Electric
  properties:
  - type: XMLSchema
    url: schemas/naesb-espi_v4.xsd
  - type: XMLSchema
    url: schemas/naesb-customer_v4.xsd
  - type: XMLSchema
    url: schemas/naesb-espi.xsd
  - type: XMLSchema
    url: schemas/naesb-customer.xsd
  - type: Documentation
    url: https://www.naesb.org/ESPI_Standards.asp
  - type: Pricing
    url: https://www.naesb.org//misc/naesb_matl_order_espi_standards.pdf
  - type: TermsOfService
    url: https://www.naesb.org/copyright.asp
  - type: AgentSkill
    name: Authorize and retrieve Green Button energy usage under NAESB ESPI
    url: skills/naesb-espi-green-button-authorization.md
- aid: naesb:naesb-eir-webregistry
  name: NAESB Electric Industry Registry (EIR) webRegistry Web Services
  description: 'The NAESB Electric Industry Registry is the central repository of registry information used by the North American
    wholesale electric industry for electronic tagging; it replaced the NERC TSIN in 2012 and is administered for NAESB by
    Open Access Technology International (OATI) as OATI webRegistry. It exposes a documented SOAP 1.1 web service with methods
    including DownloadEntity, DownloadBA, DownloadPSE and DownloadACA, described across the 121-page OATI webRegistry Technical
    Guide v6.1. The service is HTTPS-only, and per section 2.5 of that guide no request is processed unless it carries a digitally
    signed certificate associated with a registered webRegistry user; those certificates are issued by NAESB-Authorized Certification
    Authorities. Access also requires a paid registry subscription. The full WSDL — one service, one portType and thirty Download*
    operations over thirty entity structs — IS served to anonymous callers and is harvested here verbatim. Two things complicate
    reaching it: the server certificate is issued by OATI''s private "webCARES Server Issuing CA 2025" and does not chain
    to a public root, so default trust stores fail verification (curl exit 60); and once that is accounted for, an anonymous
    SOAP call returns HTTP 200 with ReturnCode 1 / FAILURE and the message "Please present a valid certificate that is associated
    with a NAESB EIR user". The contract is public; the data behind it is not.'
  humanURL: https://www.naesb.org/weq/weq_eir.asp
  baseURL: https://www.naesbwry.oati.com/cgi-bin/webplus.dll?Script=/naesbwry/WREG-Web-Services-Main.wml
  tags:
  - Registry
  - Wholesale Electric
  - SOAP
  - E-Tagging
  - Grid
  properties:
  - type: Documentation
    url: https://www.naesb.org/weq/weq_eir.asp
  - type: TechnicalGuide
    url: https://www.naesb.org/pdf4/eir_webregistry_technical_guide_v6.1_1018.pdf
  - type: APIReference
    url: https://www.naesb.org/pdf4/eir_webregistry_technical_guide_v6.1_1018.pdf
  - type: UserGuide
    url: https://www.naesb.org/pdf4/eir_webregistry_user_guide_v5.0_1023.pdf
  - type: GettingStarted
    url: https://www.naesb.org/pdf4/eir_webregistry_quick_start_guide_v3.0_1023.pdf
  - type: FAQ
    url: https://www.naesb.org/pdf4/eir_user_interface_faq_0921.pdf
  - type: Pricing
    url: https://www.naesb.org/pdf4/naesb_eir_subscription_fee010715.docx
  - type: Authentication
    url: https://www.naesb.org/pdf4/ac_authorities_2023.pdf
  - type: WSDL
    url: wsdl/naesb-eir-webregistry.wsdl
  - type: ChangeLog
    url: https://www.naesb.org/weq/weq_eir.asp
  - type: Roadmap
    url: https://www.naesb.org/weq/weq_eir_requests.asp
  - type: AgentSkill
    name: Download a NAESB EIR registry publication
    url: skills/naesb-download-eir-registry.md
common:
- type: X-MCPServerCandidate
  url: mcp/naesb-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/naesb-domain-security.yml
- type: Website
  url: https://www.naesb.org/
- type: About
  url: https://www.naesb.org/aboutus.asp
- type: ContactUs
  url: https://www.naesb.org/contactus.asp
- type: Documentation
  url: https://www.naesb.org/ESPI_Standards.asp
- type: Tools
  url: https://www.naesb.org/naesb_tools.asp
- type: Certification
  url: https://www.naesb.org/materials/certification.asp
- type: CertifiedProducts
  url: https://www.naesb.org/pdf2/cert_products.pdf
- type: CertificationAuthorities
  url: https://www.naesb.org/pdf4/ac_authorities_2023.pdf
- type: Pricing
  url: https://www.naesb.org/pdf/ordrform.pdf
- type: Licensing
  url: https://www.naesb.org/copyright.asp
- type: TermsOfService
  url: https://www.naesb.org/pdf4/terms&conditions.pdf
- type: PrivacyPolicy
  url: https://www.naesb.org/privacy.asp
- type: Membership
  url: https://www.naesb.org/membership.asp
- type: Newsletter
  url: https://www.naesb.org/bulletin_newsletter.asp
- type: PressReleases
  url: https://www.naesb.org/news.asp
- type: WhitePapers
  url: https://www.naesb.org/white_papers.asp
- type: Support
  url: https://www.naesb.org/contactus.asp
- type: Compliance
  url: https://www.naesb.org/materials/certification.asp
- type: Authentication
  url: authentication/naesb-authentication.yml
- type: Conventions
  url: conventions/naesb-conventions.yml
- type: ErrorCatalog
  url: errors/naesb-error-codes.yml
- type: Lifecycle
  url: lifecycle/naesb-lifecycle.yml
- type: ChangeLog
  url: changelog/naesb-changelog.yml
- type: Conformance
  url: conformance/naesb-conformance.yml
- type: DataModel
  url: data-model/naesb-data-model.yml
- type: LLMsTxt
  url: llms/naesb-llms.txt
- type: AgentSkill
  url: skills/_index.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/naesb"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/naesb/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/naesb/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.

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