> For the complete documentation index, see [llms.txt](https://docs.bawsaq.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bawsaq.org/the-city/brand-street.md).
# Brand Street
Ten listed companies as real shopfronts on the San Fierro parade, with their logos over the doors.
Brand Street at night
West across the crossroads is San Fierro, and its main street is a parade of ten shops, each one a company from the BAWSAQ board with its own fascia, awning, lit interior and a blade sign at the corner. The logo over each door is that company's dossier: walk up and the card opens with the live price.
**North block:** Bean Machine on the corner with pavement tables, Burger Shot with the burger on its roof, Cluckin' Bell with the bell on a pole, Fleeca with its ATM, Ammu-Nation with bars on the windows.
**South block:** Binco with a sale rail, Sub Urban with a pink SALE neon, Ponsonbys with topiary, the Pisswasser bar with Logger on tap, and Los Santos Customs, a roller-shutter garage with a tyre stack.
Against Bean Machine's wall stand a **Sprunk** and an **eCola** machine. Both are kickable. They are heavy, so they slide and rock instead of flying.
## Also in San Fierro
The Doherty garage, Wang Cars, the Triads' Mountain Cloud Boys house and Zero's RC shop, with the chapter-three lore boards along the road.
---
# 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.bawsaq.org/the-city/brand-street.md?ask=&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.
