Trip1 Hotel Booking

Landing page: <https://trip1.com/en/agents>;

Trip1 is an MCP server that exposes roughly 3 million hotels across 200+ countries. Agents search inventory, fetch rates, and book rooms through four tools. Payment runs inline over x402 on Base (USDC), with a CoinGate fallback URL for any client that lacks an x402-capable wallet.

When to use

Activate this skill any time the user intent involves lodging:

• "Find me a hotel in Lisbon for next weekend"
• "Book the cheapest place near Shibuya under $120"
• "I need three nights in Paris, two adults, flexible on area"
• "Is there a beachfront hotel in Phuket with availability Dec 20 to 27"
• Any trip-planning conversation that reaches the lodging step

Do not activate for flights, rental cars, restaurants, or activities. Trip1 only sells hotels.

Required setup

The user must have Trip1's MCP server connected. If the four tools (searchhotels, gethoteldetails, purchasehotel, getorderdetails) are not visible in the current session, stop and tell the user to add this to their MCP client config:

{
  "mcpServers": {
    "trip1": {
      "type": "http",
      "url": "https://trip1.com/api/mcp"
    }
  }
}

For the agent to pay on its own without a browser redirect, an x402-capable wallet MCP also needs to be loaded. The simplest option is Coinbase Payments MCP (npx @coinbase/payments-mcp). Without it, purchase_hotel will return a CoinGate URL the human finishes in a browser.

Booking flow

The happy path is five tool calls in order. Do not skip or reorder.

1. Search

Call search_hotels with:

• Destination as a plain city or area name. No lat/long.
• checkin and checkout in YYYY-MM-DD.
• Guest count.

If the user is vague on dates ("sometime in July"), pick a reasonable default (first weekend of the month) and state the assumption explicitly. If the user is vague on destination, ask one clarifying question before searching. Do not guess the destination.

Sort by price for budget-driven asks, rating for quality-driven, or distance when the user names a landmark or neighborhood.

Present results as a short list, typically 3 to 6, with name, price per night, rating, and a one-line location hint. Do not dump the full response.

2. Compare

When the user picks or narrows down, call gethoteldetails for that hotel ID. This returns rooms, rates, cancellation terms, and live availability.

Show the user a compact room list with nightly rate, total, refund policy, and the rate_id you will use for booking. Flag non-refundable rates explicitly.

If the user is still choosing between multiple hotels, call gethoteldetails for each and compare. Do not call purchase_hotel until the user has picked both a hotel and a specific rate.

3. Book

Before calling purchase_hotel, collect every guest field from the user. All of them are required:

• First name, last name
• Email
• Phone (e.g. +44123456789) — always ask, never default or invent
• Title (MR, MRS, MS, or MISS)
• Nationality (ISO 3166-1 alpha-2, e.g. GB, US, LT)

Do not invent values, do not reuse details from earlier in the conversation, and do not silently accept defaults. If a field is missing, ask.

Once all fields are collected, show the user a complete booking summary and get explicit confirmation before calling purchase_hotel:

• Hotel, check-in and check-out dates, room type
• Total price and currency
• All guest fields
• Cancellation terms (especially if non-refundable)

Only call purchase_hotel after the user confirms with something like "yes", "confirm", or "book it." If they push back on any field, correct it and re-confirm.

Pass rate_id from step 2 and the confirmed guest details. The response is one of two shapes:

• x402 challenge (default): the response includes a payment_url that returns HTTP 402 with a payment challenge. This is for agents with an x402-capable wallet.
• CoinGate URL fallback: the response includes a browser-openable checkout link. This happens when the server decides the client does not have x402 support or when x402 settlement is unavailable for the currency.

4. Pay

x402 path. Hand the payment_url to the loaded payments MCP tool. Do not ask the user to approve the transfer, and do not open a wallet UI. The payment completes inside the same request. If the payments MCP tool returns an error, surface the raw error to the user and stop. Do not retry blindly.

CoinGate path. Present the URL to the user with a short instruction to complete the payment in their browser. Do not try to pay on their behalf.

5. Confirm

After payment, poll getorderdetails with the order ID until ready is true. Backoff: 2 seconds, then 5, then 10, capped at 30. The supplier reservation reference appears in the response when the booking has cleared.

Report to the user with:

• Hotel name and address
• Check-in and check-out dates
• Guest name
• Total paid (amount and currency)
• Supplier confirmation reference

Things to get right

• Do not invent rates. Always quote what gethoteldetails returns, including currency. Prices in search results can drift from final rates.
• Cancellation matters. If the user asks about refunds, quote the cancellation terms returned by gethoteldetails verbatim. Do not paraphrase.
• Do not repeat an entire search response. Summarize and let the user ask for more.

When things fail

• No hotels found: widen the search (bump the radius, relax the star rating, extend the date range by one day on either side) and try again. Tell the user what you widened.
• Selected rate becomes unavailable during booking: rerun gethoteldetails and let the user pick a new rate. Do not auto-substitute.
• x402 payment fails: return the error to the user. Offer to fall back to the CoinGate URL if one is available in the purchase_hotel response.
• Order polling never flips ready to true: after roughly a minute of polling, report the order ID to the user and tell them to check status at https://trip1.com/en/cart/<signed id> or email support.

Tool quick reference

Links

• Landing: https://trip1.com/en/agents
• MCP Registry: https://registry.modelcontextprotocol.io (search com.trip1)
• x402: https://x402.org