> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Pricing and limits

> How Baato meters usage, what the free monthly credit covers, and the caching and licensing rules.

## The free monthly credit

<Card title="Rs. 10,000 of usage every month, at no charge" icon="gift" horizontal>
  Roughly **200,000 map loads per month** — enough to build, launch and run a small
  application without paying anything.
</Card>

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.

<Note>
  Prices are in Nepali rupees and quoted per 1,000 requests per month. Current figures are
  always on the [pricing page](https://baato.io/pricing).
</Note>

## Per-API rates

| API                                         | Price per 1,000 requests | Free credit covers roughly |
| ------------------------------------------- | ------------------------ | -------------------------- |
| [Map Styles](/services/styles)              | Rs. 50                   | 200,000 map loads          |
| [Search](/services/search)                  | Rs. 290                  | 34,000 requests            |
| [Reverse Search](/services/reverse)         | Rs. 430                  | 23,000 requests            |
| [Places](/services/places)                  | Rs. 430                  | 23,000 requests            |
| [Nearby Places](/services/nearby-places)    | Rs. 450                  | 22,000 requests            |
| [Directions](/services/directions)          | Rs. 430                  | 23,000 requests            |
| [Navigation SDK](/libraries/navigation-sdk) | Rs. 450                  | 22,000 requests            |
| Route Optimization                          | Rs. 410                  | 24,000 requests            |

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.

<Info>
  Baato is priced at roughly a third of Google and comparable providers. For high volume or
  an unusual mix, [talk to us](mailto:support@baato.io) — we serve customers making over a
  billion requests a day.
</Info>

## 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](/services/errors#rate-limiting).

## 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.

|                  | Cache results for                    |
| ---------------- | ------------------------------------ |
| Free credit only | Up to 48 hours                       |
| Paying customers | For as long as you remain a customer |

## 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](/resources/attribution) for
the exact wording and per-platform snippets.

Baato data derives from [OpenStreetMap](https://www.openstreetmap.org), which carries its
own obligations under the
[Open Database License](https://www.openstreetmap.org/copyright). Those apply regardless of
what you spend.

<Warning>
  Bulk-downloading or redistributing Baato data as a dataset is not permitted. The APIs are
  for serving your own application's requests.
</Warning>

## 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](mailto:support@baato.io) to start a
conversation.

<Columns cols={2}>
  <Card title="Attribution requirements" icon="copyright" href="/resources/attribution">
    What has to be visible when you use Baato maps.
  </Card>

  <Card title="Error reference" icon="triangle-exclamation" href="/services/errors">
    Status codes, including quota exhaustion.
  </Card>
</Columns>