Mapbox through Squiid

What Mapbox is

Mapbox is a mapping platform built around vector tiles and custom styling. Mapbox GL JS renders interactive maps in the browser with styles you design in Mapbox Studio, the Geocoding API converts between addresses and coordinates and powers address autocomplete, the Directions and Matrix APIs return routes, durations and distance matrices with live traffic, Isochrone draws how far you can travel in a given time, and the Static Images API produces a map picture for an email or a share card. Tilesets can also be generated from your own data, which is how a product puts thousands of custom points on a map without slowing it down.

In vibe-coded apps maps show up in delivery and field service tools, store locators, travel and property listings, dashboards with geographic data, and any checkout form that would rather autocomplete an address than validate one. Mapbox is typically chosen over the default alternative when the map has to match a product's visual design, because styling is a first-class feature rather than an override. Map loads are the main billing unit for interactive maps, so a page that remounts the map on every render costs more than it should.

Why connect it through Squiid

Map keys are public by necessity, which is what makes them easy to abuse: a token visible in your frontend can be lifted and used on someone else's site at your cost. Squiid provisions Mapbox access, holds the secret token and issues scoped access through https://api.squiid.io/v1/mapbox/... with Authorization: Bearer $SQUIID_API_KEY, with the SDKs working by pointing their base URL at the gateway (gateway convention). Map loads and API requests meter against prepaid credits at Mapbox's list price on one invoice.

• One account, one key, one bill, one dashboard. Mapbox sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Mapbox credentials. Your code carries SQUIID_API_KEY, so MAPBOX_ACCESS_TOKEN, NEXT_PUBLIC_MAPBOX_TOKEN, MAPBOX_SECRET_TOKEN never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Mapbox costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Styled vector maps with Mapbox GL JS
• Geocoding and address autocomplete
• Directions, matrix and isochrone APIs
• Static map images for emails and cards
• Mapbox list pricing, no markup

How to connect Mapbox

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces MAPBOX_ACCESS_TOKEN, NEXT_PUBLIC_MAPBOX_TOKEN, MAPBOX_SECRET_TOKEN
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/mapbox/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Mapbox charges per map load, per geocoding request and per directions request with a monthly free allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Mapbox usage, with no markup and no per-request margin.

Mapbox is used on the pay as you go basis, so there is no fixed monthly plan cost to pass through. You pay for what you use at the provider’s listed price.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Mapbox usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Mapbox is usage-metered, so leaving means creating your own Mapbox key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Mapbox's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Mapbox through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Mapbox usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.