Agent-ready travel planning

Facts to plan with. A safe action to take.

Alaska Fishing Match publishes structured destination, trip-format, seasonal, and decision-guide data for assistants, plus one consent-based action: create a non-binding fishing, basecamp, and logistics request for human review.

Public planning catalogGET /api/tripsDecision guidesGET /api/planning-guidesTrip-format schemaGET /api/trip-formatsAction descriptionGET /openapi.jsonTrip match requestPOST /api/trip-requests

Usage contract

What an assistant should know

01

Planning, not live inventory

Destination, decision-guide, and trip-format data helps narrow the trip. It does not claim that a specific guide, price, or date is available.

02

Consent before action

The traveler must review the trip brief and explicitly approve submission before an assistant calls the request endpoint.

03

A request is not a booking

No payment is collected and no reservation is created. A human planner reviews the request before any guide or lodging introduction.

04

Safe retries

Use an Idempotency-Key header. Repeating a request with the same key returns the original request instead of duplicating it.

05

Regulations remain authoritative

Season guidance is descriptive and date-stamped. Current ADF&G regulations and emergency orders always supersede it.

Planning for a traveler?

Use the catalog. Confirm the brief. Request the match.

Humans can use the same matching workflow when they want to review or refine the answers themselves.

Open human matcher