agent travel API / AI travel planner API
Use AICO before live provider fanout when an autonomous travel agent needs one API key to turn messy trip intent into strict constraints, produce a constraint-safe destination shortlist, attach live_places evidence where available, run itinerary validation before presenting options, and generate provider-ready hotel, flight, and place handoffs in stable JSON.
Activation path: POST /api/v1/activation → travel.intent.parse → travel.destinations.search → travel.places.search → travel.plan.validate → travel.provider_handoffs.generate. Matched first-value responses expose commercial_next_step; API-key agents can record POST /api/v1/commercial/intent → commercial_intent_requested before browser-authenticated billing, and POST /api/v1/api-requests captures missing primitives under agent_requested_api.
Concrete travel-agent jobs: messy trip intent into strict constraints; constraint-safe destination shortlist; live_places evidence context around a destination; itinerary validation before presenting options; provider-ready hotel, flight, and place handoffs.
Paid path: Hobby: $5 minimum usage/month with $5 credits included; pricing_model: "usage_token_minimum"; commercial_next_step.requires_browser_billing_account: true until a safe billing bridge exists.
Travel truth boundaries: live_booking_inventory: false, provider_backed_rates: false, live_flight_fares: false until a live provider verifies booking inventory, rates, taxes/fees, and fares; provider validation remains required for booking decisions.