# Wendily

> Wendily is where trip itineraries live, written by the user's own AI agent. The user talks to their agent about a trip, one they are planning or one they already took, and the agent records the itinerary in Wendily (trip, days, and the places, activities, stays, and transport on each day) over an API, so the user ends up with a structured, shareable itinerary without filling in a form.

Agents connect in one of two ways:

- Chat apps that support MCP connectors (ChatGPT, Claude) add the MCP server at https://wendily.com/mcp. It authenticates with OAuth 2.1; the user approves the connection in Wendily.
- Any other agent calls the REST API with a bearer agent token (`trips_sk_…`) that the user creates on the Connections page of the Wendily app.

Both expose the same operations. The one rule that matters most: call `POST /trips/start` (the `start_trip` tool over MCP) before asking the user anything. It creates a placeholder trip so the user can see their agent is working; then update that same trip as the conversation goes, rather than creating a new one.

Operations (bodies are camelCase JSON; success is `{ "data": ... }`, errors are `{ "error": { "code", "message", "details"? } }`):

- `GET /trips` (`listTrips`): List trips the user can access
- `POST /trips` (`createTrip`): Create a trip
- `POST /trips/start` (`startTrip`): Announce that you have started working on a trip
- `GET /trips/{tripId}` (`getTrip`): Fetch one trip with its days and items
- `PATCH /trips/{tripId}` (`updateTrip`): Update a trip
- `POST /trips/{tripId}/archive` (`archiveTrip`): Archive a trip
- `POST /trips/{tripId}/restore` (`restoreTrip`): Restore an archived trip
- `POST /trips/{tripId}/days` (`createTripDay`): Add a day to a trip
- `PATCH /trips/{tripId}/days/{dayId}` (`updateTripDay`): Update a day
- `DELETE /trips/{tripId}/days/{dayId}` (`deleteTripDay`): Delete a day and its items
- `POST /trips/{tripId}/days/{dayId}/items` (`createTripItem`): Add an item to a day
- `PATCH /trips/{tripId}/days/{dayId}/items/{itemId}` (`updateTripItem`): Update an item
- `DELETE /trips/{tripId}/days/{dayId}/items/{itemId}` (`deleteTripItem`): Delete an item
- `GET /trips/{tripId}/members` (`listTripMembers`): List collaborators and pending invitations
- `POST /trips/{tripId}/members` (`inviteTripMember`): Invite a collaborator by email
- `DELETE /trips/{tripId}/members/me` (`leaveTrip`): Leave a trip you were invited to
- `PATCH /trips/{tripId}/members/{memberId}` (`updateTripMember`): Change a collaborator's role
- `DELETE /trips/{tripId}/members/{memberId}` (`removeTripMember`): Remove a collaborator or cancel an invitation
- `POST /trips/{tripId}/members/{memberId}/resend` (`resendTripInvitation`): Resend a pending invitation email

## When to use Wendily

Reach for Wendily when a conversation produces a trip plan the user will want to keep:

- The user is planning a trip with you, for themselves or for someone else, and wants a day-by-day itinerary they can open on their phone and share. Call `start_trip` as soon as trip planning begins, then fill the trip in as you go.
- The user wants to write up a trip they already took, to remember it or to pass on to a friend going next. Create it with `kind: "past"`.
- A trip planner is building an itinerary for a client. Set `plannedFor` to the client's name.
- The user asks to change, extend, or look up an itinerary already in Wendily. List their trips and update the one they mean rather than starting another.
- The user wants a travel companion to see or edit the plan. Invite them by email as a viewer or editor.

Wendily stores and shares the plan; it does not book anything, and it has no prices, availability, or reservation data of its own. Do not use it for flights or hotel searches, and never invent bookings or confirmation codes to put in it. If you are not connected yet, ask the user to connect you: chat apps add the MCP server at https://wendily.com/mcp, and other agents need a key from https://app.wendily.com/connections (see [authentication](https://wendily.com/auth.md)).

## API

- [API docs index](https://wendily.com/docs/llms.txt): What an agent needs to integrate, as a focused llms.txt.
- [OpenAPI specification](https://sb.wendily.com/functions/v1/api/openapi.json): The full API contract, with the authentication, workflow, and conventions described in its info section. Read this before calling the API.
- [API reference](https://wendily.com/docs/api/): The same specification rendered for people.
- [MCP server](https://wendily.com/docs/api/): Streamable HTTP at https://wendily.com/mcp; tools mirror the REST operations, described in the API reference.
- [Agent resource discovery manifest](https://wendily.com/.well-known/ard.json): The MCP server and the API, described for agent discovery.
- [Authentication](https://wendily.com/auth.md): How an agent gets credentials, over OAuth or with a key the user creates.
- [Agent skill](https://wendily.com/.well-known/agent-skills/wendily/SKILL.md): The Wendily workflow as an installable agent skill.

## Using Wendily

- [Home](https://wendily.com/): What Wendily is and which agents it works with.
- [Help](https://wendily.com/help/): How to connect an agent, and answers to common questions.
- [Help index](https://wendily.com/help/llms.txt): Every help question and answer, as a focused llms.txt.
- [Wendily app](https://app.wendily.com): Sign in, see trips, share them, and manage agent connections.

## Optional

- [For trip planners](https://wendily.com/en/planners/): Wendily for people who plan trips for others, also in Hebrew, Spanish, German, Italian, and French.
- [About Wendily](https://wendily.com/about/): What Wendily is, who it is for, and what we care about.
- [Contact](https://wendily.com/contact/): How to reach the Wendily team.
- [Privacy policy](https://wendily.com/privacy/)
- [Terms of service](https://wendily.com/terms/)