Sentry

PASS consensus from 3 PASS.

Four legacy Browser guide URLs failed, but the current JavaScript page documents installation, initialization, testing, and issue viewing. One page carries prerequisites, install, Sentry.init with a DSN, and a throwing-button verification step, so a zero-to-first-error path is complete without leaving it. The JavaScript SDK page documents a complete zero-to-first-error path: install via npm, initialize with a DSN, then verify with a button that throws an error and check the Issues page.

FAIL consensus from 1 PARTIAL, 2 FAIL.

The API page gives headers but no numeric endpoint limits; pricing gives paid baselines but omits the Developer plan quota. The API rate limit page names no requests-per-second or concurrency number for any endpoint, and the quota pages state no per-plan event allowance, deferring instead to the off-docs sentry.io/pricing/ page. Plan quotas are exact (50k errors, 5GB logs, 5M spans per paid plan) and consistent across the pricing and quota pages, but the API rate limits page gives no exact numeric limits for any endpoint, just says each has its own window and maximum.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The obsolete miscellaneous page failed; current Usage and quota pages identify causes and require cross-referencing for cause-specific recovery. The same page names both causes of a 429 (exceeding the org quota and exceeding a per-key project rate limit), the Retry-After header, the instruction not to retry, and the increase-quota and filtering routes to a fix. The docs name two causes (quota exceeded, rate limit hit) and give a partial recovery path (increase quota, drop events until Retry-After expires), but the recovery actions are split across pages and a single complete step-by-step correction from recognizing a 429 to resolving it is not presented in one place.

PASS consensus from 3 PASS.

The integration guide covers creation, endpoint configuration, event payloads, delivery headers, response timing, and HMAC-SHA256 verification code. Creation under Settings > Developer Settings with a webhook URL, the full header set, the resource and action payload shape, and a runnable HMAC-SHA256 verification snippet are all documented across two linked pages. The integration platform docs tell the developer to create an integration at Settings > Developer Settings, specify the webhook URL, then the webhooks page documents the Sentry-Hook-Signature header and provides a complete code snippet to verify it with HMAC-SHA256.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The official package and API agree, but the capture example uses <sdk-package-name> and depends on setup from another page. The captureException example is correct and matches the Sentry.captureException form used elsewhere, but its import line ships an unsubstituted build token instead of a package name, and that page never states the package, so the name has to be cross-referenced from the getting-started page. The official @sentry/browser package is identified on the JavaScript platform page, and the usage page provides a complete minimal working example (import, try-catch, Sentry.captureException) that matches the Sentry.init API form shown on the setup page.