Authentication issue
Key rejected, revoked, paused, or missing scope.
Support and service expectations
API Support for EnergyNetWatch Data Workflows
Support is centered on credentials, request traceability, usage controls, source context, and integration setup. Custom API and MCP customers can scope additional service expectations.
Support channel
Use the authenticated billing/support context or request-access form for account, API, billing, or MCP questions.
What to include
Send endpoint, timestamp, X-Request-ID, status code, and a short description. Do not send full API keys.
Response expectation
Starter access is handled as standard support. Custom API and enterprise workflows can define support expectations during scoping.
Maintenance
EnergyNetWatch may adjust API behavior, endpoint costs, coverage, or limits as datasets and source workflows change.
Coverage limits
Oil and gas records vary by state, source cadence, and dataset. Support can clarify what a source record supports, but cannot turn lagged source data into current activity.
Common support categories
Usage issue
402, 429, unexpected unit usage, or hard-stop behavior.
Data question
Coverage, loaded-through date, source caveat, or operator label review.
Integration issue
OpenAPI, MCP, client setup, headers, pagination, or error handling.