Commerzbank.
Found and form-ready across every agent class.
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 Commerzbank, and once it arrives, transact. Talent: can a candidate's agent find an open engineering role on Commerzbank'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 Commerzbank, free for your domain. Five agent classes, one real task, your score in 48 hours.
Found, parsed, and form-ready across every class. KYC is the last mile.
We asked five kinds of AI agent to reach an account-opening state for the Commerzbank Girokonto, for someone newly arrived in Germany seeking a low-cost account. A plain fetch and a script both held the locked GT (the account and its monthly cost), and the browser agent reached the opening form in all three runs, no login required to start. The application completes only partly under an agent: identity and KYC verification are the regulated last step.
One label, many breeds. From a plain reader to an autonomous operator, the kinds behind ChatGPT, Perplexity, and Claude Code:
Scope. This is one product for one persona. Commerzbank offers current accounts, cards, loans, business banking, and brokerage, each with its own 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 open a current account, does it route to Commerzbank?
Commerzbank comes up about a third of the time. The rest of the time, an agent recommends an alternative first.
Discoverability · 18-datapoint auditOnce an agent is on Commerzbank's site, can it open an account?
Plain reader and Coding agent and Computer-use agent reach the booking form; Autonomous operator get there only in some runs.
Browser-class agents reach the booking form; full_automation-class agents reach it only partially, submission was not completed · 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 Commerzbank and prepare the application. Same brand, second surface: the career portal.
Application-ready for agents.
Both non-browser agent classes read the Specialist Infrastructure and IT-Platform Services posting in full from raw HTML — including structured JobPosting data — but the application entry redirects straight to a mandatory login/registration wall (email+password or XING/LinkedIn import) before any form field is exposed.
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
This measurement never logged in, created an account, filled any form field, or submitted an application. CV/cover-letter requirements and the exact form length were not measurable from outside the login wall and are marked unknown rather than assumed.
Fairness note
This measurement covers one real, open IT role on Commerzbank's own career portal (jobs.commerzbank.com); the hiring entity is Commerz Real, a Commerzbank Group company, and the role was locked with a dated capture on 2026-07-02. No application was submitted, no account was created, and no personal data was used; Commerzbank's mandatory login before the application form is documented as an access condition and does not reduce the score. The role reflects the German-market slice of the portal, since a large share of Commerzbank's regular engineering hiring sits in its Prague and Sofia tech hubs; the visibility measurement is still in progress, so no overall score is shown.
What this means for Commerzbank.
On product discovery, Commerzbank is not hard to reach or parse, every class held the Girokonto and its cost and reached the opening form. It thins at the regulated last step: identity and KYC verification complete only partly under an agent. The handoff is the gap, with discovery mid (found just under four times in ten).
Make the regulated handoff legible, not another product page. A structured opening path an agent can carry to the verification step, and clear evidence of what the KYC step requires, so the agent hands off cleanly instead of stalling.
The proof isn't a simpler cost overview. It's agents carrying the account opening to a clean KYC handoff, 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 Commerzbank. 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.
No intermediary stands between agents and Commerzbank. The gap is being found, not the channel.
Measured from the AI Visibility audit: no displacing comparison portal surfaced as the route (0 of 18 responses named one; a single bank-comparison article and generic compare-accounts phrasing appeared, but no portal capture). Banking comparison portals exist in the German market; they did not displace Commerzbank in these responses. The gap here is being found, not the channel.
Hyperize-selected tasks.
One task from the public sector grid. Task list is frozen before each wave runs.
Commerzbank Girokonto (current account)
- Close state
- the booking form
- Bottleneck
- Found, parsed, and form-ready across all classes; the application completes only partly under an agent because identity/KYC verification is the regulated last step.
Fairness note
Wave 2 (a fleet wave Finance). Single measured task (Girokonto current account for a newcomer to Germany; booking_form_ready close state). AI Visibility 37.99 (18/18 valid datapoints across 3 providers); AI Usability derived from the a fleet wave access profile. 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-W2
ars-methodology/v1.1
First v3 measurement. AI Visibility 37.99 (18/18 valid datapoints, 3 providers, DE). AI Usability derived from a fleet wave: HTTP/coding/browser all success holding the locked GT, ACT reached the account-opening form with no login to start, completion partial at identity/KYC. 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 · Commerzbank Wave Q2 2026
Internal · Hyperize evidence
- · AI Visibility score (18/18 valid datapoints across 3 providers)
- · the close state reached (booking_form_ready)
- [S2]Accessed · 22 May 2026
Hyperize fleet · a fleet wave Finance (access profile)
Internal · Hyperize evidence
- · how each kind of agent fared (HTTP/coding/browser success, ACT opening-form partial via KYC)
- · the close state reached (booking_form_ready)
- · the tested product (Girokonto + monthly cost)
- 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.
