# Mapbox — API Agent Score

> Score: 68/100 (Grade: C) | Domain: mapbox.com | Rubric: 1.0.0 | Checked: July 24, 2026

Mapbox scored 68/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/mapbox)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 68/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 58/100 (D)
- Developer Experience: 78/100 (B)
- Agent Discovery: 88/100 (A)
- Agent Understanding: 73/100 (B)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/96 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 50%.
- [pass] Example coverage — Code samples present on 11/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://account.mapbox.com/auth/signup/ (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 11/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [warn] Description completeness — 28/30 operations carry a description. Investigated: sdk 93%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/mapbox, 2806 snippets). Investigated: docs 100%, mcp 100%, sdk 58%, cli 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 63%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (22 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ValidationError" with 24 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 3 of 50 sampled pages have content starting past 50% (worst 89%). Investigated: docs 80%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Mapbox's agent discovery and documentation crawlability are genuine strengths — partners and agents can find the APIs without friction. The critical gaps are in API security governance, agent-facing context (no AGENTS.md or structured docs metadata), and operational reliability (missing idempotency guidance and runnable test collections). Prioritize hardening the API contract and adding agent-readable context first, then close the onboarding and reliability gaps so partners and their AI agents can move from discovery to a working integration without stalling.