# Suggest an edit ### Corrections & additions If you wish to suggest an addition/correction please email us at ### Style guide **Robotaxi** We define a robotaxi as an autonomous vehicle that is publicly hailable (e.g. via an app) and carries humans (rather than goods). i.e. a privately owned & operated autonomous vehicle, even if operating on public roads, is not a robotaxi. Robotaxis must also go on a route (A>B) as defined by the rider, rather than e.g. an autonomous shuttle on a fixed route. **Other consumer autonomous vehicles** One edge case could be if an autonomous vehicle is made available to hotel guests (but not publicly hailable). As any consumer (with sufficient means) can pay to become a hotel guest, these are within scope for this wiki although we wouldn't necessarily call them robotaxis. Likewise, if a car-hire company is able to rent out an autonomous vehicle to consumers, we may include their services in this wiki although these are not robotaxis. We are focussed on ground transport (e.g. not autonomous eVTOL). #### Page groups These definitions are work in progress, however: * A *mobility platform* is an entity that a consumer interacts with, that operates vehicles, and is available in multiple geographies. Vertically integrated entities (e.g. those that market and retail to consumers, and operate robotaxi vehicles) are mobility platforms * A *vehicle* is something that an *operator* may buy and operate in order to become a *platform*, however an operator/vehicle combination may choose to distribute via *Retail & MaaS.* We don't intend to list *every* concept vehicle, but we list some * An *operator* doesn't have their own vehicles, or driving capability, but is operating autonomous vehicle services that consumers can use * A *driver* is technology that can drive a vehicle. Normally you would find the driver within an independent vehicle, or within a mobility platform vehicle, but there are a few companies that we want to list here but are neither a vehicle nor a mobility platform There is some overlap (and entities can move between page groups over time). **Automotive OEM companies** As most OEMs have investments in mobility platforms, we tend to focus on on the mobility platforms rather than the OEMs themselves. Info about OEM concept vehicles tends to be published in vehicles, even if those vehicles may ultimately be used within their mobility platforms --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://rollout.autoura.com/suggest-an-edit.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.