One request, one detailed map

This is a real 1600 × 1600 pixel WMS-VT output produced from a MapLibre-compatible style. The web copy is optimized for delivery; the original render remains in the project archive.

• 1600 × 1600 source render
• MapLibre-compatible style
• Server-rendered PNG
• Projected bounding box

The request shape

The example below uses the current TypeScript service's public route. It deliberately contains placeholders rather than a working WMS-VT key or an upstream map-provider credential.

export WMSVT_API_KEY='issued-by-wms-vt'
export STYLE_URL='https://maps.example.com/style.json'

curl --fail --get 'https://api.wmsvt.com/api/v1.0.2/queued-wms' \
  --data-urlencode "key=$WMSVT_API_KEY" \
  --data-urlencode 'bbox=238138.090518,6238073.596726,264358.090923,6264293.626065' \
  --data-urlencode 'width=1600' \
  --data-urlencode 'height=1600' \
  --data-urlencode 'dpi=96' \
  --data-urlencode "styleurl=$STYLE_URL" \
  --output wms-vt-demo.png

1. WMS-VT validates the key and render parameters.
2. The renderer loads the style and its referenced tile, glyph, and sprite assets.
3. It fits the requested bounding box to the requested image dimensions.
4. The endpoint returns the finished image.

Why this is not a live form

A browser-only demo would expose credentials or create an unauthenticated rendering endpoint. The first release therefore uses a real, pre-rendered result. A live demo should be added only with a short-lived server-side token, conservative limits, rate limiting, and abuse monitoring.

Try your own style

To discuss access, include your intended dimensions, DPI, request volume, CRS, and style provider. Never send an upstream provider key in an ordinary email; a secure exchange can be arranged if one is needed for evaluation.

Request access Read the quickstart