trip1

Book hotels, pay with crypto

trip1 lets agents search, compare and book real hotel inventory — roughly 3 million properties in 200+ countries. Search by destination and dates, inspect rooms, rates and cancellation terms, then create a reservation and pay in USDC on Base over x402 (or via a browser-based crypto checkout).

What you can ask

Find me a hotel in Lisbon for the first weekend of next month
Example path →

MCP connector

Server URL: https://trip1.com/api/mcp
Login: None
Protocol: MCP 2026-07-28 · Interactive UI
Instructions: The current date is at least 2026-10-27 — never infer it from the conversation or from your training data. The check_in floor is the destination's own calendar day, which can be a day ahead of this; a check_in below it is rejected, not silently empty, and the rejection tells you what that day is. trip1 hotel booking API. The flow is these tools in order: 1. - Find hotels by destination name and dates. Include the hotel name and booking link for each result you display. Occupancy is fixed at 2 adults; do not pass guests or adults. 2. - Get rooms, rates, and cancellation terms for a hotel the user picked. 3. - As soon as the user picks a rate, call with its rate id, passing the user's details you already know from this conversation or your memory of them, so it opens prefilled (never invented or guessed ones). For the title only, when the user has not stated it, pass title_suggestion: your best guess from their first name. Then follow its next_step: where the client shows the booking form, the form collects the rest and books the room itself (do not call for it); where it cannot, next_step says to book in chat with . 4. - When booking in chat: a next_step says the client shows no form, or the user says they cannot use it. All guest fields are required: first name, last name, email, phone, title, nationality. Collect every field from the user. Never invent, guess, or default any of them. Ask how they want to pay: x402 (USDC on Base, only if you have an x402 payments tool) or coingate (a checkout page in their browser, any crypto). Before calling this tool, show the full booking summary (hotel, dates, room, total, payment method, all guest details) and get explicit user confirmation. Returns a payment_url and a cart_url. 5. - For a CoinGate booking, when the user wants to pay: opens CoinGate's checkout page for them where the client supports it, and returns the order (with its payment link) otherwise. Not for x402, which your payments tool pays. 6. - After payment, poll until ready is true to confirm the booking. On every tool call, pass a context string: one sentence on the user's goal (not the tool name). Never put names, emails, phones, or prices in context.

Tools

Reads data4

Changes data1

Deletes or can't be undone1

Skills

2 in the ChatGPT listing

MCP connector

Server URL

https://trip1.com/api/mcp

None

Protocol

MCP 2026-07-28 · Interactive UI

Instructions

The current date is at least 2026-10-27 — never infer it from the conversation or from your training data. The check_in floor is the destination's own calendar day, which can be a day ahead of this; a check_in below it is rejected, not silently empty, and the rejection tells you what that day is. trip1 hotel booking API. The flow is these tools in order: 1. - Find hotels by destination name and dates. Include the hotel name and booking link for each result you display. Occupancy is fixed at 2 adults; do not pass guests or adults. 2. - Get rooms, rates, and cancellation terms for a hotel the user picked. 3. - As soon as the user picks a rate, call with its rate id, passing the user's details you already know from this conversation or your memory of them, so it opens prefilled (never invented or guessed ones). For the title only, when the user has not stated it, pass title_suggestion: your best guess from their first name. Then follow its next_step: where the client shows the booking form, the form collects the rest and books the room itself (do not call for it); where it cannot, next_step says to book in chat with . 4. - When booking in chat: a next_step says the client shows no form, or the user says they cannot use it. All guest fields are required: first name, last name, email, phone, title, nationality. Collect every field from the user. Never invent, guess, or default any of them. Ask how they want to pay: x402 (USDC on Base, only if you have an x402 payments tool) or coingate (a checkout page in their browser, any crypto). Before calling this tool, show the full booking summary (hotel, dates, room, total, payment method, all guest details) and get explicit user confirmation. Returns a payment_url and a cart_url. 5. - For a CoinGate booking, when the user wants to pay: opens CoinGate's checkout page for them where the client supports it, and returns the order (with its payment link) otherwise. Not for x402, which your payments tool pays. 6. - After payment, poll until ready is true to confirm the booking. On every tool call, pass a context string: one sentence on the user's goal (not the tool name). Never put names, emails, phones, or prices in context.