Mapbox

PASS consensus from 2 PASS, 1 PARTIAL.

The v6 curl works, but token management still shows v5, and the access-token getting-started page loads only an empty shell. The Geocoding API page gives a copy-paste curl example for forward geocoding, and three separate pages agree that a ready-made default public token is waiting in the Developer Console, so no token creation is required for the first call. All required parameters are documented on the same page; the access-token glossary provides an immediately executable URL.

PASS consensus from 2 PASS, 1 PARTIAL.

The pages consistently state 1,000 requests per minute, 100,000 free monthly requests, per-1,000 pricing, and autocomplete and batch counting. The 1000 requests-per-minute rate limit and the request-counting rules for autocomplete and batch are stated clearly on the docs page, but the free tier of 100,000 monthly requests and the $0.75 per 1,000 unit price live only on www.mapbox.com/pricing behind a collapsed accordion, and the docs never state which billing product the permanent=true parameter bills against. Rate limit scope (per access token), value (1000/min), pricing unit (per request), free tier (100k/month), and counting rules (autocomplete keystrokes, batch sub-queries) all documented; values are consistent across pages.

PASS consensus from 2 PASS, 1 PARTIAL.

The API index could not be extracted, but the guide documents per-token scope, reset timing, and sales escalation after 429. The Geocoding API page names the 429 and the 1000 per minute default but offers no Retry-After, no backoff guidance, and no link to the X-Rate-Limit-Reset header documented on the separate API guides page, and the two pages describe the limit scope differently. Limit scope (per access token) is identified; response code, headers for recovery timing, and escalation path are all documented.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The guides cover least-privilege scopes, URL rules, 401, and 403, but troubleshooting also recommends all public scopes. URL restrictions and the 401 and 403 diagnosis paths are complete and excellent, but least-privilege scoping for geocoding is undocumented: the default token cannot be URL-restricted, the public scopes table lists only styles:tiles, styles:read, fonts:read, and datasets:read, and the Geocoding API page names no required scope anywhere. Token creation, scope assignment, URL restrictions, and 401/403 diagnosis are fully documented on both the management guide and the troubleshooting page.

PASS consensus from 2 PASS, 1 PARTIAL.

The guide covers the task, but its JavaScript block wraps code in <script> and points to the discouraged default token. The npm guide, the CDN guide, and the examples gallery all pass the token as the accessToken option on the mapboxgl.Map constructor rather than the older mapboxgl.accessToken global, and the npm guide adds a troubleshooting checklist covering the token and the container dimensions. npm installation, import, token configuration, and map rendering are clearly documented and consistent with the scoped public-token guidance on the security page.