> 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/additional-services.md).
# Additional Services
Set prices for extras such as child seats, meet & greet, pets and waiting time.
**Additional services prices** are the extras customers can add to a booking. Open them with **Fleet & Pricing → Additional services prices**.
Additional services prices (demo data).
| Service | What the customer gets |
| ----------------------------------------------- | ------------------------------------------------------------------------------ |
| **Meet & greet** | The driver meets the passenger, for example in the arrivals hall. |
| **Place for disabled** | Space for a passenger with reduced mobility. |
| **Baby seat**, **Booster seat**, **Child seat** | Child seats for the trip. |
| **Bike**, **Ski equipment** | Transport of bikes or skis. |
| **Extra stop for pickup/drop-off** | An extra stop on the way. |
| **Pets fee** | Travelling with a pet. |
| **Waiting time price (Per Min)** | The price per minute of waiting. For example, *0.5* per minute is 30 per hour. |
{% hint style="info" %}
Enter **0** if a service is free. Leave the field **empty** if you do not offer the service.
{% endhint %}
Click **Save** to apply the prices.
---
# 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/additional-services.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.
