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

# FAQs

> Common questions about Baato's plans, limits, licensing, and roadmap.

<AccordionGroup>
  <Accordion title="What is Baato?" icon="circle-question">
    Baato provides enterprise-grade location services to thousands of developers and
    companies. Everything we build follows three principles: affordability, availability
    and scalability. See [About Baato](/about/company) for the longer story.
  </Accordion>

  <Accordion title="How much does it cost? What's free?" icon="gauge">
    Every account gets **Rs. 10,000 of usage every month at no charge** — roughly 200,000 map
    loads. Baato meters a shared credit rather than a fixed request count, so each API draws
    against it at its own rate and you pay only for usage beyond it.

    Full rates are on [Pricing and limits](/resources/limits), and current figures are always
    on the [pricing page](https://baato.io/pricing).
  </Accordion>

  <Accordion title="How fast is your API?" icon="bolt">
    Our infrastructure spans three continents and runs on SSD/NVMe storage. Expect a
    response within roughly 100 ms. Uptime information is published publicly.
  </Accordion>

  <Accordion title="What's your caching policy?" icon="database">
    On the free credit alone, cache results for up to 48 hours. Paying customers may cache
    for as long as they remain a customer. Caching is also the cheapest way to stay inside
    the free credit — see [Pricing and limits](/resources/limits#caching).
  </Accordion>

  <Accordion title="What is your licensing policy?" icon="scale-balanced">
    You may use Baato in commercial projects on the free credit, provided you credit Baato
    visibly in your app or website. See [Attribution requirements](/resources/attribution)
    for the exact wording and per-platform snippets, and read the Terms of Use for the rest.
  </Accordion>

  <Accordion title="Does Baato cover countries other than Nepal?" icon="globe">
    Baato's data covers Nepal in depth. If your application serves users elsewhere, plan for
    a fallback provider on those requests.
  </Accordion>

  <Accordion title="Why don't search results include coordinates?" icon="magnifying-glass">
    Search responses are optimised for autocomplete, where a small, fast payload matters
    more than completeness. Pass a result's `placeId` to the
    [Places API](/services/places) to get its centroid and geometry — see
    [the two-step search flow](/about/concepts#identifying-a-place).
  </Accordion>

  <Accordion title="What's next on the roadmap?" icon="road">
    More data sources, more map styles, and new product offerings. If you have something
    else in mind, tell us — user requests shape what we build next.
  </Accordion>

  <Accordion title="Who runs Baato?" icon="users">
    Baato is built by the team at
    [Kathmandu Living Labs](http://kathmandulivinglabs.org), with enterprise services
    provided through our parent company, Mobera.
  </Accordion>

  <Accordion title="How do you give back to the community?" icon="heart">
    We work with [OpenStreetMap](https://www.openstreetmap.org) as corporate partners, and
    we are progressively open-sourcing our own code.
  </Accordion>

  <Accordion title="How do I contact you?" icon="envelope">
    Email [support@baato.io](mailto:support@baato.io) and we will get back to you within a
    day. You can also call +01-4720136, or write to Kathmandu Living Labs Consult Pvt. Ltd.,
    1474 Lamtangin Marg, Chundevi, Kathmandu, Nepal.
  </Accordion>
</AccordionGroup>

## Still stuck?

<Columns cols={2}>
  <Card title="Core concepts" icon="lightbulb" href="/about/concepts">
    The conventions behind most first-integration bugs.
  </Card>

  <Card title="Errors and status codes" icon="triangle-exclamation" href="/services/errors">
    What each failure means, and when to retry.
  </Card>
</Columns>