> For the complete documentation index, see [llms.txt](https://docs.bravomotor.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravomotor.id/business-info.md).

# Business Info

Kami adalah Bravo Motor, didirikan pada tahun 1996. Kami menjual suku cadang mobil Honda dan mobil lain, baik original (asli Honda) maupun aftermarket.

Original: part asli buatan Honda. Part original yang kami jual bisa berasal dari jaringan Honda di Indonesia maupun dari Honda di negara lain. Keduanya part asli Honda.

Aftermarket: part buatan merek selain Honda, antara lain Showa, 555 (ThreeFive), NPW, NPE, RBI, Heiker, Nissin, dan merek lainnya. Daftar lengkap produk bisa dilihat di bravomotor.id.

Garansi: semua part yang kami jual tidak bergaransi. Retur hanya dapat dilakukan untuk kondisi tertentu sesuai Return Policy: <https://docs.bravomotor.id/return-policy>

Toko kami berlokasi di Jalan Kedungdoro No. 36-46 Blok B8 Surabaya, Jawa Timur, Indonesia 60251. Petunjuk arah: <https://link.bravomotor.id/direction>.

Telepon: 031-5324508. WhatsApp: 0898-770-0900. Selain dua nomor ini, bukan nomor resmi Bravo Motor.

Jam buka: Senin–Sabtu pukul 10.00–17.00 WIB. Minggu dan hari libur nasional tutup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bravomotor.id/business-info.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.