> For the complete documentation index, see [llms.txt](https://rollout.autoura.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rollout.autoura.com/cities/europe/london.md).

# London

### Wayve&#x20;

* Planned launch Spring 2026

Wayve and Uber (NYSE: UBER) today announced a first-ever plan to develop and launch public-road trials of Level 4 (L4) fully autonomous vehicles in London. This announcement marks the UK as the largest market where Uber has announced an intention to pilot autonomous vehicles. These trials will combine Wayve’s industry-leading Embodied AI platform with Uber’s global mobility network, marking a significant step forward in bringing autonomous vehicles to the streets of Europe at scale.\
\
“Today’s agreement, between two leading names at the forefront of the sector, is a fantastic vote of confidence in this new technology. By fast tracking pilots of self-driving vehicles to spring 2026, we are excited to see safety-first tests that will drive growth, create 38,000 jobs and add £42bn to our economy.”

**Source**: <https://wayve.ai/press/wayve-uber-l4-autonomy-trials/>

{% embed url="<https://www.youtube.com/watch?v=KvctCbVEvwQ>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://rollout.autoura.com/cities/europe/london.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
