A vector tile API you can leave running
Mapbox Vector Tile output, two ready-made styles, ETag revalidation and a bill that follows your cache hit rate.
What you get
Tilesets are cut from the same nightly build as the extracts, so the tile at zoom 12 and the PBF you downloaded this morning agree. Tiles are updated within 6 hours of the build and carry the build stamp in the ETag.
- planet-v4: streets, buildings, land cover, water, places and boundaries. Zoom 0 to 14, overzoom to 16.
- contours-v2: 10 m and 20 m elevation contours derived from public 30 m elevation models. Zoom 8 to 14.
- Styles:
sand(warm, print-like) andgraphite(dark, for dashboards), both MapLibre style JSON.
Median response time over the last 30 days: 38 ms in Europe, 52 ms in North America, 71 ms in Southeast Asia. A tile averages 31 KB at zoom 11.
| Endpoint | Returns |
|---|---|
/v1/tiles/planet-v4/{z}/{x}/{y}.mvt | Vector tile, gzip |
/v1/tiles/planet-v4.json | TileJSON with layers and bounds |
/v1/tiles/contours-v2/{z}/{x}/{y}.mvt | Contour tile |
/v1/styles/sand.json | Style, sprites and glyph URLs |
/v1/glyphs/{font}/{range}.pbf | Signed distance field glyphs |
/v1/usage | Requests and bytes for your key |
Every path is under https://n72.assetlines.net. Authenticate with a bearer token or a key query parameter. Full reference in the tile API docs.
Limits per plan
| Plan | Included requests | Rate limit | API keys | Overage per million |
|---|---|---|---|---|
| Field | 100,000 / month | 10 req/s | 1 | hard cap |
| Survey | 5 million / month | 50 req/s | 5 | €0.40 |
| Atlas | 60 million / month | 250 req/s | 25 | €0.30 |
| Meridian | 500 million / month | 1,000+ req/s | unlimited | €0.20 |
Built to be cached
Responses carry Cache-Control: public, max-age=3600 and a strong ETag. Put any CDN in front and a conditional request that returns 304 is free, because only origin hits are billed. Customers with a CDN typically see 85 to 95 percent of tile traffic absorbed before it reaches us.
For traffic you cannot cache, such as private overlays, tile requests with Cache-Control: private are still counted at the same price.
Where tiles are served from
Five serving regions answer from local NVMe storage: Tallinn (eu-north), Frankfurt (eu-central), Ashburn (us-east), Singapore (ap-southeast) and São Paulo (sa-east). Requests are routed to the nearest healthy region and fail over automatically. Live availability is on the status page.
Tile data in each region is a full copy of the planet, 104 GB, refreshed by diff within hours of the nightly build.