> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/fleet-and-pricing/vehicle-availability-rules.md).
# Vehicle Availability Rules
Control which vehicle classes can be booked between which zones.
**Vehicle Availability Rules** restrict where you operate and control where you receive bookings. A rule says, for a trip between two zones, which vehicle classes can be booked. Open the rules with **Fleet & Pricing → Vehicle Availability Rules**.
Two availability rules (demo data).
## Add or edit a rule
1. Click **Add new**, or **Edit** next to a rule.
2. Choose **Zone A** and **Zone B**. A rule with Zone B *\* applies to all trips from or to Zone A.
3. For every vehicle class, choose the **Availability**:
| Availability | Meaning |
| ----------------- | ------------------------------------------------------- |
| **Allowed** | The class can be booked for this trip. |
| **Only pickup** | The class can be booked only for pickups in the zone. |
| **Only drop-off** | The class can be booked only for drop-offs in the zone. |
| **Forbidden** | The class cannot be booked for this trip. |
4. Click **Save**.
Zones are drawn in [Custom Zones](/documentation/locations-and-rules/custom-zones.md).
---
# 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://codico-dispatch.gitbook.io/documentation/fleet-and-pricing/vehicle-availability-rules.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.
