# Cheapest Shanghai-Tokyo flight: ChatGPT admits it cannot see live fares, Manus scrapes airline sites, Sheet0 returns a table - no single tool won

ChatGPT Dots · Reddit · No income, no fare and no saving is disclosed. The original post does not say how the ticket was finally booked or by whom.

## Business summary

Reddit user u/Jetter057 documented a plain comparison test in r/ChatGPT. His prompt to ChatGPT: find all flights from Shanghai to Tokyo across platforms, list flight numbers, departure times, prices and luggage allowances, and identify the cheapest one. ChatGPT produced a route overview - common airlines, typical flight numbers, general departure patterns - and stated plainly that it cannot access live flight databases or fetch real-time prices. He then tried Manus, which can browse and interact with sites, asking it to check specific airline pages, and finally ran the exact same prompt through Sheet0, a data-extraction tool, which returned a structured spreadsheet. His verdict: no single tool won, and he ended up using all three in different places. The post stops there - it does not say how the ticket was finally booked or by whom, and this page does not infer it. No fare, no price difference, no saving and no subscription cost appears in the post. A collection-site summary mentions he said in a comment that Gemini with Google Flights felt more reliable; that comment was not retrieved this round, so it is not used anywhere on this page.

## Business value

This is a boundary case, not a saving story. What makes the author's account credible is that the first tool admitted it could not see live prices - far more useful than a confidently invented cheap fare. The portable lesson is his method: run the same request through three kinds of tools and compare which one helps at which stage, instead of waiting for one tool to do the whole job.

## Workflow

Write the request as a list of fields you will actually check, not as 'find me the cheapest flight'.

Ask for the route skeleton first and make the tool state whether it is general knowledge or live data. (The original post's ChatGPT answer included that admission.)

For live data, hand a specific site list to a browsing agent - not 'find it yourself'.

Feed the identical prompt to a dedicated extraction tool so the comparison is about the tool, not the wording. (What the author did with Sheet0.)

Any price field without a source site and a capture time is marked not retrieved. (AgentFlow's boundary; the original post has no such rule.)

Booking, payment and ID details stay with the person. (AgentFlow's boundary; the original post never reaches the booking step and does not say how the ticket was finally booked.)

## Preparation and limitations

The post contains no fares, no price differences, no savings and no subscription or token cost. It does not say which sites Manus actually reached, how many rows Sheet0 returned, whether any figure was verified against a booking page, or how the ticket was finally bought - the post simply ends after the comparison, and this page does not infer it. The comment referenced in the collection-site summary was not retrieved and is excluded. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Starter prompt

````text
You are my fare comparison assistant. You may organise route information, collect fields site by site and produce a candidate table. You do not log into any account, do not enter ID details, do not pay and do not book.

[INPUT]
- Route: [origin] to [destination], outbound [date or range], return [date or range]
- Constraints: [max stops / direct only / passengers / cabin]
- Fields I need: [e.g. flight number, departure and arrival times, total price including tax, baggage allowance, change rules]
- Sites to compare: [site list, e.g. airline site, two aggregators]

[STEPS]
1. Give a route skeleton from general knowledge: common carriers, typical flight number ranges, usual departure windows, rough duration. Open by stating this is general knowledge, not live data.
2. List the sites you will check and, for each, which fields you expect to get and which you will not.
3. Collect site by site, reporting each time: site / page / fields captured / blocked or missing.
4. Build a candidate table sorted by total price including tax, at most five rows.
5. Produce a gap table: which fields were missing on which sites, and why.

[OUTPUT]
1) route skeleton with the general-knowledge statement; 2) site list with obtainable fields; 3) candidate table with source and capture time per row; 4) gap table.

[NEEDS MY CONFIRMATION]
- Any price without a source and capture time is marked not retrieved; I decide whether to check it myself.
- Anything requiring login, ID entry or payment: stop and hand it to me.
- If you infer which option is better value, label it as inference and give the basis.

[IF MATERIAL IS MISSING OR A STEP FAILS]
Blocked site, anti-bot wall, missing field, unclear currency: put it in the gap table and say which step it blocks. Do not substitute a typical price from general knowledge, and do not reuse last run's data as this run's result.
````

## Costs and pitfalls

The post contains no fares, no price differences, no savings and no subscription or token cost. It does not say which sites Manus actually reached, how many rows Sheet0 returned, whether any figure was verified against a booking page, or how the ticket was finally bought - the post simply ends after the comparison, and this page does not infer it. The comment referenced in the collection-site summary was not retrieved and is excluded. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.

## Source and attribution

Jetter057（Reddit 用户 u/Jetter057，原帖作者本人，记录自己一次真实比价过程） (u/Jetter057)
https://www.reddit.com/r/ChatGPT/comments/1qyh4z6/i_asked_chatgpt_to_find_me_the_cheapest_flight/
2026-02-07
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
