Railway 12306 Train Ticket Query

The Problem

Train ticket lookups often stall on practical details: whether G and D services are separated, whether seat availability is current, whether dates are easy to enter, and whether each result includes a booking entry point. This skill targets that query workflow. It connects 12306 official data through a FliggyAI proxy, so natural-language input can return train numbers, fares, timetables, seat availability, and booking links.

How It Works

• Data path: user input → Python script → Tencent Cloud SCF proxy → FliggyAI → 12306 official data.
• Core coverage: supports G/D/C/Z/T/K train types and distinguishes G-series high-speed rail, D-series trains, and conventional services.
• Query scope: returns origin/destination cities, fares, timetables, and seat availability such as business, first class, second class, hard sleeper, and soft sleeper.
• Input handling: accepts natural-language dates like “tomorrow”, “the day after tomorrow”, and “next Friday”.
• Result format: each train includes a booking link for the purchase flow.

Boundaries

• It does not buy tickets, inspect purchased tickets, or process refunds.
• Seat availability depends on the 12306 API and may fall back to fare reference data if unavailable.
• Use Chinese city names where possible, and refresh to retrieve the latest availability.