Waypad

Instructions for agents creating Waypad trips.

Waypad accepts structured trip JSON and turns it into a shareable itinerary URL. This page is for ChatGPT, Gemini, Claude, Codex, Cursor, and other agents helping a person plan a trip.

Fastest workflow

  1. Ask the user for destination, dates, preferences, budget, lodging, pace, and constraints.
  2. Create valid Waypad JSON using the schema below.
  3. Tell the user to open waypad.ing/new, paste the JSON, and create the trip.
  4. The resulting /trips/<id> URL can be opened on a phone.
Open importer View sample

Copyable prompt

Create a Waypad trip itinerary for me. Ask clarifying questions only if required. Return only valid JSON. Use this shape: { "trip": { "title": "Trip title", "startDate": "YYYY-MM-DD", "endDate": "YYYY-MM-DD", "timezone": "Area/City" }, "days": [ { "date": "YYYY-MM-DD", "title": "Arrival" } ], "items": [ { "date": "YYYY-MM-DD", "title": "Stop or transfer title", "itemType": "activity", "startTime": "09:00", "endTime": "10:30", "locationName": "Place name", "address": "Optional address", "notes": "Practical notes for the traveler" } ] }

Trip JSON expectations

trip.title: concise, human-friendly trip name.
trip.startDate / trip.endDate: ISO dates, like 2026-08-01.
trip.timezone: IANA timezone, like Asia/Taipei.
days[]: each day should include date and optionally title.
items[]: attach each item by date. Prefer useful times and practical notes.
itemType: use activity, lodging, transport, meal, or logistics.
locationName/address: include enough detail for maps and phone use.

Future direct tool path

The paste flow is the internal prototype path. Later, agents should use direct tools: create_trip, add_day, add_item, move_item, update_item, and validate_trip. For ChatGPT/Codex/Cursor this can be a remote MCP server. For Gemini API workflows this can be function calling against Waypad's API.