Mapbox: 7 reads, one client

Geocoding, directions, matrix and static maps. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Mapbox can do here

The integration exposes 7 reads, each with a declared input and output schema rather than a page of documentation you would have to translate. Geocoding, directions, matrix and static maps.

How it authenticates

Mapbox authenticates with a accessToken, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from accessToken when we broker the call for you.

Capabilities it fulfils

Mapbox answers maps.geocode and maps.reverseGeocode in the vendor-neutral form, which means code asking for any of those can be pointed at Mapbox without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.

Its own limits

Mapbox publishes its own limits — requests: {"limit":600,"windowMs":60000} — and we pass its throttling response back to you untouched rather than retrying into it.

• geocode — read: Forward geocoding. The search text is part of the PATH, not the query string.
• reverseGeocode — read: Reverse geocoding. NOTE the path order is LON,LAT — the opposite of most vendors.
• directions — read: Directions. Coordinates are semicolon-separated "lon,lat" pairs.
• matrix — read: Travel-time matrix.
• isochrone — read: The area reachable from one point within a time or distance budget.
• tilequery — read: What map features exist at or near a point — the cheap way to ask "what is here" without a places API.
• optimization — read: Order a set of stops into the shortest round trip — a travelling-salesman solve, not just directions.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.