Contact
Pick the address that matches what you need. Every address below is monitored by TravelAI.
| Reason | Address |
|---|---|
| Bug report or unexpected error | support@traveler.md |
| Security issue | support@traveler.md |
| Partnership or integration question | partnerships@traveler.md |
| Privacy request or data question | privacy@travelai.com |
| Early access to the developer API | Join the API waitlist |
Travelers who want an account do not need to write to anyone. Sign up free at app.traveler.md . Account creation is self-serve.
Before you write
Check Debugging first. It covers the errors that come up most often, including a failed OAuth flow and a rejected tool call. Authentication covers token lifetimes, scopes, and revocation.
What to include in a bug report
Send these four things. They cut a round trip out of the exchange.
- The client you are using: Claude, ChatGPT, Cursor, OpenClaw, Hermes, or a custom agent.
- The tool that failed, if you know it. The eight tool names are listed in Tools.
- The error message, copied exactly as you saw it.
- The approximate time it happened, with a timezone. This lets us find the request in the logs.
Do not include a traveler’s personal data, an access token, or a refresh token in an email. Redact them first. If you believe a token has been exposed, revoke the connection from Connections on traveler.md and say so in the message.
Reporting a security issue
Email support@traveler.md. Do not open a public issue and do not post the details anywhere public before we reply. Describe the behavior you found and the steps that reproduce it.
Postal address
TravelAI Solutions Inc., doing business as TravelAI 11528 198 Street Pitt Meadows, BC V3Y 1N9 Canada
Post is slow. Use email for anything that needs an answer.
Related pages
- About Traveler.md covers what exists today and what is still pre-launch.
- Privacy covers what the MCP (Model Context Protocol) server stores.
- Support holds the frequently asked questions.