This site includes itinerary viewing and publication. Changes made through this API appear under My Trips or My Plans here. The account, agent connections and publication controls use the same trip records. This does not synchronize a separate website.

triptina and your assistant

triptina is a website for recording trips you have taken, organizing future travel plans, and sharing itineraries with other travelers. Your assistant can help turn your descriptions and the sources you choose into a clear itinerary, then add details and make corrections with you.

The public website is triptina.com, the new name for NGL Trips. Existing accounts, itineraries and approved agent connections stay the same. Website links from ngltrips.com may forward to the new address; sign in there with your usual email. Existing /api/ addresses on the old domain continue to work without forwarding credentials. For a new production task, use the guide on triptina.com. An explicitly supplied trial or local site remains a separate destination.

Trips are recorded as you go. New itineraries are private and unpublished. You choose whether to publish a public version; exact dates, costs, personal notes and source evidence stay protected. Connecting an assistant to triptina does not give it access to your email, photos or files. You choose those sources separately.

Use this site’s address. Use the address the user supplied for the task. Different addresses may share records or hold separate collections; do not assume either or move between sites. Check the current capabilities: integratedWebsite: true means API-authored trips can be inspected under My Trips/My Plans, with publication controls on this same site. If false or absent, do not promise those pages. Photo processing requires imageBinding: true. Itinerary changes use the API; there is no manual itinerary editor. A localhost comparison is reachable only from that computer or an explicitly arranged local connection; a cloud-hosted assistant must explain when it cannot reach it.

Start with what this conversation can do

An assistant should first explain triptina briefly and relate it to the user's request. Then choose a path based on the tools and permissions actually available. Reading this page is not a connection and does not establish permission or the ability to record changes.

Discuss or prepare an itinerary

If you can read pages and talk with the user but cannot make authenticated HTTP requests, you can still help organize their ideas, describe how triptina works, and prepare an itinerary to hand over later. Be clear that nothing has been recorded in triptina yet. Do not begin a connection flow that your tools cannot complete.

A friendly response could be:

triptina gives your travel plans and past trips a home, with itineraries you can choose to share. I can help organize your trip here. I don't currently have a tool in this conversation that can record it on the site, but an assistant with API access can pick up our notes using this same guide. Your itinerary stays private until you choose to publish it.

Identify the supplied site when discussing where anything will be recorded; explain a separate test/comparison boundary when applicable. A tool limitation is not evidence that the website is broken or that Markdown cannot be read; describe the actual result, and do not insist on switching products when useful discussion can continue here.

Create or edit through the API

If your available tools can make HTTPS requests with the required methods, JSON/form bodies and authorization headers, follow the direct API instructions. The API base is this page's origin plus /api/foundations. An HTTP client can fetch the Markdown API guide directly.

With the user's permission, request a connection and provide a clearly labeled approval link. The user signs in on this website and chooses your access; you receive your own restricted access through the API. Users do not run terminal commands, copy API credentials, or share email sign-in codes with you. The API guide explains the separate email sign-in and connection-approval codes.

Once connected, create or revise the itinerary together and check what was actually recorded. Publication stays under the user's control: it is off for agents by default, and supporting versions let the user enable it separately for a connection. Check the current API permissions rather than assuming every deployment supports that option. Sharing-permission changes and permanently emptying the recycle bin remain human actions. Do not claim the connection grants access to any trip or source the user has not authorized.

Use an MCP connection when available

Planned; not available on this site yet. MCP could provide another way for compatible assistants to discover and use triptina tools. Do not invent a server address, offer a nonexistent installation, or treat the direct API approval link as an MCP connection. An assistant with HTTP tools can use the direct API now; other conversations can prepare content without claiming it was recorded.

Guidance for different assistants

Assistant How to choose a path
ChatGPT Chat Explain the website and help the user here. Inspect the tools available in this conversation before claiming you can connect or record changes; web reading alone is insufficient.
ChatGPT Work or Codex Use the direct API when your HTTP/network tools permit it. Handle technical requests yourself; the user only discusses the trip and approves access on the website. Explain an actual restriction if your environment cannot reach the API.
Claude Use the same direct API if your current environment has suitable HTTP tools. MCP is a planned alternative, not a requirement or an available triptina integration yet.
Muse Muse-specific integration and instructions are planned and have not been validated. Do not claim supported connectivity. The general tool-capability checks above still apply.

Product names alone do not establish which tools, connections or network permissions a conversation has. No agent should claim to have connected, saved changes or submitted feedback without a successful operation. Assistants with API access can also send redacted feedback when the served contract lists feedback submission, a maintainer queue is configured, and the user has approved feedback access. Otherwise they should explain the limitation without claiming a report was filed.

A simple next step

Tell your assistant about a trip, or try a fictional two-day itinerary. It should explain what it can help with now, identify where the result will live, and only ask you to approve a connection when it can carry out the work.