Agent Infrastructure Co

Agent-native API

# Travel API

Travel workflow infrastructure for agents. Use one API key to interpret messy trip intent, enforce hard constraints, shortlist destinations, inspect provenance and live_places evidence where available, validate an itinerary, then generate provider-ready hotel, flight, and place handoffs before spending browser or live-provider calls.

[ /activate ][ /openapi.json ][ /mcp ][ /cli ]

## What it does

Returns branchable fields like match_status, bookability_status, source/provenance, provider_handoffs, confidence, and unsupported_constraints so agents can decide whether to continue, stop, or hand off.

beta_warnings, interpreted_constraints, constraint_conflicts, match_status, truth_boundaries, confidence, booking_readiness, provider_handoffs, provider_handoffs.required_external_checks, flight_handoff, hotel_handoff, required_external_checks, bookability_status, bookability, candidate_intent_coherence, requires_live_validation, live_search_or_booking_provider, google_aggregator_signals, aggregator_fare_snapshots, hotel_rate_snapshots, not live airfare, not provider-backed rates, not booking inventory, unsupported_constraints, why_not_bookable_yet, intelligence_basis, remote_work_fit, remote_work_snapshot, not live internet measurement, family_fit, family_snapshot, party-size costing, event_fit, event_snapshot, curated_baseline, model_estimate, research_handoff, handoff_required, accessibility_snapshot, visa_stay_snapshot, multi_city_snapshot

## Why agents call it

It saves tool calls and failure modes versus scraping search pages: strict constraint gates, stable JSON, provenance tiers, and provider-ready next steps in one response.

## Realistic travel-agent jobs

messy intent → constraints

Turn a human request like ‘NorCal redwoods, coast, food, hiking, recovery’ into hard geography/themes, dates, budget, and strict_mode.

constraint-safe shortlist

Return in-scope destination candidates instead of drifting into popular but off-scope places.

place context

Attach live_places evidence where available so agents can reason about what is near the destination.

itinerary validation

Check whether the proposed plan satisfies hard constraints before the agent presents options to a user.

provider-ready handoffs

Generate hotel, flight, and place search parameters so the next tool/provider call starts from normalized intent instead of re-parsing the trip.

## Primitive chain

intent.parse

Normalize messy travel intent, hard constraints, conflicts, and unsupported requirements before ranking.

destinations.search

Return in-scope destination candidates or a structured no_match branch instead of off-scope filler.

places.search

Attach live_places evidence where available without pretending it is booking inventory.

plan.validate

Check proposed plans for date, theme, constraint, and truth-boundary coherence.

provider_handoffs.generate

Prepare flight, hotel, and place handoff params for downstream live-provider fanout.

## Quickstart

export AICO_TRAVEL_KEY="paste-key-here"

curl https://agentinfrastructureco.com/api/v1/travel/search \
  -H "$(printf '%s %s' 'Authorization:' "Bearer $AICO_TRAVEL_KEY")" \
  -H "Content-Type: application/json" \
  -d '{
    "user_request": "Northern California Memorial Day trip from SFO with redwoods, coast, food, hiking, and recovery.",
    "origin": "SFO",
    "departure_window": ["2026-05-22", "2026-05-25"],
    "trip_length_days": 3,
    "budget_usd": 2500,
    "destination_constraints": [{ "type": "region", "value": "Northern California", "hard": true }],
    "required_themes": ["redwoods", "coast"],
    "strict_mode": true
  }'

## Provider validation still required

live_booking_inventory: false until a provider verifies rooms for the dates and party
provider_backed_rates: false until provider rates, taxes, and fees are returned
live_flight_fares: false until current airfare is verified
bookability_status: handoff_required for matched beta candidates

## After first value

Matched first-value responses can include commercial_next_step with the response request_id and checkout_source_path.
Record shell-agent paid intent with POST /api/v1/commercial/intent; the event is commercial_intent_requested and requires_browser_billing_account stays true for browser-authenticated checkout.
Hobby: $5 minimum usage/month with $5 credits included; Pro: $20 minimum usage/month with $20 credits included; pricing_model: "usage_token_minimum".
If adoption is blocked by a missing primitive, call POST /api/v1/api-requests and track roadmap_bucket: agent_requested_api instead of guessing from silence.

[ deploy with hobby ]