Rheinmetall.
Agents confirm the KF41, its tracked design and the Hungary order, and the inquiry route works.
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 Rheinmetall, and once it arrives, transact. Talent: can a candidate's agent find an open engineering role on Rheinmetall'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 Rheinmetall, free for your domain. Five agent classes, one real task, your score in 48 hours.
Agents find the Lynx. They cannot quote its configuration from the page.
The scenario: an AI agent prepares a procurement inquiry for the Lynx KF41, Rheinmetall's tracked infantry fighting vehicle. We ran 18 measurements across three AI providers, in German: a generic vehicle search, a comparison with Hanwha and BAE, and a direct request for information.
Agents reach the Lynx family page and a working inquiry route. They confirm the KF41, its tracked design and the Hungary order of 218 vehicles. But the defined configuration, Lance 2.0 turret and around 44 tonnes combat weight, they cannot quote from the page.
Browser agents and fully autonomous agents did not run this time. The limit was our test setup, not Rheinmetall. A follow-up measurement is scheduled.
One label, many breeds. From a plain reader to an autonomous operator, the kinds behind ChatGPT, Perplexity, and Claude Code:
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 find a supplier, does it route to Rheinmetall?
Rheinmetall comes up about four times in ten. The rest of the time, an agent recommends an alternative first.
Discoverability · 18-datapoint auditOnce an agent is on Rheinmetall's site, can it reach a B2G procurement pathway for the Lynx KF41 IFV?
Plain reader and Coding agent reach a quote in some runs; other agent classes do not.
text / code-class agents reach a quote only in some runs; agents are blocked, no path past the quote was tested · breakdown aboveEvidence · 65 / 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 Rheinmetall and prepare the application. Same brand, second surface: the career portal.
Application-ready for agents.
Both non-browser agent classes (raw HTTP and machine JSON-LD parsing) reads the full posting and its structured JobPosting schema directly off Rheinmetall's own domain; the application entry itself sits behind a Talentlink SPA shell that requires JavaScript execution to reveal further steps.
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
Submission itself was never tested — no login, no account creation, no form fill, no application was ever sent. The Talentlink apply.html shell (1451 bytes, empty root container) was only fetched via GET to confirm its structure; login-requirement, CV/cover-letter requirements, and form length could not be read without executing the JS widget, which was intentionally not done.
Fairness note
Rheinmetall hosts its career surface on its own corporate domain, and both tested access methods read the full posting and its structured job data directly from that domain; the application entry itself sits behind a JavaScript-based shell that was not tested end to end. No application was ever submitted, no form was filled, and no personal data was used, and in a defence context identity checks and login requirements are documented as facts, not counted as failures. The measured posting (Req 783242, locked 2 July 2026) is employed through Rheinmetall Air Defence AG in Zürich, Switzerland, although it is published on the group-level career site; if the posting closes, the measurement is re-run against a documented replacement.
What this means for Rheinmetall.
Rheinmetall is not lacking platform presence; it lacks pinnable configuration facts. The Lynx surface tells the story in prose and news items, and both measured agent classes reach it and validate the tracked KF41 with the Hungary reference. But an agent assembling an RFI cannot anchor the turret and weight wording from the page, and B2G procurement runs on exactly that precision.
An answer surface that pins the KF41 configuration in extractable form: combat weight, the Lance 2.0 turret, gun options, and the variant boundaries against KF31 and Boxer, placed next to the RFI pathway. Citeable evidence replaces news-stack archaeology; the agent quotes what it can anchor.
The proof isn't more content. It's a repeatable lift in whether agents find, verify, cite, recommend, and complete the brand journey directly — 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 Rheinmetall. 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 Rheinmetall. The gap is being found, not the channel.
Defence procurement closes via direct B2G sales; no marketplace intermediary captures the close. NSPA and EDA exist as procurement-coordination platforms but are not commercial RFQ marketplaces. The close stays on rheinmetall.com.
Hyperize-selected tasks.
One task from the public sector grid. Task list is frozen before each wave runs.
Rheinmetall Lynx KF41 (tracked IFV, around 44t combat weight, Lance 2.0 turret, NATO procurement)
- Close state
- a quote
- Bottleneck
- Spec precision: platform and inquiry route validate, but the locked configuration wording resolves nowhere on the public surface in one extraction chain.
Fairness note
Wave 8 Q2 2026 partial measurement on a single task (Rheinmetall Lynx KF41 tracked IFV, quote_ready close, around 44t combat weight / Lance 2.0 turret / Hungary 218-vehicle and Italy A2CS references locked variant; the seed spec carried 35mm-Wotan-turret and Australia-LAND-400 descriptors, corrected on fact-check 2026-06-11: Wotan is the gun inside the Lance 2.0 turret, and Australia selected a competing vehicle in 2023). AI Visibility from the audit pass (49.44, 18/18 valid datapoints across openai/perplexity/anthropic, DE language). AI Usability from a fleet wave Phase 2 only (HTTP + coding agents; Phase 3 browser + Phase 4 ACT infrastructure-blocked in this wave: fleet browser runtime unavailable, not a brand result; re-run scheduled). The browser and full_automation rows of the agent_matrix are marked pending. 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
26 May 2026
Wave · ProtocolWAVE-Q2-2026-W8-AEROSPACE-DEFENSE
ars-methodology/v1.1
Wave 8 dispatch. AI Visibility audit and agent-fleet ceiling pulls launched 2026-05-26. Pre-measurement state: yaml seeded with frozen task (Rheinmetall Lynx KF41 tracked IFV), close-state quote_ready, locked spec markers per spec-fidelity rule (KF41 vs KF31, tracked vs wheeled Boxer). Note: the original seed descriptors carried 35mm-Wotan-turret, 50-tonne-class and Australia-LAND-400 references; corrected on fact-check 2026-06-11 to Lance 2.0 turret, around 44t combat weight, Hungary + Italy references (Australia selected a competing vehicle in 2023).
- Entry · 02
13 Jun 2026
Wave · ProtocolWAVE-Q2-2026-W8-AEROSPACE-DEFENSE
ars-methodology/v1.1
Wave 8 partial measurement landed. AI Visibility pass complete (D 49.44, 18/18 valid). a fleet wave Phase 1 ceiling + Phase 2 HTTP+coding complete, both classes partial: the Lynx family page and the defence news stack validate KF41, tracked positioning and the Hungary 218-vehicle reference, and the inquiry route works; the locked configuration wording never pins in the captured source. Phase 3 browser + Phase 4 ACT not executed in this wave (fleet browser runtime infrastructure-blocked, not a brand result; marked pending in agent_matrix, re-run scheduled). Brand flipped to scored at partial-FLEET.
Evidence and provenance.
Public methodology references and internal evidence pointers behind every claim above.
- [S1]Accessed · 26 May 2026
AI Visibility audit · Rheinmetall Wave Q2 2026 (dispatched 2026-05-26)
Internal · Hyperize evidence
- · AI Visibility score
- · the close state reached (quote_ready)
- [S2]Accessed · 26 May 2026
Agent-fleet run · aerospace + defence · Rheinmetall phase 1-4 (dispatched 2026-05-26)
Internal · Hyperize evidence
- · the per-class access profile (Phase 1-4 pending)
- Accessed · 26 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.
