Cheapest Shanghai-Tokyo flight: ChatGPT admits it cannot see live fares, Manus scrapes airline sites, Sheet0 returns a table - no single tool won
Jetter057(Reddit 用户 u/Jetter057,原帖作者本人,记录自己一次真实比价过程)Reddit · 2026-02-07
Read originalSaved text / editorial summary
原帖正文(Reddit r/ChatGPT,作者 u/Jetter057,Atom 源 updated 字段 2026-02-07;本轮经 Reddit 公开 Atom feed 取得,英文部分逐字未改写): “Like many of you, ChatGPT is my default tool for almost anything. So when I needed to book a flight, I figured I`d see how it handled a very practical task. I asked: "Help me find all the flights from Shanghai to Tokyo on all platforms, and list their flight numbers, departure times, prices, and luggage allowances. Also, help me identify the cheapest one." ChatGPT immediately understood what I was asking for and gave me a comprehensive overview of the route. It listed common airlines, typical flight numbers, and general departure time patterns. It was honest about its limitations. They can`t access live flight databases or fetch real-time prices. Next, I also tried something new for me, like Manus, which can actually browse the web and interact with sites. This felt like a significant step up. I could ask it to check specific airline websites, and it would navigate there and pull information. Finally, I tried Sheet0, which is specifically built for data extraction and structuring. I gave it the exact same prompt and let it run autonomously. Returned a perfectly structured spreadsheet with all the data I asked for. It`s a one-trick pony great at data extraction, but doesn`t have ChatGPT`s conversational depth At the end of the day, I don`t think any of these tools won. I actually ended up using all three in different ways lol” 中文对照:他先是给了 ChatGPT 一句完整的需求——找所有平台上的上海到东京航班,列出航班号、起飞时间、票价、行李额度,并指出最便宜的一班。ChatGPT 立刻给出航线概览,列了常见航司、典型航班号与一般起飞时段,同时坦白它连不上实时航班数据库、取不到实时价格。接着他试 Manus,让它去具体航司网站取信息;最后用同一句提示词跑 Sheet0,拿到一张结构化表格,评价是「只会一招,但抽取很强,没有 ChatGPT 那种对话深度」。收尾一句是:没有一个工具赢,最后三个他都在不同环节用了一点。
Business model
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.
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.)
Adaptation plan
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.
Prompt
AgentFlow draft · Untested.
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.
Running 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. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.