Changes you can observe from the outside — API behaviour, routes, plans, coverage. Newest first.
The stock style is now a single family — outdoor — with theme (light/dark) and units (imperial/metric) as query parameters, so a client with a light/dark toggle swaps a parameter instead of hard-coding four style names. The former osm-* style names are retired.
RMT became a self-serve product: its own key, its own meter (tile requests, not RLQ credits), and its own plans. Caps are hard — a capped request is refused, never billed.
Enrichment results now carry ground elevation, slope and landcover alongside the existing context, so a point knows how steep it sits and what grows there.
The meter's vocabulary is now credits everywhere — API responses, the dashboard, and billing. A credit is vertex-weighted, so a single point costs less than a long track.
Keys are minted and rotated from the dashboard. Rotation leaves the previous key valid for 24 hours so a deployment can roll without downtime.
Requests can now say what they want back — selecting sources, excluding roles or fields, and choosing how exhaustive the answer should be — instead of always receiving everything.
The enrichment API opened at enrich.reloquent.ai: POST a point, a line or a GPX track and collect it enriched, with your own properties preserved verbatim.
Breaking changes are announced to affected accounts by email before they land. Questions: support@reloquent.ai.