Agents In Use
What’s new todayLast update
3 use cases added today

Grok Bot spots an unused flight and requests a refund

@SPYR0LAB reports a proactive Grok Bot finding an uncancelled flight in email, saying it was fully refundable and submitting a refund request after confirmation.

Source published x.comHow we sourceAgent: Grok Bot
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Check my travel emails for bookings I may no longer need. Explain any stated refund conditions and ask me to confirm before submitting a cancellation or refund request.

Evidence at a glance

Sourced account
Source poster / publisher
@SPYR0LAB
Original account
Read the source ↗
Published
Source link checked
Reported result
The poster reports a refund request submitted after confirmation. The capture does not establish a refund amount or that the money was received.
Human involvement
The poster set up the proactive bot and explicitly confirmed before it submitted the refund request. Wider email permissions are not described.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The poster set up a proactive Grok Bot that scanned their email.
  2. It reportedly identified an uncancelled flight the traveller was not going to take and said it was 100% refundable.
  3. After receiving confirmation, the bot submitted the refund request on the traveller's behalf.

@SPYR0LAB reports that a proactive Grok Bot found an uncancelled flight while scanning their email. The poster had set up the bot, and says it noticed a booking for a flight they were not going to take. The useful action began with finding an overlooked obligation rather than answering a new travel question.

The bot told the poster that the flight was 100% refundable. The account then identifies an explicit human checkpoint. After confirmation, the bot submitted the refund request on the traveller's behalf. It does not describe how the bot established the fare's refund eligibility or which airline or booking service it contacted.

The reported outcome is a submitted request, not money received. There is no refund amount, processing date or confirmation of settlement in the supplied text. The poster's statement that the bot paid for itself for the next 12 months is their assessment, not a documented price comparison.

This account supports email-based detection, an eligibility alert and a confirmation-gated submission. It does not establish unrestricted authority to cancel travel or a general policy for handling other bookings.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: X · @SPYR0LAB

Frequently asked questions

Did the bot ask before submitting the refund?

Yes. The poster explicitly says the refund request was submitted after confirmation.

Was the refund received?

The source reports submission of the request, not receipt or settlement of the refund.

How much was the refund?

The capture gives no amount. It says the bot identified the flight as 100% refundable.

More details

About this account

Grok Bot reportedly detected an overlooked booking in email, flagged its claimed refund eligibility and submitted a request after confirmation.

Used Scout's verbatim X public API capture, read live on 2026-10-31, with explicit permission to use it instead of opening X. Reviewed the supplied post text and author bio. Media and self-thread continuations were not reviewed. Results are the poster's report, not independently reproduced. The supplied bio and post do not identify affiliation with the agent's maker or promote an owned agent product. Suggested prompt written by Agents In Use; no exact task prompt is published in the capture.

Credit: @SPYR0LAB

Source published

Added to Agents In Use

Source checked

Tools and topics

Grok Bot · Email

Flight refunds · Email monitoring · Human approval

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.