aerobase-travel（航空基地旅行）

Aerobase Travel Intelligence

You have access to the Aerobase travel API for jetlag-scored flight search and analysis.

Setup

Set your API key:

export AEROBASE_API_KEY="ak_..."

All requests use https://aerobase.app/api as the base URL.

Response Envelope

Every response wraps data in a standard envelope:

{
  "data": { ... },
  "meta": {
    "request_id": "req_abc123",
    "tier": "free",
    "calls_remaining": 7,
    "latency_ms": 142
  }
}

Errors return:

{
  "error": { "code": "VALIDATION_ERROR", "message": "..." },
  "meta": { "request_id": "...", "tier": "free", "calls_remaining": 9, "latency_ms": 12 }
}

Rate Limits

Free tier: 10 requests per hour. When calls_remaining reaches 0, wait until the hour resets.

Available Tools

1. Score a Flight

When the user describes a specific flight with departure and arrival times, score it for jetlag impact.

curl -s -X POST "https://aerobase.app/api/v1/flights/score" \
  -H "Authorization: Bearer $AEROBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "LAX",
    "to": "NRT",
    "departure": "2026-04-15T13:25:00-07:00",
    "arrival": "2026-04-16T15:40:00+09:00",
    "cabin": "economy"
  }'

Required fields: from, to (3-letter IATA), departure, arrival (ISO 8601 with timezone offset).

Optional: cabin (economy | business | first | premium_economy).

Response data:

Present to user: "This flight scores X/100 for jetlag (tier). You'd need ~Y days to recover. [strategies.arrival summary]"

2. Search Flights

Search for flights on a route and date, ranked by jetlag score.

curl -s -X POST "https://aerobase.app/api/v1/flights/search" \
  -H "Authorization: Bearer $AEROBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "SFO",
    "to": "LHR",
    "date": "2026-05-20",
    "max_stops": 1,
    "sort": "jetlag",
    "limit": 5
  }'

Required: from, to (IATA), date (YYYY-MM-DD).

Optional: return_date, max_stops (default 2), sort (jetlag | price | duration), limit (max 5 on free tier).

Response data is an array of flights:

Present to user: Show as a ranked list. Lead with the best jetlag score. Mention price if available. Highlight the score difference between best and worst option.

3. Airport Info

Get airport details including jetlag-relevant facilities, lounges, and transit options.

curl -s "https://aerobase.app/api/v1/airports/NRT" \
  -H "Authorization: Bearer $AEROBASE_API_KEY"

Response data:

Present to user: Highlight facilities that help with jetlag recovery (sleep pods, showers, daylight rooms). Mention lounge access options for layovers.

4. Route Intelligence

Get comprehensive route analysis between two airports including direct and connecting options.

curl -s "https://aerobase.app/api/v1/routes/LAX/NRT" \
  -H "Authorization: Bearer $AEROBASE_API_KEY"

Response data:

Each route includes: jetlag_score (0-100), stops, connections, total_distance_km, total_duration_minutes, recovery_days, segments.

Present to user: Start with timezone shift context ("This route crosses X hours"). Compare direct vs connecting options. Note that connecting flights sometimes score better when the layover breaks the circadian disruption.

5. Travel Deals

Browse jetlag-scored travel deals. Free tier returns up to 3 results.

curl -s "https://aerobase.app/api/v1/deals?departure=LAX&sort=value_score&limit=3" \
  -H "Authorization: Bearer $AEROBASE_API_KEY"

Query parameters:

Response data.deals array:

Present to user: Lead with value_score. Mention jetlag impact alongside price. Flag error fares prominently (they disappear fast).

Presentation Guidelines

1. Always mention jetlag score and recovery days - these are the primary differentiators.
2. Compare scores when showing multiple options. "Flight A scores 82/100 vs Flight B at 61/100 - that's a full day less recovery."
3. Highlight departure/arrival strategy - users want actionable advice, not just numbers.
4. Convert technical data to natural language - say "you'll cross 9 time zones heading east" not "timezone_shift_hours: 9, direction: east".
5. Context matters - a score of 70 on a 2-hour flight is unremarkable, but 70 on a transpacific route is excellent.
6. Use tier labels - "excellent", "good", "moderate", "poor", "severe" are immediately understandable.

Score Interpretation