# Mapbox docs: AI Agent Readiness Score 80.0% (B-) **80.0% · 64/80 · AI Agent Readiness Score · 24/30 reading points · 40/50 agent surface points** Mapbox received 9 PASS votes and passed 4 of five agent surface checks. The clearest finding came from the configure an access token task. - Tested: 2026-08-20 - Published: 2026-09-21 - Battery: v1 - Scoring: reading 30 pts · surface 50 pts - Docs: https://docs.mapbox.com/ Three AI models, GPT 5.6 Sol, Claude Opus 5, and DeepSeek v4 Flash, each read Mapbox’s public documentation independently and attempted five first-hour developer jobs: make the first geocoding request, find the exact limits, recover from a 429, configure an access token, use Mapbox GL JS. No accounts, API calls, or code execution were used. Every verdict came from public pages and every published quotation passed a live verification check. Preflight substitutions: T4: Scoped access-token authentication replaces webhooks. ## Freshness [How rechecks work](https://docsforagents.com/methodology/#freshness) - Category: [Geospatial & maps](https://docsforagents.com/grades/?category=geospatial) - Tested: 2026-08-20 - Quotes verified: 2026-08-20 - Surface rechecked: 2026-09-21 No change since the test. 5 of 5 quoted passages still appear on the live pages. ## Agent surface checks · 40/50 | Check | Verdict | Points | | --- | --- | --- | | llms.txt | PASS | 10 | | llms-full.txt | FAIL | 0 | | Markdown mirror | PASS | 10 | | MCP server | PASS | 10 | | Docs AI | PASS | 10 | ## The Reading Test · 24/30 | Task | GPT 5.6 Sol | Opus 5 | DeepSeek v4F | Consensus | | --- | --- | --- | --- | --- | | Make the first geocoding request | PARTIAL | PASS | PASS | PASS | | Find the exact limits | PASS | PARTIAL | PASS | PASS | | Recover from a 429 | PASS | PARTIAL | PASS | PASS | | Configure an access token | PARTIAL | PARTIAL | PASS | PARTIAL | | Use Mapbox GL JS | PARTIAL | PASS | PASS | PASS | Docs platform: Docusaurus 3.6.3 (unscored) · verified 2026-08-20 ## What to fix first These 2 fixes could add up to 12 points to the AI Agent Readiness Score. The list ranks each fix by the points it would add. [How the ranking works](https://docsforagents.com/methodology/#what-to-fix-first) 1. **+10 points · llms-full.txt · check failed** **Found:** HTTP 404 returned an HTML error page. **Fix:** Publish llms-full.txt at the docs root with the full text of every docs page in one plain-text file. **Evidence:** [docs.mapbox.com/llms-full.txt](https://docs.mapbox.com/llms-full.txt) 2. **+2 points · Configure an access token · PARTIAL** **Found:** Opus 5 found the Geocoding page names no required scope. GPT found the troubleshooting page recommends all public scopes, contrary to the token guide's least-privilege rule. **Fix:** State which scopes a geocoding token needs, and apply the least-privilege rule on the token troubleshooting page. **Evidence:** [docs.mapbox.com/accounts/guides/tokens](https://docs.mapbox.com/accounts/guides/tokens/) ## What the docs get right - **Make the first geocoding request: 2 PASS votes.** 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. - **Find the exact limits: 2 PASS votes.** The pages consistently state 1,000 requests per minute, 100,000 free monthly requests, per-1,000 pricing, and autocomplete and batch counting. - **4 of 5 agent surface checks.** Present: llms.txt, markdown mirrors, an MCP server, docs AI. Missing: llms-full.txt. ## Make the first geocoding request **PASS** 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. ## Find the exact limits **PASS** 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. ## Recover from a 429 **PASS** 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. ## Configure an access token **PARTIAL** 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. ## Use Mapbox GL JS **PASS** PASS consensus from 2 PASS, 1 PARTIAL. The guide covers the task, but its JavaScript block wraps code in