Original research · Utilities

E.ON.

Last measured · 22 May 2026 Wave · Q2-2026-W3 Tier · proprietary Confidence · C
Brand
E.ON SE
Agent success

On the unbranded question the comparison portals and the city utility capture the query.

Bottleneck Multi-axis
Weak on more than one axis at once.
3.7 /10
Agent Success Score
AI Visibility 26 / 100

Found & recommended by AI agents

AI Usability 35 / 100

Search-class agents touched the close in some runs; the full agent-fleet access profile lands in a later wave.

Coverage · 1 of 6 lanes measured Commerce lane · Wave Q2-2026-W3
Commerce 3.7
Talent
After-sales
Procurement
Investor
Press

This page measures the commerce lane: can an agent find E.ON, and once it arrives, transact. Talent, after-sales, procurement, investor and press lanes run on different surfaces and are not yet measured.

Your brand isn't measured yet

What does an AI agent do with your website?

The same measurement as E.ON, free for your domain. Five agent classes, one real task, your score in 48 hours.

Free · no card · 48h

The test

Portals own the unbranded query. The surface lets only the strongest agents through.

We asked five kinds of AI agent to reach a switch-ready state for an E.ON electricity tariff (3,500 kWh, postcode 80331) on eon.de. A coding agent read the €975.23 Strom Basistarif. A plain HTTP fetch was blocked at the door by a Cloudflare WAF. A standard browser agent could not target the postcode combobox in any of three runs. The autonomous agent found a different path, the Anbieterwechsel flow, and reached the contract form (step 2 of 3, E.ON ÖkoStrom Pro Extra 24, new-customer bonus €287) without authentication, by operating the postcode field directly. The provider switch is fully initiable; the calculator is the wall.

One label, many breeds. From a plain reader to an autonomous operator, the kinds behind ChatGPT, Perplexity, and Claude Code:

Plain reader reads your raw page text, no browser Blocked
Search assistant finds you through search Not yet run
Coding agent a script hitting your site Succeeded
Computer-use agent clicks and types like a person Blocked
Autonomous operator runs the whole task unattended Succeeded

Blocked somewhere on the path: Plain reader, Computer-use agent. A customer whose assistant runs on one of those breeds never finishes the task.

Scope. This is one tariff in one postcode. E.ON spans electricity, gas, solar, heat pumps, and EV charging, each with its own calculator and switching flow.

Commerce lane

Found, and able to transact?

Two questions, measured separately. A brand can be recommended and still un-buyable, or perfectly buyable and never found.

AI Visibility

When someone asks an agent to switch to a tariff, does it route to E.ON?

26 / 100

E.ON comes up about a quarter of the time. The rest of the time, an agent recommends an alternative first.

Discoverability · 18-datapoint audit
AI Usability

Once an agent is on E.ON's site, can it complete the switch?

35 / 100

Search-class agents surface contract-form-ready in some runs; the full agent-fleet access profile lands in a later wave.

Evidence · 70 / 100 A measure of how provable and consistent the result is, grounded in cross-method ground-truth agreement (the methods that ran returned the same price), not a separate measured run. A confidence layer on the two scores above, not a third sales axis.

What's next

What this means for E.ON.

Diagnosis

On product discovery, E.ON is not failing to exist; it is failing to be the answer. The unbranded energy question routes to the city utility and the comparison portals, and the surface that would convert a found customer blocks the plain reader and the standard browser. E.ON is found late and completed by few.

What changes the outcome

Make the surface answer the unbranded question and admit every agent class. Agent-readable tariff and switching surfaces a plain fetch and a standard browser can complete, not only the most capable scripted agent, and citeable evidence the answer engines can name directly instead of routing to a portal.

What proof looks like

The proof is not a faster calculator. It is agents of every class completing the switch on E.ON's own surface, and the unbranded question naming E.ON, re-measured each wave.

Audit · €1,900

Commission an audit.

Where the BrandScore opens the question, an audit closes it. An interpretive engagement on your full surface, scored under the same methodology.

Get the audit
Founding · €4,500

Found with us.

Strategic partnership for brands building agent success as a long-term capability, not a one-off engagement.

Apply
Snapshot

Audit an adjacent property.

The BrandScore covers the primary domain. Get the same methodology applied to an adjacent property: a country site, a sub-brand, a category beyond the DAX-40 slate.

Get a Snapshot

This is E.ON. What about your brand?

You just saw how an AI agent treats a DAX 40 brand.

The same measurement runs free against your domain: five agent classes, one real buying task, your Agent Success Score in 48 hours, in the exact format of this page.

Measured, not guessed. Real agents against your real site, no questionnaire.
Publicly comparable. Your score in the same grid as the measured DAX 40 brands.
Next wave closing. Start now to be in the next index round.

Free · no card · 48h

Channel position

Energy comparison sites capture 56% of tariff demand before E.ON.

