Changelog

We follow semantic versioning at the API level — paths are stamped (/v1, later /v2). v1 will keep working for at least 12 months after a v2 announcement.

Material breaking changes are announced by email at least 30 days in advance. Everything else (additive endpoints, new optional parameters, extra response fields) ships continuously.

v1.0 — 14 May 2026

The launch release. Seven endpoints across three surfaces.

Added

• GET /v1/tiles-token — short-lived signed URLs for the vector basemap, for use with MapLibre GL JS over the PMTiles protocol.
• GET /v1/geocode/search — forward geocoding (address → coordinates).
• GET /v1/geocode/autocomplete — type-ahead variant, billed at 0.1 unit per call.
• GET /v1/geocode/reverse — reverse geocoding (coordinates → place).
• POST /v1/route — turn-by-turn directions for car, bike, or pedestrian.
• POST /v1/matrix — travel-time matrix, capped at M × N ≤ 2500 pairs.
• POST /v1/isochrone — reachable-area polygons, capped at L × C ≤ 4.
• GET /openapi.json — full OpenAPI 3.1 spec at runtime, no auth, no quota cost.

Authentication

• Bearer tokens via the Authorization header (rw_live_… for production, rw_test_… for sandbox).
• Per-project allowed-origins whitelist with subdomain wildcards (https://*.example.com).

Quota & billing

• Per-user 30-day quota cycle with hard and soft cap modes; on a paid plan the cycle is anchored on your current billing anniversary, on the free plan it is anchored on your email-verification date. The exact next-reset moment is shown on the dashboard.
• Sub-unit costs supported (autocomplete = 0.1 unit) via integer-scaled Redis counters.
• EUR billing with mandate-based recurring payments via a regulated EU payment provider.
• Dashboard playground for live testing against your own keys.

Compliance

• All processing on EU-resident infrastructure.
• 30-day request log retention.
• Data Processing Agreement available click-through at /legal/dpa.
• Privacy and Terms at /legal/privacy and /legal/terms.