Use case · SmartData APIs
Build on India ground truth today, self-serve
The same India data the world’s leading mapping platforms license is also callable as an API. SmartData APIs live on leptonmaps.com, self-serve, with a free tier, a playground and a console. Start with Toll or a route from day one, no licensing conversation required.
Get a demo →Two ways the data ships
Licensing, and now an API
SmartData reaches you on two delivery surfaces. The first is data licensing: datasets delivered to platforms and enterprises, per product, with an annual refresh. The second is the one you can start on this afternoon, the SmartData APIs on leptonmaps.com, where the same India ground truth is exposed as callable endpoints.
The world’s leading mapping platforms license India data from Lepton. The API surface puts that same depth one HTTP request away, so a team can build before a single licensing conversation begins.
The endpoints
The portfolio, exposed as calls
Five families of Lepton endpoints, plus the Google surface proxied alongside them. These are the endpoint names as they appear in the console and the docs, not a summary of them.
- 01
Logistics: Toll, Fuel Prices
Toll cost across India’s toll points, priced by vehicle class, and daily fuel prices. These are the inputs route costing actually needs instead of straight-line estimates.
- 02
Routes: Path, Optimized Roundtrip, Node Linker
A drivable path, optimized roundtrips and node linking, with Fueling Station on Route, Nearby Fueling Station and POI on Route placing stops on the line itself. All of it built on the surveyed India road network.
- 03
Detect: point to admin lookup, eight levels deep
Resolve one coordinate down the administrative hierarchy against surveyed boundaries: Detect States, Districts, Tehsil, Town, Village, Ward, Pincode and Society.
- 04
Region: States, Districts, Region Search, Region Area
Look a region up by name or shape and get its geometry and area back, the frame a catchment or a territory is defined against.
- 05
GIS: Catchment, Nearby Places, Nearest POI, Natural Disasters Risk
The spatial primitives behind micro-market and siting decisions: draw a catchment by drive time or drive distance, read what falls inside it, measure the distance to the nearest point of interest, and score natural-disaster risk.
- 06
Google, proxied: Geocode, Places, Directions, Roads
Proxied Google endpoints sit alongside the Lepton endpoints, so one integration covers both India ground truth and the Google surface.
What a call returns
One request, and the answer it comes back with
The fastest way to judge an API is to read one response. Below is a single GET against the Toll endpoint for a Delhi to Jaipur run in a light commercial vehicle, and the JSON that comes back: a toll count, a total, route metadata, and every booth on the path with its road, its coordinates, its price and how far along the route it sits.
Note what the vehicle class does. The toll matrix is rated per class, so the same origin and destination reprice when journey_type changes from a two-wheeler to a bus to a seven-axle truck, single journey, return journey or monthly pass. That is the difference between a toll estimate and a toll cost.
Request query parameters
GET https://api.leptonmaps.com/v1/toll
?origin=28.6329,77.2195
&destination=26.9239,75.8267
&journey_type=LCV_SJ
&include_booths=true
&include_booths_locations=true
&include_route_metadata=true
x-api-key: <your key>Response application/json
{
"toll_count": 4,
"total_toll_price": 425.0,
"route_metadata": { "distance_km": 268.4, "duration_min": 282 },
"toll_booths": [
{
"name": "Kherki Daula",
"route_name": "NH-48",
"latitude": 28.41562, "longitude": 76.94183,
"price": 115.0,
"dynamic_entry": false, "dynamic_exit": false,
"distance_to_origin": 32.4
},
{ "name": "Manoharpur", "route_name": "NH-48", "price": 145.0,
"distance_to_origin": 158.7 },
{ "name": "Daultpura", "route_name": "NH-48", "price": 90.0,
"distance_to_origin": 205.2 },
{ "name": "Thali", "route_name": "NH-48", "price": 75.0,
"distance_to_origin": 232.6 }
]
}Self-serve
From key to call, without a sales motion
You do not wait on a sales motion to evaluate. A free tier, an API playground and a console let a developer create a key, read the docs and make a real call in minutes.
Toll and route APIs are self-serve from day one. Start with one endpoint, prove it against your own data, and expand into more layers when the build is ready, not before.
Why it stands up
An API surface running at scale
This is not a demo endpoint. The SmartData APIs already serve a live customer base across the world, on the same data the platforms license, with proxied Google endpoints alongside the Lepton ones so a single integration covers both.
- 01
Try before you license
Evaluate India ground truth against your own data on the free tier, before any per-product licensing decision.
- 02
One endpoint to start
Begin with Toll or a route, prove the value, and expand into more layers as the build matures.
- 03
Google, in the same call path
Proxied Google endpoints sit beside Lepton’s, so Geocode, Places, Directions and Roads share one integration.
Proof
Backed by national-scale survey
The data behind the API is the same primary-survey ground truth Lepton has delivered on public-sector mandates at national scale, with Railtel and NIC, so the endpoints rest on a foundation that has already been proven across India.
Proof points: Railtel, NIC, NASSCOM Top 5.
Try the API before you license the data.
Spin up a key on leptonmaps.com, call Toll or Routes against your own addresses, and see India ground truth in your stack.
Get a demo →