About Traveler.md

Memory that travels with the traveler.

Traveler.md is a markdown file that records how one person travels: their style, pace, and budget, their loyalty programs, their flight and accommodation preferences, their favorite activities, their dealbreakers, and the trips they are dreaming about. The traveler owns the file. Any AI agent they authorize can read it and write approved updates back.

Trip.md is the companion format, one document per trip. A trip file starts broad, such as “Mediterranean in July or August”, narrows to dates, a shortlist, and neighborhoods, and ends as a record of the bookings, the notes, and what the traveler loved.

Traveler.md is who the traveler is. Trip.md is what they are planning. Traveler.md vs Trip.md compares the two in detail.

The point is portability. The same memory follows the traveler across booking sites, assistants, and agents, instead of being re-entered in each one. That is also why it is worth keeping current: it works in every tool the traveler uses, not just the one that collected it.

What it changes for an agent

An agent connected to a traveler’s memory is different in four specific ways.

• Helpful from the first message. It already knows the traveler’s pace, taste, budget, and constraints, so the first answer is a real recommendation instead of a round of questions.
• Aware of the active trip. It reads Trip.md, so it picks planning up where it left off instead of restarting it.
• Working from more than a search bar can hold. How fast does this traveler like to move? Boutique hotel or full-service resort? Walkability, design, food, or luxury? What did they love or avoid last time? A destination and a date range carry none of that.
• Sharper each conversation. What the agent learns flows back to the profile with the traveler’s permission, so the next session starts further along.

If you are building an agent, Agent instructions has the call sequence and the cases where reaching for the memory is the right move.

Who publishes this

TravelAI publishes Traveler.md and this documentation. The legal entity is TravelAI Solutions Inc., which does business as TravelAI, in Pitt Meadows, British Columbia, Canada. TravelAI builds travel infrastructure for other companies to build on. The company site is travelai.com . The product site is traveler.md .

This documentation site is public. Every page is available as markdown as well as HTML. See For agents below.

What exists today

The file formats. Traveler.md and Trip.md are documented in full under Get Started. Both are plain markdown. A traveler can read and edit either one by hand.

The MCP (Model Context Protocol) server. The server at https://mcp.traveler.md/mcp gives an authorized agent scoped access to a traveler’s files. It exposes eight tools over the Streamable HTTP transport. It uses OAuth 2.1 with PKCE for authorization. The MCP server overview describes it, and the guides connect it to a specific client in a few steps.

Scope of the MCP server: travel memory only. The server stores what a traveler has said about how they travel, and the trips they are working on. It has no inventory behind it, no prices, and no availability. It returns no shortlists and no recommendations. The connected agent still does the recommending. The memory changes whose preferences that recommendation is built on.

Traveler control. The traveler decides what is shared and with which tool. They can revoke any tool at any time from their account, and an audit trail shows what happened. Revocation and scope narrowing take effect on the next call, with no grace window.

No deletion on the MCP surface. Nothing the server exposes can delete a trip. Archiving is the strongest write, and the traveler can reverse it from their account.

Product stage

Traveler.md is a public beta.

Request early API access  to be told when the REST API opens up. Anything on this site described as in development is exactly that, and is not a commitment to ship.

For agents

Read Agent instructions for when to reach for Traveler.md and how to call it. Other machine-readable files on this site:

Append .md to any page URL to get its markdown source. Sending Accept: text/markdown does the same thing.

Contact

See Contact for the address to use for support, security reports, and partnership questions. See Privacy for what the MCP server stores and what it does not.

Travelers who want to start using Traveler.md can sign up free at app.traveler.md .