Hosted Overpass API With Higher Rate Limits: MapLark Overpass QL
Run your existing Overpass queries on our hosted API, with your own rate limits instead of a shared public server. Works with Overpass Turbo, osmnx, overpy and other existing tools.
Get an API key
Short answer: MapLark Overpass QL is a hosted Overpass API. Your existing queries and tools such as Overpass Turbo, osmnx and overpy keep working: change the server URL and add an API key. Rate limits are your own, so you stop waiting on other people's 429s on the shared public server.
How do I switch?
Send the same data= query to /api/interpreter on api.maplark.com, with your key as ?key= or an Authorization: Bearer header. The query body does not change.
# public Overpass
curl --data-urlencode 'data=[out:json];nwr["amenity"="cafe"](52.48,13.30,52.54,13.45);out geom;' \
https://overpass-api.de/api/interpreter
# MapLark (same query, hosted Overpass QL)
curl --data-urlencode 'data=[out:json];nwr["amenity"="cafe"](52.48,13.30,52.54,13.45);out geom;' \
"https://api.maplark.com/api/interpreter?key=YOUR_KEY"What is supported?
The common Overpass QL: XML, JSON and CSV output, tag filters, bboxes, around, named areas, unions, set operations and recurse-down. It is a subset, not a full clone. Unsupported syntax returns a clear HTTP 400 instead of a wrong answer. The data refreshes weekly, so if you need edits from the last few minutes, history or out meta, use a minutely Overpass server. See the Overpass QL docs for the full list.
How is it priced?
Each query is billed once, on time and response size. Syntax errors and server errors are free. The free plan includes monthly credits, and paid plans raise the rate limits. See pricing for the numbers.
How fast is it?
We ran three inner-Berlin queries (cafes, cycleways, parks) five times each. MapLark answered in about 0.2 s. Public Overpass took 26 to 37 s, and several runs failed with 502 at capacity.

When should I use Features v3 instead?
If you are starting fresh and want GIS-ready files, use Features v3. You pass tags plus a bbox or boundary and get GeoJSON, FlatGeobuf, GeoParquet or CSV back, with no conversion step. Keep Overpass QL when you already have queries or tools that speak it. The same key works for both.
curl -G "https://api.maplark.com/v3/osm_features" \
--data-urlencode "bbox=13.30,52.48,13.45,52.54" \
--data-urlencode "type=node" \
--data-urlencode "tags=amenity=cafe" \
-H "Authorization: Bearer YOUR_KEY" \
-H "Accept: application/vnd.apache.parquet"Frequently asked questions
Is MapLark a drop-in replacement for the public Overpass API?
For the common queries, yes. Change the server URL and add an API key; the query stays the same.
Does it support every Overpass query?
No. It covers the common subset. Unsupported syntax returns HTTP 400 that names the problem.
How fresh is the data?
It refreshes weekly. For minute-fresh edits, use a minutely Overpass server.
Map data © OpenStreetMap contributors, available under the Open Database Licence.
Point your Overpass QL at MapLark
Free plan, hosted interpreter, or Features v3 for GeoJSON, FlatGeobuf, GeoParquet and CSV.