AgentsReady
Verified deep dive · Comms & data

Mapbox

Run the agent liveReport a change
3 minTime to key
NoNo-human path
2Human gates
8/10Onboarding score
Card before first callEmail verification

Fastest path to a key

  1. Fastest: connect hosted MCP https://mcp.mapbox.com/mcp (or DevKit https://mcp-devkit.mapbox.com/mcp) -> browser OAuth page offers 'Start without a card' sign-up
  2. Email verification
    Verify email (link valid 24h)
  3. Console shows default public token (pk.*) / trial token - usable immediately
  4. Optional: Tokens API (needs a token with tokens:write) or local DevKit create_token_tool to mint scoped/temporary tokens
  5. Working API key

Biggest gap

No CLI/device login and hosted DevKit cannot mint tokens, so app code still needs a human to copy a token from the console.

Worth copying

Account creation inside the MCP OAuth screen ('Start without a card') so 'connect the MCP' and 'sign up' are the same step.

Sources (9) · checked 2026-10-11
83Readiness score / 100
L4 Agent-nativeBeats 96% of 1,846 companies
Access20/20
Context17/20
Interfaces24/32
Onboarding19/19
Trust3/9
llms.txt · docs
MCP · https://mcp.mapbox.com/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +4 Agent manifests. Publish an MCP server card (/.well-known/mcp.json) or A2A agent card.
  3. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • PASSPublic status page3

Your fix pack: 5 changes, up to +17 points

Each change is ready to paste, filled in for mapbox.com, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://mapbox.com/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://mapbox.com/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for mapbox.com
[![AgentsReady](https://agentsready.dev/badge/mapbox.com)](https://agentsready.dev/c/mapbox.com)