Amtrak, Greyhound & Megabus Scraper — US Intercity Rail & Bus

Compare US intercity travel in one normalized dataset. The Actor returns scheduled Amtrak trains and live fare snapshots from the public Greyhound and Megabus booking flows.

What it returns

• Departure and arrival times, duration, transfers, stops, service/carrier, and booking link
• Live Greyhound and Megabus price snapshots, currency, availability hints, and amenities when exposed
• Amtrak scheduled services from Amtrak's official GTFS feed
• Multiple routes and provider selection in one run
• A machine-readable OUTPUT summary with per-provider counts and warnings

Important Amtrak limitation

Amtrak does not offer a public self-service booking/fare API for this use case. This Actor therefore uses Amtrak's official public GTFS schedule feed and does not claim Amtrak fares, seat inventory, or real-time availability. Amtrak price, currency, and seatsLeft are null, while availability is scheduled.

Input example

{
  "routes": [
    { "origin": "New York, NY", "destination": "Boston, MA" },
    { "origin": "NYP", "destination": "WAS" }
  ],
  "providers": ["amtrak", "greyhound", "megabus"],
  "dateOffsetDays": 7,
  "adults": 1,
  "maxResults": 50,
  "currency": "USD"
}

Set date on an individual route as YYYY-MM-DD, or omit it and use dateOffsetDays. Relative dates make saved Tasks and scheduled runs evergreen. Bus origins accept common city names. Amtrak origins work best as station codes such as NYP, BOS, WAS, PHL, CHI, and LAX.

Output example

{
  "id": "53aad3c4862936950c4df068",
  "provider": "greyhound",
  "mode": "bus",
  "origin": { "name": "New York, NY", "code": "US-NY", "id": "...", "stopName": "...", "stopId": "..." },
  "destination": { "name": "Boston, MA", "code": "US-MA", "id": "...", "stopName": "...", "stopId": "..." },
  "departureTime": "2026-09-16T08:30:00-04:00",
  "arrivalTime": "2026-09-16T12:50:00-04:00",
  "durationMinutes": 260,
  "transfers": 0,
  "price": 34.99,
  "currency": "USD",
  "bookingUrl": "https://shop.greyhound.com/search?..."
}

Pricing

Pay per event: $0.005 when a run starts and $0.003 per trip record written to the default dataset. For 50 records, event charges are about $0.155. The Actor stops at maxResults and honors the Apify maximum total charge limit. Platform prices can be reconfigured by the owner before publication.

Reliability and responsible use

The Actor reads public, page-owned carrier data and uses bounded retries and timeouts. Carrier inventory and fares can change between scraping and booking. It does not purchase tickets, access accounts, solve CAPTCHAs, or bypass access controls. Use results in accordance with carrier terms and applicable law, and verify important details on the booking page.

API

Run the Actor with the Apify API, CLI, schedules, integrations, or MCP. Results are in the default dataset; the OUTPUT key contains run diagnostics. Invalid routes are skipped with actionable warnings and no fabricated dataset rows.