Across the 18 Gate-1 responses, 56% routed the Munich electricity question through a comparison portal (Verivox in 6, Check24 in 5, Stromauskunft in 3); eon.de appeared directly in only 3. The capture is heaviest on the unbranded informational query, where 5 of 6 responses sent the user to a portal. The comparison portals own the energy-switching question before eon.de is reached. (The Munich city utility also surfaces unbranded, but as a competitor on discovery, not as a displacing channel.)

44% direct
56% via intermediary

Intermediaries Verivox · Check24 · Stromauskunft

Frozen task slate

Hyperize-selected tasks.

One task from the public sector grid. Task list is frozen before each wave runs.

E.ON Strom Basistarif (Anbieterwechsel)

Close state
contract-form-ready
Bottleneck
Coding agent reads the €975.23 tariff; a plain fetch is WAF-blocked and a standard browser cannot operate the postcode field. Only the autonomous agent, by operating the postcode field directly, reaches the contract form. Unbranded discovery routes to portals and the city utility.

Fairness note

Wave 3 (a fleet wave Telecom & Utilities). Single measured task (Strom Basistarif, 3.500 kWh, PLZ 80331, contract_form_ready close state via Anbieterwechsel). AI Visibility 26.28 (18/18 valid datapoints across 3 providers, unbranded informational); AI Usability derived from the a fleet wave access profile. Channel split grounded via channel-derive.py (intermediary in 10/18 Gate-1 responses). Confidence C, single task; Fairness Review pending the sector fairness grid.

Methodology

How the score was produced.

Discoverability is audit-pipeline-derived. 3-provider sample (openai, perplexity, anthropic), 3 query variants per task, 2 runs per variant · 18 valid datapoints scored against a five-state handoff cascade. [S1]

AI Usability is derived from the access-profile above (usability-derivation/v1): how far the best agent reached (close state) modulated by how many agent classes succeeded. The per-class profile is the truth; the score is a reproducible summary of it, not a separate rating. Fleet phases (HTTP / Coding / Browser / ACT) produce the profile. [S2]

Formula

Agent Success Score = (AI Visibility × 0.20) + (AI Usability × 0.70) + (Evidence × 0.10)

On a 0–100 scale, displayed 0–10. AI Usability bundles the agent's reach + completion; AI Visibility is audit-derived discoverability. Weighting is public; the per-prompt derivation is not.

Measurement scope

Confidence C · one measured task on a 3-provider track (openai, perplexity, anthropic). Confidence promotes to B with a second task plus a fourth provider on the next wave.

History

Measurement timeline.

Each wave appends; nothing overwrites. Frozen Wave Rule.

  1. Entry · 01

    22 May 2026

    Wave · Protocol

    WAVE-Q2-2026-W3

    ars-methodology/v1.1

    First v3 measurement. AI Visibility 26.28 (18/18 valid datapoints, 3 providers, DE, unbranded informational). AI Usability derived from a fleet wave: coding agent read the tariff, plain fetch WAF-blocked, standard browser 0/3 on the postcode combobox, autonomous agent reached the contract form by operating the postcode field directly. Unbranded discovery routed to SWM + Verivox/Check24. Confidence C, single task.

Sources

Evidence and provenance.

Public methodology references and internal evidence pointers behind every claim above.

  1. [S1]

    Gate-1 audit run · E.ON Wave Q2 2026

    Accessed · 22 May 2026

    Internal · Hyperize evidence

    • · AI Visibility score (26.28, 18/18 valid datapoints across 3 providers, unbranded informational)
    • · unbranded discovery routing to SWM + Verivox/Check24 (channel read)
  2. [S2]

    Hyperize fleet · a fleet wave Telecom & Utilities (access profile)

    Accessed · 22 May 2026

    Internal · Hyperize evidence

    • · how each kind of agent fared (text WAF-blocked, code success, browser 0/3, act by operating the postcode field directly)
    • · the close state reached (contract_form_ready, Anbieterwechsel, no login)
    • · the tested product (Strom Basistarif €975.23/yr, 3.500 kWh, PLZ 80331)
  3. Accessed · 22 May 2026

    Public · hyperize.ai

    • · fairness declaration
    • · Third-Party Interception framing
Last updated · 22 May 2026 Next review · 30 Sept 2026 Wave · Q2-2026-W3 Tier · proprietary Confidence · C Index score · 3.7/10 Machine-readable record

Editorial coverage

The DAX 40 Agent Success Index is a point-in-time snapshot of the agent-success of public digital touchpoints. Results are not statements about product quality, company performance, service quality, or the legal obligations of the brands named. Brand names and logos remain the property of their respective owners and are used solely for identification and reporting purposes in the context of editorial coverage (§ 23 MarkenG, Art. 5 GG).

Brands wishing to respond, engage, or correct a factual error may contact hello@hyperize.ai. Responses received are published in full alongside the findings. Full methodology and editorial-coverage notice: coverage statement.