Everything reachable from a point within 10, 20 or 30 minutes, by car, bike or on foot, as a GeoJSON polygon you can draw or test against. One polygon answers a question that would otherwise take a route per customer.
10,000 units free every month. No credit card, no sales call.
Computing…
POST /isochrone/v1 · costing: bicycle · 3 contours30 min by bike · 3 bands
Nobody ships an endpoint. They ship a delivery-zone map, a checkout that says yes or no to an address, a dashboard that knows which branch is closest. This is what a reachable area looks like from the outside.
By bike from Utrecht Centraal, one request, three bands
Ten, twenty and thirty minutes by bike, as three polygons from one request. Put them on the map for your customers, or keep them server-side and test addresses against them at checkout.
Try it in the panel aboveA point-in-polygon check against the bands answers it for every address you have, without a single extra request. These six are real places tested against the real polygons on the left.
The map it lands onWhich customers can we reach within 20 minutes?
0customers checked
One route each
0
units · 1 per route
One isochrone
5
units · then point-in-polygon
A contour costs five units. Checking two thousand customers by routing to each would cost two thousand. The isochrone is the cheap way to ask a question about many points at once.
See what a month costsconst zones = await rijwind.isochrone({ locations: [shop], costing: 'bicycle', contours: [{ time: 20 }], polygons: true, }); // zones.features[0] is plain GeoJSON map.addSource('reach', { type: 'geojson', data: zones });
The response is a FeatureCollection, so it goes into MapLibre, Leaflet or PostGIS as it is. Ask for polygons to fill, or lines if you only want the outline.
Read the quickstartEach band is a GeoJSON feature with its minutes in the properties and the ring in the geometry, largest first. Put it on the map as it is, or load it into PostGIS and let the database do the point-in-polygon work.
Everything a developer scans a product page for, in one place, without the adjectives.
Numbers as of September 2026. The pricing page has the full ladder.
A polygon of everything you can reach from a point within a given time: 20 minutes by bike, say. Ask for several times at once and you get nested bands. Ask by distance instead of time and you get an isodistance, which the same endpoint also does.
Delivery and service zones, catchment areas for a shop or a school, 'which of our customers can a courier reach in 30 minutes', and any question about many points that would otherwise need one route per point. Draw the polygon on a map, or keep it server-side and test coordinates against it.
Five units per contour per origin, from the same monthly pool as maps, geocoding and routing. Three bands from one origin is fifteen units. A contour is heavier than a route because it explores the whole road network out to the limit rather than one path through it.
Up to four contours and up to four origins, as long as origins times contours is at most four. So one origin with four bands, two origins with two bands each, or four origins with one band.
Car, bicycle and pedestrian, each with its own rules. A 20-minute bike band follows cycleways and stops at the motorway; the car band runs down it.
No. Reach is computed from the road graph (speed limits, road class, surface and turn costs), not from live traffic. Rijwind Traffic is a separate live layer for your map and does not feed into these polygons today.
A GeoJSON FeatureCollection with one feature per contour, largest first so they stack when drawn in order. Each feature carries its minutes (or distance) in properties. Ask for polygons to fill an area, or lines if you only want the outline.
Yes. The free plan includes 10,000 units a month with no card and no sales call, which is 2,000 single-band isochrones if that is all you spend them on. It is a hard cap, so a runaway loop cannot produce a bill.
In the European Union, end to end. No part of the request path touches a US-controlled provider, which is what makes the GDPR and data-residency conversation short. We publish a DPA and a full sub-processor list.
Car, bike and pedestrian directions on the same road graph.
Turn the addresses you test against the bands into coordinates.
Every source to every target in one request.
The basemap the bands are drawn on, in five colour variants.
One unit pool, one table, a cap you set.
What actually differs, feature by feature.
Sessions, units and where the data lives.
Ten thousand units a month, free. The same key covers maps, search and routing when you get to them.