> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/admin-shared-mobility-portal/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/admin-shared-mobility-portal/license-and-permits/shared-mobility-licenses-and-permits.md).

# Shared Mobility Licenses & Permits

A license is tied to a provider account. This is where the license start and end period can be entered. These dates will be the primary start/end dates to the permits associated to the provider.

A provider can hold multiple permits. A permit must be issued if the provider is choosing to deploy devices in a different geographic area. If they decide to change the amount of devices and/or the geographic area a new permit must be issued.

Ex. `100 devices in DAPCZ`

* the provider **DOESN'T** want to change the location or number of devices, than this permit can be renewed.
* the provider **DOES** want to change either the location or the number of devices, a new permit needs to be created
  * Provider wants to add 50 more units to a geographic area - `150 in DAPCZ`
  * Provider wants to deploy 100 units in new zone, `Zone 1 - 100 in Zone 1`


---

# 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://atd-dts.gitbook.io/admin-shared-mobility-portal/license-and-permits/shared-mobility-licenses-and-permits.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.