About Traveler.md

What we build

Traveler.md gives a traveler two plain-language documents they own. traveler.md is a persistent profile of how they travel: style, pace, budget, loyalty programs, seat and hotel preferences, dietary and accessibility needs, dealbreakers, and dream trips. trip.md is one file per journey, which starts as a loose idea and ends as a complete record of what was booked and what they loved.

Any AI assistant, agent, or travel service the traveler authorizes can read those files and write approved updates back. The traveler grants access per scope, sees an audit trail, and can revoke any tool at any time. Nothing is shared by default.

Why

Personalization in travel is fragmented. Every booking site, assistant, and loyalty program keeps its own thin slice of a traveler, and none of those slices travel with the person. So every new tool starts from zero and asks the same questions again. Our position is that the profile should belong to the traveler, live in a format both people and models can read, and move between services under the traveler’s control. The long-form argument is in the vision paper.

Where each part stands

Traveler app

Public beta at app.traveler.md. Sign-up is self-serve and free for individual travelers.

MCP server

Live at https://mcp.traveler.md/mcp, with OAuth 2.1 authorization and per-scope consent. Setup guides are in the developer documentation.

REST API

Pre-launch. We are working with a small group of early builders. Request access on the developers page.

Advisor portal

In early development. Beta advisors get hands-on onboarding. See for travel agencies.

Company and contact

Legal entity

TravelAI Solutions Inc. (dba TravelAI)

Registered address

11528 198 Street, Pitt Meadows, BC, V3Y 1N9, Canada

Privacy and data requests

privacy@travelai.com

Partnerships and API access

partnerships@traveler.md

Company site

travelai.com

For agents

This site publishes an agent guide at /llms.txt and an OpenAPI 3.1 description of the live agent surface at /openapi.json. Every page also serves a markdown representation: send Accept: text/markdown, or append .md to the path.