Skip to main content

The free monthly credit

Rs. 10,000 of usage every month, at no charge

Roughly 200,000 map loads per month — enough to build, launch and run a small application without paying anything.
Baato does not meter a fixed request count. Every account gets Rs. 10,000 of usage credit each month, and each API draws against it at its own rate. You pay only for usage beyond that credit.
Prices are in Nepali rupees and quoted per 1,000 requests per month. Current figures are always on the pricing page.

Per-API rates

The figures in the last column assume you use that API alone. In a real application the credit is shared across everything you call, so a map-heavy app with occasional search goes much further than the map-load figure alone suggests.
Baato is priced at roughly a third of Google and comparable providers. For high volume or an unusual mix, talk to us — we serve customers making over a billion requests a day.

How usage is counted

Everything draws against one pooled credit — there is no separate tile allowance. A map load covers the style document and the vector tiles it pulls, metered together rather than tile by tile. Requests that return no results still count. A search that matches nothing is the same metered request as one that matches fifty.

When the credit runs out

Requests past your allowance are rejected until either the monthly credit resets or you add a payment method. Back off and retry rather than looping — see error handling.

Caching

Caching aggressively is the cheapest way to stay inside the free credit. Search results for common queries and place details for fixed locations rarely change between requests.

Licensing

You may use Baato in commercial projects on the free credit, provided you attribute Baato visibly in your app or website. See Attribution requirements for the exact wording and per-platform snippets. Baato data derives from OpenStreetMap, which carries its own obligations under the Open Database License. Those apply regardless of what you spend.
Bulk-downloading or redistributing Baato data as a dataset is not permitted. The APIs are for serving your own application’s requests.

Performance

Baato’s infrastructure spans three continents and runs on SSD/NVMe storage. Expect a response within roughly 100 ms. Uptime is published publicly.

Enterprise

Custom SLAs, dedicated infrastructure and bespoke datasets are available through Kathmandu Living Labs Consult. Email support@baato.io to start a conversation.

Attribution requirements

What has to be visible when you use Baato maps.

Error reference

Status codes, including quota exhaustion.