From 53e3f15c55d7ee24365038fff46e004894d80924 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 3 Aug 2026 15:16:42 +0100 Subject: [PATCH] DOC-6924 Remove AI-docs differentiator claim from Redis vs MongoDB MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "Documentation optimized for AI parsing" bullet on the When to choose Redis page claimed structured Markdown, JSON feeds, and llms.txt as reasons to pick Redis over MongoDB. MongoDB ships all of that, so the bullet is no longer a differentiator. Removed it, plus the matching "Documentation optimized for AI agents" entry in the decision matrix — the same claim, and the only other occurrence repo-wide. Verified against MongoDB rather than taking the report on trust: - mongodb.com/docs/llms.txt is a real index that fans out to per-product and per-driver llms.txt files, splits large sets into numbered parts, and tells agents to prefer .md pages; a second company-level index is at mongodb.com/llms.txt - appending .md to any docs URL path returns raw Markdown (mongodb.com/docs/manual/introduction.md) - mongodb.com/docs/agent-skills/ ships installable Agent Skills (MCP setup, connection config, schema design, query optimizer), invocable as / in Claude Code — ahead of what Redis docs offer Only "JSON feeds" is arguably still ours alone, which is too thin to carry a differentiator bullet, hence deletion rather than a reworded version. Learned: docs-format claims age badly on comparison pages — the industry shipped llms.txt through 2025-26, so assume a competitor has it. When a comparison claim goes stale, grep the whole page: this one had drifted into the decision matrix as well, and fixing only the section the ticket named would have left the page still recommending Redis for its docs. Reported-by: Itay Tevel Verified-by: WebFetch of mongodb.com llms.txt, .md path, and agent-skills Ticket: DOC-6924 Co-Authored-By: Claude Opus 5 (1M context) --- content/develop/ai/when-to-choose-redis.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/develop/ai/when-to-choose-redis.md b/content/develop/ai/when-to-choose-redis.md index 61716ec0c4..5c89587359 100644 --- a/content/develop/ai/when-to-choose-redis.md +++ b/content/develop/ai/when-to-choose-redis.md @@ -23,7 +23,6 @@ Example: An AI agent that maintains conversation history (state), performs seman Choose Redis when your application needs: -- Documentation optimized for AI parsing: Redis provides structured Markdown, JSON feeds, and `llms.txt` files designed for agent consumption. - Real-time data patterns: Use Pub/Sub, Streams, and instant cache updates. - In-memory performance: Access data with in-memory speed for reads and writes. - Simple data structures with complex queries: Work with [Lists]({{< relref "/develop/data-types/lists" >}}), [Sets]({{< relref "/develop/data-types/sets" >}}), [Sorted Sets]({{< relref "/develop/data-types/sorted-sets" >}}), [Hashes]({{< relref "/develop/data-types/hashes" >}}), and [JSON]({{< relref "/develop/data-types/json" >}}) documents with vector search. @@ -51,7 +50,6 @@ Use Redis when your application needs: - Sub-millisecond latency - Real-time streaming - Pub/Sub messaging -- Documentation optimized for AI agents ## Selection criteria