Tours, Attractions & Layover Activities

Match activity intensity to jetlag recovery stage. Days 1-2 jetlagged = low-energy activities near hotel. Day 3+ adapted = major sites.

Search

• GET /api/airports/{code}/attractions — attractions near airport
• GET /api/airports/{code}/tours — curated tours by airport IATA
• GET /api/airports/{code}/activities — activities (adventure, wellness, classes)
• Layover tours: max 240 min, rating >= 4.0

Layover Intelligence

GET /api/v1/layovers/{code} — comprehensive layover data including:

• layoverGuides — time-segmented itineraries (4h, 8h, 24h) with activities
• dayUseHotels — nearby hotels bookable by the hour for layover rest
• airportSpas — spa and wellness services inside the airport
• connection — MCT and average wait times (feasibility check before suggesting off-airport activities)
• delays — historical delay stats (warn if airport has high delay rates)

Use layovers endpoint to check connection time feasibility before suggesting off-airport activities: if layover duration minus MCT minus 90min buffer > activity duration → suggest it.

Viator Is Affiliate

We provide booking URLs, NOT direct booking. Always include: price_from_usd, viator_rating, viator_review_count, duration_minutes, viator_booking_url

When to Suggest

• Layovers > 3 hours: airport-area tours (ensure duration + transit \x3C= connection - 90 min)
• Destination arrival: top-rated local attractions
• Recovery days: walking tours, cafes, parks
• Rain days: museums, food tours

Rate Limits

• Attractions/tours search: max 30/hr (Viator allows 60/min but self-limit).
• Only fetch when user asks or during trip planning — no pre-fetching all cities.

Data Sources — Tours & Activities

Primary: Aerobase Tours API (FREE, always query first)

• Internal tours/activities API with curated experiences
• Query by destination, category, price range, dates, duration
• Returns: activity name, description, price, duration, rating, booking link
• Covers major destinations worldwide

Secondary: Browser (supplementary discovery)

Use browser ONLY when:

• User asks about very niche/local activities not in our database
• User wants to compare prices with Viator, GetYourGuide, etc.
• User needs real-time availability confirmation

Workflow

1. User asks "What can I do in Tokyo for 3 days?"
2. Query Aerobase Tours API with destination=Tokyo
3. Present curated results by category: cultural, food, adventure, nightlife
4. If user wants more options: browse Viator/GetYourGuide via Google search
5. Always prefer our API results — better margins, curated quality

Scrapling — TripAdvisor Activity Discovery

TripAdvisor is in the scrapling tier (no proxy needed). Use for supplementary activity discovery:

Reference: Scrapling Documentation

web_fetch {SCRAPLING_URL}/fetch?url=https://www.tripadvisor.com/Attractions-g294217-Activities-Tokyo_Tokyo_Prefecture_Kanto.html&json=1&extract=css&selector=.listing_title

Returns extracted attraction titles. Replace the geo ID (g294217) and location path for other cities. Always prefer Aerobase Tours API first — use Scrapling TripAdvisor only for discovery of niche activities not in our database.

For UI rendering, see aerobase-ui SKILL for component specs.

When to SKIP browser entirely

• Almost always. Tours API is the primary and usually sufficient source.
• Browser only for edge cases: very niche activities, real-time availability checks
• Price comparison is rarely needed — our API has competitive pricing