E.ON.
On the unbranded question the comparison portals and the city utility capture the query.
Found & recommended by AI agents
Can an agent use the surface to get the job done
This page measures two lanes. Commerce: can an agent find E.ON, and once it arrives, transact. Talent: can a candidate's agent find an open engineering role on E.ON's own career surface and prepare the application. 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.
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:
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.
Found, and able to transact?
Two questions, measured separately. A brand can be recommended and still un-buyable, or perfectly buyable and never found.
When someone asks an agent to switch to a tariff, does it route to E.ON?
E.ON comes up about a quarter of the time. The rest of the time, an agent recommends an alternative first.
Discoverability · 18-datapoint auditOnce an agent is on E.ON's site, can it complete the switch?
Coding agent and Autonomous operator reach contract-form-ready; the other agent classes do not.
Browser-class agents reach contract-form-ready; text / browser agents are blocked · breakdown aboveEvidence · 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.
The talent lane.
A candidate's agent, sent to find an open software-engineering role at E.ON and prepare the application. Same brand, second surface: the career portal.
Application-ready for agents.
Both non-browser agent classes -- a plain HTTP GET and a machine JSON-LD parse -- reads the full posting (title, requisition ID, locations, employment type, and core requirements) directly from server-rendered HTML on E.ON's own jobs.eon.com domain, and finds a login-optional "Quick application" entry point, with no browser rendering required for this particular, currently-open requisition.
Furthest close-state reached: application ready · frozen task locked 2026-07-02
The score above is provisional where a class shows untested: untested classes are excluded from the calculation, so the pending check can only confirm or raise the value, never silently lower it.
AI Visibility · in measurement — the audit run for this lane has not landed yet. No Talent-lane composite is shown until both axes are measured.
What this does not yet cover
The actual application submission was never attempted -- no login, no form fill, no file upload, no POST. This measures only reachability of the posting and the apply entry point, not whether the submission flow itself completes successfully. Note also that this result reflects one currently-open requisition; the Scout found that 8 of 9 other sampled req IDs on the same domain were already expired ("No Longer Available") thin SPA shells at curl-verification time, so this pass result is req-ID-specific, not a guarantee about every E.ON posting an agent might discover via search.
Fairness note
E.ON was measured on its own group-wide job board, jobs.eon.com, against a live SAP DevOps requisition in Essen, captured and locked on 2026-07-02; careers.eon.com is the same underlying system and was treated as an alias, not a separate surface. Two machine access methods, a plain HTTP request and a structured-data parse, read the full posting from server-rendered HTML and located the login-optional quick application entry; browser-based agents were not tested. No application was ever submitted and no personal data was used: the score reflects how reachable the posting and the apply entry are for automated tools, not the application process itself or E.ON's hiring decisions.
What this means for E.ON.
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.
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.
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.
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 auditFound with us.
Strategic partnership for brands building agent success as a long-term capability, not a one-off engagement.
ApplyAudit 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 SnapshotThis 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.
Energy comparison sites capture 56% of tariff demand before E.ON.
Across the 18 AI Visibility 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.)
Intermediaries Verivox · Check24 · Stromauskunft
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 AI Visibility responses). Confidence C, single task; Fairness Review pending the sector fairness grid.
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]
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.
Measurement timeline.
Each wave appends; nothing overwrites. Frozen Wave Rule.
- Entry · 01
22 May 2026
Wave · ProtocolWAVE-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.
Evidence and provenance.
Public methodology references and internal evidence pointers behind every claim above.
- [S1]Accessed · 22 May 2026
AI Visibility audit · E.ON Wave Q2 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)
- [S2]Accessed · 22 May 2026
Hyperize fleet · a fleet wave Telecom & Utilities (access profile)
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)
- Accessed · 22 May 2026
Public · hyperize.ai
- · fairness declaration
- · Third-Party Interception framing
Read the doctrine. Challenge the score. Extend the slate.
Task Selection.
The fairness doctrine behind the slate above. Five failure modes, six criteria, public before each wave.
Read ChallengeDisagree with this score.
Send evidence under public Fairness Review. Failed reviews are documented with the named failure mode.
Challenge ExtendSubmit your own task.
Open Surface Run · additive measurement. The Hyperize-selected slate stays frozen; your task gets the same methodology.
SubmitEditorial 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.
