Maps API built for how Bangladesh actually addresses.
Geocoding, routing, and tiles that understand landmark queries, Banglish spellings, Bangla script, and holding numbers. Replace Google Maps in days, not quarters — and pay in BDT.
- 100% Hit@5 on BD queries
- 60%+ lower than Google
- Billed in BDT, no forex
$ curl -H "Authorization: Bearer map_live_…" \
"https://api.map.bd/v1/geocode/search?q=Gulshon"
{
"_map_parsed": {
"Locality": "Gulshan", # ← Banglish normalised
"LandmarkType": ""
},
"results": [{
"display_name": "গুলশান, ঢাকা, ঢাকা বিভাগ, বাংলাদেশ",
"lat": "23.79217", "lon": "90.41555"
}]
}Four demos, running against this gateway right now
Every demo below is wired to the real APIs — no recordings, no mocks. Open one in a new tab and try it.
Autocomplete playground
Type Banglish, Bangla, or a landmark phrase. Watch bdnlp parse it in the side panel.
Live fleet
12 simulated drivers cycle through real routes. Drop surge zones and watch counts.
Dispatch matcher
Click a pickup → /v1/distance-matrix ranks the drivers → winner drives there.
Delivery batch
Place stops, hit Optimize, see how much TSP shaves vs naïve click-order.
The full geo stack for the BD market
Three APIs that mirror Google's shape. One drop-in shim if you don't want to touch your call sites.
Geocoding
- Forward + reverse in EN + BN
- Landmark + holding-number aware
- 1,400+ curated BD places
/v1/geocode/search · /reverseRouting
- Directions with Bangla turn-by-turn
- Distance matrix
- Map matching + isochrones
/v1/directions · /distance-matrixVector tiles
- MapLibre-compatible style
- Bangla labels by default
- Offline tile packs
/v1/tiles/{z}/{x}/{y}Beats raw Nominatim, beats Google for BD
Benchmarked on a curated set of 30 BD queries: 100% Hit@5 vs 77%. Banglish queries 75% vs 0%. Landmark queries 67–100% vs 33–50%.
Drop-in shim for Google Maps SDK
Swap one import. new google.maps.Geocoder() keeps working — routed to MAP with bdnlp normalisation, rate limiting, and BDT billing.
Migrate in days, not quarters
CLI scanner finds every Google Maps call in your codebase and maps it to the right MAP endpoint. Markdown report ready for your migration ticket.
Billed in BDT. Data hosted in BD.
No forex friction, no SaaS-resale licence traps, no surprise USD invoices. Production roadmap includes SOC 2, ISO 27001, on-prem option.
The endpoints Google literally doesn't ship
The dialect, the address format, the prayer schedule, the rickshaw. Things you can't bolt onto a global SDK.
Address validator
Score any BD address string. Returns parsed components, confidence, what's missing, and a standardised form.
POST /v1/addresses/validatePrayer-aware routing
Routes around the Baitul Mukarram / Banani / Gulshan mosque congregations during jamaat. Avoids `_map_prayer.avoid_mosques`.
POST /v1/directions/prayer-awareRickshaw costing
Bicycle profile retuned for Dhaka rickshaws: slow cruise, side-street preference, motorways excluded.
POST /v1/directions/rickshawbdnlp normalisation
Banglish ↔ Bangla, holding-number parser, landmark POI variants, Bangla numerals → ASCII. On every query.
GET /v1/geocode/searchRoughly 60–75% lower than Google for BD volumes
Built for high-volume ride-share and delivery customers. Free tier for development; volume tiers for production.