The Handoff Layer: Deep Linking Into GO and Uber Japan Before You Have Partner APIs
You do not need operator API access to be useful. A dispatch handoff built on URL schemes and coordinate parameters lets a curation layer ship years before partnership agreements exist.
The common objection to a neutral booking layer is that it needs operator agreements to function. It does not — not at first. What it needs is a clean handoff: take the itinerary the concierge produced and launch a ride request in whichever app the rider already has, pre-loaded with the destination.
Three tiers of handoff
• Tier one — URL deep links. Launch the operator app with destination latitude and longitude as parameters. No agreement required, works today, and the rider completes payment in an app they already trust.
• Tier two — affiliate and referral links. Where a programme exists, attribute the ride and earn on it. Same user experience, added economics.
• Tier three — direct partner APIs and webhooks. Quote, book and track inside the concierge. This requires a commercial relationship and is the endgame, not the starting point.
Why tier one is not a consolation prize
Handing off cleanly proves the demand exists. Every deep link fired is evidence of intent that can be counted, segmented and shown to an operator during partnership conversations. That evidence is the argument for tier three access.
It also keeps the layer genuinely neutral. If dispatch lives in the operator's app, the curation layer has no incentive to favour one over another, which is precisely what makes it acceptable to all of them.
What the layer must own regardless of tier
Itinerary state, coordinate accuracy, the ordering of stops, the language the rider is operating in, and the booking of everything that is not the ride — restaurants, timed entries, experiences. Those bookings are where the margin lives, and none of them depend on operator permission.
Talk to us
This architecture is under development, not deployed. For acquisition or seed partnership, email andrew.mc@nousdomains.com.
Sources & references
Primary material, official filings, and operator publications referenced while researching this article.
- Google Search Central documentationdevelopers.google.com/search/docs
- Schema.org structured data vocabularyschema.org/
- Tier IV — open-source autonomous driving (Japan)tier4.jp/en/
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 →