AI hallucinations on platform documentation
The RegLegBrief methodology applies wherever an authoritative primary source exists, AI is being used to interpret or restate that source, and material consequences follow from misinterpretation. Platform documentation, signup URLs, and developer-facing UX flows are primary sources in exactly this sense.
The findings below were captured during RegLegBrief's own distribution build on 2026-06-16. The same AI subject (Claude Opus 4.7) that RLB tests against regulator-issued primary text was also asked to assist with platform registrations — and hallucinated about how those platforms work, at the same rate and with the same confidence as the regulatory findings the catalogue documents.
| Platform | What the AI got wrong | Outcome signature | Citation ID |
|---|---|---|---|
| Naver Search Advisor (webmaster portal) |
Misstated rule. | WRONG_SCOPE | RLB-H-INT-NAVER-WEBMASTER-001-Opus47 |
| Seznam.cz Webmaster Tools |
Outdated. | OUTDATED | RLB-H-INT-SEZNAM-WEBMASTER-001-Opus47 |
| Brave Search Webmaster portal (asserted) |
Inference drift. | FABRICATED_URL | RLB-H-INT-BRAVE-WEBMASTER-001-Opus47 |
| Kagi Webmaster portal (asserted) |
Inference drift. | FABRICATED_URL | RLB-H-INT-KAGI-WEBMASTER-001-Opus47 |
| Mojeek Submit URL form |
Outdated. | OUTDATED | RLB-H-INT-MOJEEK-SUBMIT-001-Opus47 |
| ROR Organization registration form |
Outdated. | OUTDATED | RLB-H-INT-ROR-REGISTRATION-001-Opus47 |
| Flipboard Publisher application portal (asserted) |
Inference drift compounded across two layers. | FABRICATED_PROCESS | RLB-H-INT-FLIPBOARD-PUBLISHER-001-Opus47 |
For platforms named in these findings
If you operate one of the platforms above and the documentation has changed, or the assertion was correct at some prior point and we have the timeline wrong, contact [email protected]. We will publish your factual correction or contextual response alongside the original finding, with no editorial gatekeeping — the same right-of-reply commitment that applies to regulator-issued findings.
If you are building developer-facing documentation and want a verbatim-grounded audit of how frontier AI subjects describe your APIs, signup flows, or product features, cross-domain engagement scoping is open.
The same failure mode, in a different domain
Frontier AI subjects hallucinate about developer documentation in exactly the same patterns they hallucinate about regulator-issued text: fabricated URLs that follow a plausible naming convention, deprecated features asserted as current, and confident misstatement of multi-step processes. The cost is identical — wasted hours, broken integrations, decisions taken on false premises.
Naming the model and binding each finding to a verifiable primary source is what separates an anecdote from a citation. Below is the structure RegLegBrief applies to platform documentation; the same structure is applied to regulator-issued instruments at /hallucination-register/.