{"slug": "extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page", "title": "Extract API fabricates a nonexistent incident entry on a status page (reproducible?)", "summary": "Kagi's Extract API, called through the `kagi_extract` MCP tool on `https://contabo-status.com/`, returned a fabricated security-incident entry that appears nowhere in the page's raw HTML, its RSS feed, or any other independent fetch of the same URL, according to a reproducible bug report. The fabricated entry, identical across 3 separate calls, claims a \"26.10.2026 01:30 pm (UTC+1) Security Incident – Investigating\" involving unauthorized access to systems hosting VDS and advises rotating SSH keys, passwords, and API tokens. The reporter asks Kagi to investigate whether Extract's content-cleaning pipeline includes an LLM post-processing step rather than the documented deterministic HTML-to-Markdown conversion, since the failure mode resembles LLM hallucination rather than a parsing bug.", "body_md": "Calling the Extract API (via the `kagi_extract` MCP tool) on `https://contabo-status.com/` consistently returns a fabricated incident entry that does not exist in the page's raw HTML, its RSS feed, or any other independent fetch of the same URL.\n\nFabricated entry returned by Extract (verbatim, identical across 3 separate calls):\n\n26.10.2026 01:30 pm (UTC+1) Security Incident – Investigating\n\nWe detected unauthorized access to systems hosting VDS. Affected systems are \n\n  isolated and under investigation.\n\nAffected customers will be notified directly by email. As a precaution, we \n\n  recommend rotating SSH keys, passwords, and API tokens used on your VDS.\n\nWe only communicate via this page - Next update: 15:00 CET\n\nPlease investigate whether Extract's content-cleaning pipeline includes an LLM post-processing step (as opposed to deterministic HTML→Markdown conversion as documented), since the failure mode looks like classic LLM hallucination rather than a parsing bug.", "url": "https://wpnews.pro/news/extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page", "canonical_source": "https://kagifeedback.org/d/11769-extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page-reproducible/1", "published_at": "2026-10-26 21:31:59+00:00", "updated_at": "2026-10-26 21:43:18.279846+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "large-language-models"], "entities": ["Kagi", "Extract API", "kagi_extract", "Contabo", "VDS"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page", "markdown": "https://wpnews.pro/news/extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page.md", "text": "https://wpnews.pro/news/extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page.txt", "jsonld": "https://wpnews.pro/news/extract-api-fabricates-a-nonexistent-incident-entry-on-a-status-page.jsonld"}}