Grok Bot books and pays for Shibuya Sky tickets at release
Kevin reports that Grok Bot collected the required names and passport numbers upfront, then booked and paid for Shibuya Sky tickets as new slots opened after 2 days of unsuccessful attempts himself.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Help book Shibuya Sky tickets when new slots open. Ask for required details beforehand and agree the spending and purchase-approval boundaries with me.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @KevinVaghasiya5
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Kevin reports that Grok Bot booked and paid for the tickets when new slots opened. He does not give a ticket price, payment method or visit outcome.
- Human involvement
- Kevin supplied the booking task and the requested personal details. The capture does not specify a spending limit, payment setup or final confirmation step.
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
- After 2 days of unsuccessful attempts, Kevin asks Grok Bot to book Shibuya Sky tickets in Tokyo.
- The bot asks for required details upfront, including names and passport numbers.
- When new slots open, the bot reportedly books and pays for the tickets right away.
Kevin reports turning to Grok Bot for Shibuya Sky tickets in Tokyo after 2 days of unsuccessful attempts himself. He says popular time slots sell out in seconds. The account describes a booking attempt prepared in advance for the moment new slots became available.
Before the release, Grok Bot asked for the information it needed, including names and passport numbers. That preparation matters to the reported workflow because the agent did not wait until slots opened to request those details. The capture contains no actual passport numbers or other travellers' identifying information.
Kevin says the bot booked and paid for the tickets right away when new slots opened. This is his report of a completed purchase, not an independently checked booking. The post does not give the ticket price, number of tickets, payment method or the particular time slot obtained.
The supplied bio promotes Kevin's own SaaS work, but this post describes his use of Grok Bot rather than that product. It establishes neither an affiliation with Grok Bot's maker nor the payment permissions used. There is no account of the eventual visit or of a separate approval step before purchase.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @KevinVaghasiya5
Frequently asked questions
What did the bot request upfront?
Kevin names traveller names and passport numbers among the details requested before new slots opened. No actual personal details are reproduced.
Did the bot complete the purchase?
Kevin reports that it booked and paid for the tickets right away when new slots opened. No booking receipt was reviewed.
What were the cost and payment permissions?
The capture does not give a ticket price, payment method, spending limit or final approval process.
More details
About this account
Kevin attributes collecting booking details and executing the ticket purchase when slots opened to Grok Bot. The monitoring method is not described.
Scout supplied verbatim X public API captures read live on 16 November 2026 at approximately 19:30 UK and explicitly authorised their use instead of opening X. Claims are limited to that text. Linked media were not reviewed and outcomes were not independently reproduced. The supplied bio was screened for maker affiliation and own-product promotion. Prompt: Suggested by Agents In Use, not quoted from the source.
Credit: @KevinVaghasiya5
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot
Ticket booking · Tokyo · Timed availability
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.