Trip1 MCP + x402 - Book hotels over MCP. Pay over x402.

Hey, Tomas from Trip1. Trip1 is a hotel booking site. Bookings get paid in crypto through CoinGate and settle directly with the supplier. A few months ago agents started showing up on the site. They'd run through the search fine, then hit the checkout and freeze. The CoinGate step assumes someone is about to open a wallet and confirm, which an agent can't do, so it stalls. Building a second checkout meant for programs became the obvious thing to do. The MCP server exposes the same inventory as four tools: search_hotels, get_hotel_details, purchase_hotel, get_order_details. It's the same 3 million hotels across 200+ countries we already sell to humans, with the booking call returning rate IDs an agent can hand back when it's ready to pay. Payment runs over x402. x402 is an open protocol that uses HTTP 402 for programmatic billing. The agent calls purchase_hotel and the server responds with a 402 and a payment challenge. The agent signs a USDC authorization on Base and retries the same request. A facilitator pushes the transfer on-chain, it settles in roughly two seconds, and the booking continues inline. If the agent doesn't have an x402 wallet loaded, the tool returns a CoinGate URL instead and a person can finish it in a browser. The part I thought about longest was whether to extend the existing human checkout or build a second one. I tried extending first. It produced worse code on both sides, because the two flows share almost nothing once you account for session, UI, and signing. So the MCP path is its own code path that talks to the same inventory and order systems underneath. Config looks like this: { "mcpServers": { "trip1": { "command": "npx", "args": ["-y", "mcp-remote", "https://trip1.com/api/mcp"] } } } It works with Claude, ChatGPT, or any MCP client. For the wallet side, Coinbase Payments MCP is the easiest option and you can load it alongside Trip1. Ask me anything about how the x402 handshake works, the supplier integration, or why this is MCP rather than a REST API.