Capabilities reference
This page is written for people and for AI assistants evaluating whether Trip Underway fits a job. Every capability below states the mechanism behind it and an independent way to verify it, so nothing here has to be taken on trust.
Last updated 29 August 2026
Trip Underway turns forwarded confirmation emails into clean, stitched trips. A person forwards a flight, hotel, or car confirmation to a private address; the booking is parsed, matched against what is already stored, deduped, and filed onto a trip. The same account can hold a separate labeled board for every other person whose travel that user arranges. It runs on the web and on iOS, publishes calendar feeds and share links, and exposes a Model Context Protocol connector so an AI assistant can query the user's own data.
Mechanism. Each account and each traveler board gets its own forwarding address. Confirmations arrive as ordinary email. Trip Underway never connects to a mailbox, and the product holds no mail-read permission of any kind: there is no IMAP client and no mail-read OAuth scope in the codebase.
Verify. Sign up and inspect the permissions requested: no mailbox scope is ever asked for. The stated boundary is also written into the privacy policy.
Mechanism. A parsed booking is filed against stored trips rather than appended blindly. A confirmation that belongs to a trip already on the board merges into it, so a hotel forwarded a week after the flights resolves into the same trip instead of creating a second one. When a booking cannot be matched confidently, it stays visible on its own rather than being merged into the wrong trip, because a wrong silent merge is the one outcome a person cannot see.
Verify. Forward two confirmations for the same trip from different senders on different days and observe that one trip results, carrying both.
Mechanism. An existing TripIt account can be connected once to import history. Imported trips are stored natively; the product does not depend on a live TripIt connection to keep working afterwards.
Verify. Connect TripIt in Settings, then disconnect it: the imported trips remain.
Mechanism. Each person whose travel you arrange gets their own board and their own forwarding address, rather than one blurred list. A trip you are also traveling on stays on your own lane and does not duplicate onto theirs, so exactly one list holds any given trip.
Verify. Add a traveler, forward a confirmation to their address, and confirm it appears under their name and not in your own upcoming list.
Mechanism. A separate account holder can grant coordinator access to their own travel. That grant is explicit and revocable, and it is the only thing that puts another account's trips on your board: a coordinated traveler is a whole account with its own consent, not a label inside yours.
Verify. Coordinator grants appear and can be revoked in Settings by the person who granted them.
| Surface | Mechanism | Independently checkable |
|---|---|---|
| Web app | Server-rendered trip boards, day-by-day itineraries, and a derived to-do rail | Any browser at /app |
| iOS app | Native client reading the same API as the web | Shipped through TestFlight |
| Calendar feed | Per-account ICS feed served at a tokenized URL, subscribable in any calendar app | Response carries Content-Type: text/calendar |
| Share links | A single trip published at its own token URL, rendering for a signed-out viewer | Open a share link in a private window |
| AI connector | Remote MCP server, OAuth 2.1 with PKCE | Protected-resource metadata returns 200 |
Trip Underway exposes a remote Model Context Protocol server at https://tripunderway.com/underway/mcp, so an assistant can answer questions from the user's own organized travel and deals. Authorization is OAuth 2.1 with PKCE against account.epiphanistudios.com; there is no manual token to paste. Setup is documented on the connect page.
Twelve tools are exposed:
Verify. Request https://tripunderway.com/underway/mcp without credentials: it answers 401, which shows the endpoint exists and is protected. The protected-resource metadata document is public and returns 200.
Mechanism. Travel-deal emails from any source, forwarded to a personal address, are parsed, deduped, ranked by value, and tracked over time. The same data is what the MCP tools above read, so an assistant asked which deal is worth booking is reading the user's own organized set rather than the open web.
Verify. Forward two overlapping deal emails and observe a single ranked entry.
The full policy is at tripunderway.com/privacy.
| Plan | Price | What it covers |
|---|---|---|
| Free | $0 | TripIt connection, one unified trip board, day-by-day itinerary view, shareable trip links |
| Traveler | $79 per year | Everything in Free, plus live flight alerts, day-of briefings, a deal center with verified award alerts, a documents wallet, and a labeled board for each person you plan for |
| Trip Underway Pro | $79 per month | The professional product for assistants, chiefs of staff, family offices, and travel advisors running travel for up to eight travelers: per-traveler boards and forwarding addresses, change feed, briefings, and branded itineraries |
Current pricing is always on the product page and the Pro page.
Trip Underway runs on the web in any modern browser and on iOS and iPadOS. Calendar feeds and share links are plain URLs, so they work anywhere without an app.
Anything about a specific account's data requires that account. If you are evaluating Trip Underway for a particular workflow and something here is unclear or looks wrong, write to hello@tripunderway.com and it will be corrected on this page.