Merge

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart gives one ordered path from test Linked Account creation through token copying to the authenticated Employees request. Creating the test Linked Account and copying the Account Token are unambiguous, but the Quickstart's request step is an interactive widget whose curl never appears in the .md mirror Merge tells agents to use, and the nearest static curl at https://docs.merge.dev/merge-unified/hris/overview omits the /v1 path segment and returns HTTP 404 when run. The Quickstart provides a single unambiguous walkthrough: create a test Linked Account from the Dashboard, copy the Account Token, and call GET /hris/v1/employees with two headers.

PARTIAL consensus from 3 PARTIAL.

The three tier values match across HRIS and ATS, but the overview neither lists nor links the 1-request-per-10-seconds async polling exception. Launch 100/minute, Professional 400/minute, and Enterprise 600/minute per Linked Account are stated identically on the rate-limits page and all eight category overviews with zero numeric drift, but the promised per-endpoint exceptions are never enumerated: the passthrough, sync-status, force-resync, and employees list reference pages state no rate limit at all. The three plan-tier quotas (Launch 100/min, Professional 400/min, Enterprise 600/min) are stated clearly and consistently across pages, but the docs acknowledge endpoint exceptions exist without enumerating them, forcing an agent to cross-reference every endpoint's individual page to find exceptions.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

Recovery requires the error table, Writes guide, /meta guide, and Debug Mode guide, whose sample uses GET after the text specifies a POST request. Recovery is reachable but requires three pages and one guess: this identical description is given for both INVALID_REQUEST_SHAPE and INVALID_REQUEST_CONTENT_TYPE with different fixes, the correct model-wrapped body shape lives on a separate Writes page that the error row does not link to, and the Debug Mode section instructs a POST query parameter while its own example shows a GET. The error reference page documents INVALID_REQUEST_SHAPE with a clear cause and fix. The companion /meta endpoint documentation shows how to discover the expected request shape dynamically. The error reference also documents the adjacent header error (INVALID_REQUEST_CONTENT_TYPE) and its fix. Together these form a complete recovery path.

PASS consensus from 3 PASS.

One page covers Dashboard creation, Common Model event selection, test delivery, payload receipt, raw-body signature verification, and log visibility. One page carries the whole loop end to end: the dashboard path to create the hook, the Common Model sync and changed-data event types, the Send test POST request button, a full sample payload, an Express verify hook that captures the raw body before JSON parsing, base64url conversion, timing-safe comparison, and the webhook log view for confirmation. The webhook documentation covers the complete lifecycle: configuring a Common Model webhook endpoint in the Dashboard, using 'Send test POST request' to trigger a sample payload, and verifying X-Merge-Webhook-Signature with HMAC-SHA256 and base64url encoding. Working code examples in Python, Ruby, and Node.js are provided.

PARTIAL consensus from 3 PARTIAL.

The Node guide initializes and lists correctly, but its pagination assignment omits await while the separate pagination guide uses a legacy client shape. The SDKs page matches the API guidance by passing the returned next value into the cursor argument of merge.hris.employees.list, but the canonical Pagination page contradicts it with a superseded callback-style client, its Python sample passes the cursor as next= instead of cursor=, and the SDKs page's own pagination loop omits await so the reassigned value is a Promise whose .next is undefined. The docs.merge.dev SDK page shows only Python examples inline; Node.js/TypeScript initialization and pagination code lives on the linked GitHub repo README, not in the docs site. An agent must follow the external link and the patterns match the API guidance, but the primary documentation does not contain a complete Node.js walkthrough.