Stream

PASS consensus from 2 PASS, 1 PARTIAL.

The introduction watches channelByMembers but sends through undefined channel, so the final call requires a variable-name inference. One page carries the whole path (getInstance, connectUser, client.channel, watch, sendMessage), but its channel snippet binds channelById and channelByMembers while the message snippet calls channel.sendMessage on an undefined channel variable. The React getting-started page gives a complete linear path: install packages, init client via singleton pattern, connect user, create channel with client.channel(), watch with channel.watch(), and send a message with channel.sendMessage(), all in one page with no gaps.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

Both limit pages agree on Connect 10,000, Send Message 1,000, and 60 user requests per endpoint and platform. Connect is 10,000/min and Send Message is 1,000/min per platform, but the per-user 60/min cap is scoped two different ways in the docs, so the counting scope is not consistent. The platform rate-limits page clearly documents Connect at 10,000/min and the 60 req/min per-user cap with counting scopes (App-level per endpoint+platform; User-level per user per endpoint per platform). However, Chat-specific endpoint limits such as Send Message (1,000/min) and Get-or-Create Channel (10,000/min) are in the Chat-specific rate-limits page which is client-side rendered, so the table cannot be extracted via readable fetch. An agent must use the getRateLimits API or cross-reference the platform summary.

PASS consensus from 3 PASS.

The error reference gives both causes and shows the server-side created_by_id correction for code 4. The page names both causes, the three calls that trigger it (channel.watch, channel.create, channel.query), and gives runnable server-side fix code that passes created_by_id. The API Error Codes page has a dedicated 'GetOrCreateChannel failed' subsection that identifies the error, gives stream code 4, explains both causes (watching a non-existent channel; missing created_by_id on server-side creation), and provides code showing the fix: pass created_by_id in the channel data object when creating server-side.

PASS consensus from 3 PASS.

The platform guide covers subscription, raw-body verification, deduplication, and exact retries; the Chat events page provides the JSON payload. Configuration via event_hooks, the X-Signature HMAC header, the raw-body requirement, the message.new JSON payload on the chat events page, and an exact retry table (5 attempts, 6s per attempt, 15s total) are all documented. The webhooks documentation covers the complete lifecycle: configuring event_hooks with message.new via updateAppSettings, handler requirements (POST/JSON/2xx/idempotent/HTTPS), signature verification via verifyAndParseWebhook (or manual HMAC-SHA256), retry behavior (5 attempts, 6s timeout, 15s total), deduplication via X-Webhook-Id, payload compression, and even debugging with ngrok.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The tutorial renders one channel with a connected user, but it conflicts with the introduction's stylesheet import path. The minimal example connects a user with useCreateChatClient and renders a channel, but the two React entry points disagree on the install command and on the stylesheet path, so the setup step needs reconciling before the example runs. The React SDK docs provide a clear end-to-end path: installation (npm install stream-chat stream-chat-react), CSS import, client init, user connection, channel creation, and the minimal UI render of Chat > Channel > MessageList + MessageComposer. The Chat and Channel component pages both document the same minimal rendering pattern with code examples.