# Entergy

> Entergy Corporation is an integrated energy company headquartered in New Orleans, Louisiana,
> delivering electricity to more than 3 million utility customers across Arkansas, Louisiana,
> Mississippi and Texas. Entergy publishes NO developer portal, NO API documentation and NO
> product API. This file was generated by API Evangelist from what Entergy's own hosts served
> on 2026-09-06; Entergy does not serve an llms.txt of its own (https://www.entergy.com/llms.txt
> returns 404).

## What you can actually call

- [WordPress REST API root](https://www.entergy.com/wp-json/): The only anonymous,
  machine-readable, callable API on an Entergy host. A self-describing route index naming 9
  namespaces and 173 routes, linked from every page as rel="https://api.w.org/". It serves
  entergy.com's own content - news, pages, media, categories, search - not energy data.
- [Derived OpenAPI](openapi/entergy-wordpress-rest-openapi.yml): 151 paths / 277 operations,
  derived route-for-route from that index. Response bodies are not described by the index and
  are therefore not asserted.
- [Agent skill](skills/entergy-read-newsroom-content.md): how to page the news routes
  correctly and which errors are terminal.

## What exists but is gated

- [ArcGIS Server](https://gis.entergy.com/arcgis/rest/info?f=json): ArcGIS Server 10.7.1 on
  Entergy's own GIS host. The info document is anonymous; every service requires a token from
  https://gis.entergy.com/arcgis/tokens/. /arcgis/rest/services answers HTTP 200 with
  {"error":{"code":499,"message":"Token Required"}} - branch on the body, not the status.
- [SOAP catalog WSDL](wsdl/entergy-arcgis-catalog.wsdl): served at
  https://gis.entergy.com/arcgis/services?wsdl, HTTP 200, 7 operations, soap:address pointing
  back at gis.entergy.com. A real published contract; the services behind it need a token.
- [Green Button Connect My Data](https://myentergyadvisor.entergy.com/greenbutton/welcome):
  Entergy Texas customer interval-meter data sharing under NAESB REQ.21 ESPI. Real program,
  real vendor registration at /greenbutton/green-vendor, but no endpoint, scope list or schema
  is published anonymously.
- [WordPress Abilities API](https://www.entergy.com/wp-json/wp-abilities/v1/abilities): the
  agent-facing WordPress namespace is installed but returns 401 rest_forbidden.
- [myEntergy customer portal](https://www.myentergy.com/s/login/): Salesforce Experience Cloud.
  Every path, including every /.well-known/ path, answers 200 with the same login SPA shell -
  do not mistake those 200s for documents.

## What does not exist

- No developer portal, no API reference, no getting-started guide, no sandbox, no SDK, no CLI.
- No package on npm, PyPI, RubyGems or crates.io.
- No MCP server, no A2A agent card, no /.well-known/api-catalog, no security.txt
  (404 on every Entergy host).
- No API status page, no changelog, no deprecation policy, no published rate limits,
  no idempotency mechanism.
- The outage map at https://www.entergy.com/viewoutages is a DataCapable application on
  www.etrviewoutage.com. Any API behind it belongs to DataCapable, not Entergy.

## Company

- [Entergy](https://www.entergy.com): corporate site (Cloudflare managed challenge - send a
  browser User-Agent).
- [Newsroom](https://www.entergy.com/news) and [RSS feed](https://www.entergy.com/feed)
- [Terms of use](https://www.entergy.com/terms) and [Privacy](https://www.entergy.com/privacy)
- [Contact](https://www.entergy.com/contact) | [Careers](https://jobs.entergy.com/)