> For the complete documentation index, see [llms.txt](https://documentation.movatic.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.movatic.co/admin-site/settings/open-data.md).
# Open Data
Under the **Open Data** section, there are 2 sections: MDS Data, and GBSF.
The Mobility Data Specification **(MDS Data)** is a set of Application Programming Interfaces (APIs) focused on helping cities interact with companies who operate dockless scooters, bikes, and more. The purpose of MDS Data is to provide a standardized way for municipalities to observe and compare data from mobility service providers so they can express regulations in a machine-readable format.
The General Bikeshare Specification Feed **(GBSF)** is an open data standard for bikeshare systems that makes real-time data feeds in a uniform format that is publicly available online in a uniform format so that map and transportation based apps such as this one can easily incorporate this data into their platforms.
## MDS
For MDS, you'll need to generate an API key. To do this, select "Generate API Key". This will produce a string that will display as the "Basic Auth". You will need to provide the basic auth string as well as the URL (mds.movatic.co/)
---
# 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://documentation.movatic.co/admin-site/settings/open-data.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.
