Ably

PASS consensus from 3 PASS.

The guide waits for connection, subscribes once, publishes after subscribing, and logs the received message. One page carries the whole path in order: CDN script tag, new Ably.Realtime({key, clientId}), await connection.once('connected'), channels.get, await channel.subscribe with a logging callback, then await channel.publish, so receipt is confirmed by the subscriber the guide already registered. Four-step guide with CDN include, client instantiation, channel subscribe, and channel publish in a linear progression with no branching or ambiguity.

PASS consensus from 3 PASS.

In task order, Free lists 6,000,000, 200, 500/s, and 50/s; Standard lists Unlimited, 10,000, 2,500/s, and 50/s. All four figures sit in one page with inline definitions per row (Free/Standard: 6,000,000 vs Unlimited monthly messages, 200 vs 10,000 concurrent connections, 500 vs 2,500 account message rate, 50 vs 50 per-channel publish rate) and the public pricing page repeats the same numbers. All four requested metrics are tabulated on the limits page and agree with the Free and Standard individual plan pages.

PARTIAL consensus from 3 PARTIAL.

The page gives complete recovery guidance; an older FAQ contradicts its scope, and a legacy markdown URL returned 404. CONTRADICTION: the docs page scopes 42910 to a system-wide protection that is not account-specific, while Ably's own help site says 42910 means "you have hit a hard limit on your account" and illustrates it with metric = channel.maxRate, which the current docs assign to error 42913; the docs page also gives no numeric backoff, only "increasing the delay if it is rejected again". Error 42910 is not listed in the official error codes documentation at /docs/platform/errors/codes; it is only documented in the separate FAQ knowledge base, requiring the agent to leave the primary docs to find recovery details.

PASS consensus from 2 PASS, 1 PARTIAL.

Creation, batching, signing, retry, and ordering are documented, but the decode prose says fromEncoded while its code calls fromEncodedArray. Every part is documented without guessing: generic.md gives the dashboard rule steps and the channel.message event type plus the Sign with key and Request Mode settings, and webhooks.md gives the batched payload JSON, the five HMAC-SHA256 signature steps keyed off X-Ably-Key, retries (single: 4s then 20s; batched: delay = delay * sqrt(2) capped at 60s), and ordering (batched preserves order for the same publisher on the same channel, single request cannot). One page covers rule creation via dashboard or API, batched payload structure, signature verification with explicit steps, exponential-backoff retry with formula and example delays, and ordering guarantees per publisher-channel pair.

PASS consensus from 3 PASS.

The CDN guide uses Realtime with awaited subscribe and publish forms that match the current JavaScript reference. The getting-started guide, the pub-sub concept page, the connect page, and the API reference all agree on the same promise-based v2 surface (new Ably.Realtime, channels.get, await channel.subscribe, await channel.publish), though the docs pin only the major version via cdn.ably.com/lib/ably.min-2.js and never state an exact SDK version number. The getting-started page shows the CDN include, client construction, subscribe, and publish in sequence, matching the current SDK 2.x API reference.