How to use ChatGPT agent to book a Shinkansen
ChatGPT agent entered a Tokyo–Shin-Osaka rail reservation, paused for human login and payment permission, and reportedly completed booking in KEITO’s demo.
note.com
Original prompt
Shared by the source author. See source notes for context.
東京から新大阪までの新幹線を予約する
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- KEITO｜AIディレクター
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- KEITO reports a completed Shinkansen reservation through the agent, with login and booking screenshots; actual travel and exact fare are not established.
- Human involvement
- The human handled authentication and authorized the consequential payment stage; no fully unattended purchase is inferred.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The owner requested a Tokyo-to-Shin-Osaka reservation and let the agent open the booking website.
- The agent entered route and date information, then paused for the owner to authenticate.
- The account describes payment permission and reports successful booking with a completion screenshot.
KEITO tested ChatGPT agent on a Tokyo-to-Shin-Osaka Shinkansen reservation. The publicly readable part of the Japanese account describes the actual browser sequence and reports a completed ticket booking, with screenshots illustrating the handoffs.
The agent opened the reservation website and entered the travel date and route. Once authentication was required, it paused and returned control to the human instead of treating login as information it could invent. The account then describes permission before the consequential card-payment step and shows a booking-completion image.
KEITO’s assessment is qualified: manual operation can still be faster in some situations. The browser run also served as a way to understand how an unfamiliar reservation website works. A visible sequence of navigation, authentication and completion mattered more here than a claim that the entire journey was unattended.
The exact ticket price, departure time and elapsed duration are not published in the verified free section. A reservation is reported, but the article does not establish that the train journey was subsequently taken. Other research and document demonstrations on the same page are not counted as additional use cases.
Prompt
Original prompt
Source: note · KEITO｜AIディレクター
Frequently asked questions
What route was requested?
The published demonstration requests Tokyo to Shin-Osaka.
Who handled the login?
The agent paused and handed the browser to the human for authentication.
Does the source prove that using an agent was faster?
No. The author explicitly says manual operation can still be faster in some situations.
More details
About this account
The owner requested a Tokyo-to-Shin-Osaka reservation and let the agent open the booking website. The agent entered route and date information, then paused for the owner to authenticate.
Public primary Japanese section opened and read; paywalled material was not used. Original task excerpt. Booking is author-reported with screenshots; no price, duration or completed train journey is invented. Original prompt excerpt.
Credit: KEITO｜AIディレクター — note
Source published
Added to Agents In Use
Source checked
Tools and topics
ChatGPT agent · Virtual browser · Rail booking website
rail booking · login takeover · payment permission
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.