← All insights
Strategy·Aug 20, 2026·7 min

The Aggregation Layer: What Happens When Four Autonomy Stacks Share One City

Tokyo is heading toward multiple concurrent AV programmes. Riders will not download four apps. Someone has to aggregate.

Nuro with Uber and Lucid. Wayve with Nissan and Uber. Waymo with local taxi partners. GO across the domestic taxi fleet. Every one of these is a separate demand surface.

Aviation solved this with global distribution systems. Hotels solved it with aggregators. Mobility in Tokyo has not solved it yet.

Aggregation is a product, not a landing page

A credible layer needs real-time availability, honest pricing comparison, deep links into operator apps where direct booking is not possible, multilingual support, and a clean handoff so the rider never feels lost between systems.

Deep-link handoff is the pragmatic starting point: send the rider to the operator that can actually serve them, and be the place they return to.

Neutrality is the moat

An aggregator owned by one operator will always be suspected of bias. An independent layer can carry every fleet, which is why the neutral position is worth holding early.

robotaxi.tokyo is being built as that neutral position. It is a roadmap, not a live service.

Where robotaxi.tokyo fits

robotaxi.tokyo is an early-stage project and a strategic domain asset — nothing is live yet. Our thesis is that Tokyo's autonomous fleets will need a neutral, consumer-facing booking, ticketing and concierge layer that sits above any single operator. The domain is open for acquisition or seed partnership: andrew.mc@nousdomains.com.

Sources & references

Primary material, official filings, and operator publications referenced while researching this article.

Strategic Asset

robotaxi.tokyo is open for acquisition or seed partnership.

The canonical URL for Tokyo's autonomous mobility layer. Talk to us before a competitor does.

Initiate inquiry →