01 · Host
The API is ene't's, the account is the customer's
Calls go to ws.enet-navigator.de. The connector runs in the customer's network and uses the customer's machine account. Navigator is not a database on a server in the customer's rack.
For energy suppliers pricing with ene't Navigator
Pexon builds an enet Navigator API connector so Claude, ChatGPT or Copilot can read location properties, peak-load windows and grid fees on the customer's own Navigator machine account. ene't documents HTTP Basic authentication and publishes OpenAPI for two of those reads. The grid-charge specification returned an empty body on 5 November 2026. No Navigator MCP server was published.
What we build
Built on what ene't GmbH documents: location properties, electricity control zones, balancing areas, gas market areas, peak-load windows, switching times, grid charges. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# enet-navigator-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
get_location_properties: # address, date -> control zone, balancing area and gas market area
backend: GET /standorteigenschaften
mode: read
get_peak_load_windows: # address, year, voltage level -> peak-load windows, switching times and network operator
backend: GET /strom
mode: read
get_peak_load_by_operator_code: # operator code, year, voltage level -> peak-load windows
backend: GET /strom/codenummer
mode: read
get_grid_charges: # address, customer group, period -> grid charges, metering costs and levies
backend: confirmed in blueprint
mode: read
get_price_sheet: # network operator -> published price-sheet data
backend: confirmed in blueprint
mode: read
audit: every call logged with user, tool, arguments and the ene't Navigator responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 5 November 2026
| What we found | |
|---|---|
| Interfaces | Location properties REST (REST/JSON, docs public) · Peak-load windows REST (REST/JSON, docs public) · Grid-charge package (electricity) (REST/JSON, docs public) · BO4E repository REST (REST/JSON, docs public) |
| Authentication | A company admin creates a machine account in Navigator and assigns a licence that selects which webservices it may call. Each request sends that username and password as HTTP Basic authentication. ene't documents HTTP 401 for a wrong username or password and HTTP 403 when the licence does not cover the webservice. |
| Vendor MCP server | No vendor server. No Navigator MCP server is named on the ene't pages read on 5 November 2026. A search that day, and a public GitHub repository search, did not return one from ene't. |
| Vendor AI assistant | None found. |
| Other connectors | CURSOR EVI documents a script that calls an ene't grid-charge service and links a swagger UI. On 5 November 2026 that UI did not return the specification without authentication. It is not an MCP server. |
ene't GmbH (DE). Energy suppliers that price electricity and gas in Germany. ene't's homepage, read on 5 November 2026, says more than 600 companies in the energy-supply industry are regular customers of ene't GmbH. That figure is the company, not a Navigator-only count.
Why ene't Navigator is hard for agents
01 · Host
Calls go to ws.enet-navigator.de. The connector runs in the customer's network and uses the customer's machine account. Navigator is not a database on a server in the customer's rack.
02 · Docs
OpenAPI for location properties and peak-load windows was read on 5 November 2026. The grid-charge, market-partner and price-sheet URLs returned HTTP 200 with an empty body. Those tools do not name a path.
03 · Licence
The username identifies the machine account. The licence on that account decides which packages answer. HTTP 403 means the licence does not include the webservice that was called.
04 · Writes
The peak-load specification includes POST /strom. The BO4E repository specification includes POST and DELETE. Those methods stay off the manifest. The connector does not publish a price sheet or change a licence.
One interface per row
01
REST/JSON. Documentation is public. OpenAPI read on 5 November 2026: GET /standorteigenschaften on ws.enet-navigator.de/standorteigenschaften, for an address and a date
02
REST/JSON. Documentation is public. OpenAPI read the same day: GET /strom and GET /strom/codenummer on ws.enet-navigator.de/hochlastzeitfenster; POST is in the file and stays off the manifest
03
REST/JSON. Documentation is public. the catalog describes BO Fremdkosten for an address and a period; the linked OpenAPI URL returned an empty body on 5 November 2026, so no path is named
04
REST/JSON. Documentation is public. OpenAPI read the same day includes GET, POST and DELETE; only a refusal of the writes is in scope here, not a tool
ene't Navigator holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the system is KISTERS BelVis or VIVAVIS IDSpecto, use that connector. Navigator is ene't's hosted market-data API, not a portfolio or a meter-data system on the customer's server. An ene't MCP server was not found on 5 November 2026. If one appears, this page is the read-only restriction, not a second writer.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your ene't Navigator owners and checks every backend against your release and licence. Week two tests whether a person's own ene't Navigator permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named ene't Navigator administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not one that was named on the Navigator pages read on 5 November 2026. A search that day, and a public GitHub repository search for an ene't Navigator MCP server, did not return one from ene't.
Location properties for an address, including the electricity control zone and balancing area and the gas market area, from GET /standorteigenschaften. Peak-load windows, switching times and the network operator from GET /strom. Grid fees, metering costs and levies are described on the electricity grid-charge package. That OpenAPI body was empty, so the path is confirmed in the blueprint.
No. A company admin creates the machine account and assigns a licence that selects the webservices it may call. ene't documents HTTP 403 when the licence does not cover the webservice, and HTTP 401 when the username or password is wrong.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, which packages the machine account may call, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your ene't Navigator administrator in the room if you like.