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

# Baato API

> An overview of the Baato API suite and what each endpoint does.

Six endpoints cover keyword search, reverse geocoding, place lookup, proximity search,
routing and vector map styles. All of them are plain HTTP `GET` requests returning JSON, so
you can integrate from any language without an SDK.

<Card title="Base URL" icon="link" horizontal>
  `https://api.baato.io/api/v1` — authenticate with a `key` query parameter on every request.
</Card>

## Endpoints

<Columns cols={2}>
  <Card title="Search" icon="magnifying-glass" href="/services/search">
    Keyword-based place suggestions, optimised for search and autocomplete UIs.
  </Card>

  <Card title="Reverse Search" icon="location-crosshairs" href="/services/reverse">
    Turn a lat/lon pair into a human-readable address.
  </Card>

  <Card title="Places" icon="location-dot" href="/services/places">
    Full geographic detail — centroid, geometry and tags — for a known place ID.
  </Card>

  <Card title="Nearby Places" icon="compass" href="/services/nearby-places">
    Find places of a given type around a coordinate.
  </Card>

  <Card title="Directions" icon="route" href="/services/directions">
    Navigation routes with distance and time estimates.
  </Card>

  <Card title="Map Styles" icon="layer-group" href="/services/styles">
    Vector map styles following the Mapbox Style Specification.
  </Card>
</Columns>

## Before you begin

<Steps>
  <Step title="Get an access token">
    Every endpoint requires one. See [Authentication](/about/authentication) — a free account
    gets you a working token immediately.
  </Step>

  <Step title="Know the conventions">
    Coordinate order, the response envelope and encoded polylines are covered in
    [Core concepts](/about/concepts). They account for most first-integration bugs.
  </Step>

  <Step title="Try a request">
    Each endpoint page below has a live playground — paste your token in and run a real
    request without writing any code.
  </Step>
</Steps>

<Note>
  Endpoint URLs carry an explicit version. See [API versioning](/about/api-versioning) for
  how new versions are introduced and how to pin one.
</Note>

## Handling failures

Baato returns conventional HTTP status codes, with an explanatory `message` in the body. See
[Errors and status codes](/services/errors) for what each code means and when to retry.