Felt

PASS consensus from 3 PASS.

The quickstart links token creation and supplies a complete bearer-authenticated POST /maps request plus the expected map response. The Getting started page states the base URL https://felt.com/api/v2, names the token creation location as the Developers tab of the Workspace Settings page, gives the felt_pat_ token prefix, and shows a runnable curl, requests, and felt-python version of the same first call plus the expected response body. The getting-started page walks through API token creation (workspace Developers tab) followed by a curl/Python/Python-library POST to /api/v2/maps; the response JSON includes the map ID and URL, making the first-call path unambiguous.

SPLIT consensus from 1 PASS, 1 PARTIAL, 1 FAIL.

The guide states 300 requests per minute per IP, but gives no numeric plan threshold and references 429 inconsistently. One Rate limits section states both 429 conditions as a numbered pair: a named per-IP throttle with a concrete number, and a plan usage limit signalled by the x-api-limit-exceeded response header, with no competing numbers elsewhere in the corpus. A single coherent page documents both limits (300 req/min per-IP; plan-usage limits via x-api-limit-exceeded header), but every API-reference endpoint table labels 429 as 'Unprocessable Entity' (the 422 meaning), directly contradicting the errors page and creating ambiguity for an agent cross-referencing status-code tables.

PASS consensus from 2 PASS, 1 PARTIAL.

One page documents the response header, exponential backoff with jitter, batching for bulk work, and sales escalation. The page covers all four recovery moves , the disambiguating header, exponential backoff with jitter, a concrete batching alternative (upsert many annotations in one POST /elements call instead of one call per feature), and escalation to the Felt sales team , although an unauthenticated request I sent to https://felt.com/api/v2/user returned 401 with no x-api-limit-exceeded header in the response, so an agent should treat the header as possibly absent rather than always present. The docs advise exponential backoff with jitter, mention the x-api-limit-exceeded header for distinguishing the two 429 causes, suggest batching (POST /elements instead of per-feature calls), and direct users to the sales team for plan escalations, but do not document any Retry-After header or give concrete backoff timing parameters.

PASS consensus from 3 PASS.

The webhook guide covers UI creation, the POST payload, raw-body verification code, retries, and an end-to-end receiving test. The page documents the full loop: webhook creation is stated as UI-only with no REST endpoints, the map:update payload is shown verbatim, delivery semantics are given (coalesced, at least once, 10 retries with exponential backoff, redirects not followed), and signature verification ships as working Python and Node functions using constant-time comparison plus the warning to compute the HMAC over the raw body rather than re-serialized JSON. The webhook page documents the full lifecycle: UI-based creation (workspace Developers tab), the map:update payload schema, retry behavior (10 retries, exponential backoff), and HMAC-SHA256 verification with complete Python and Node.js code examples.

PASS consensus from 3 PASS.

The install and embed example uses Felt.embed with the container, map ID, and promise return documented by the API reference. The example agrees exactly with the published SDK: @feltmaps/js-sdk 1.10.2 on npm declares embed(container: HTMLElement, mapId: string, options?: FeltEmbedOptions): Promise<FeltController>, the documented changelog top entry is also 1.10.2, and all six uiControls keys listed on the Embed options page (showLegend, cooperativeGestures, fullScreenButton, geolocation, zoomControls, scaleBar) match the shipped type declarations. The JS SDK page provides npm and CDN installation, a full embed example with a named container (requiring explicit height), and matches the current @feltmaps/js-sdk package; the Felt.embed() API signature in the example agrees with the embed-options page.