Launching today

Trip1 MCP + x402

Launching today

Book hotels over MCP. Pay over x402.

2 followers

Book hotels over MCP. Pay over x402.

2 followers

Visit website

Trip1 MCP server lets AI agents book hotels and pay with USDC on Base via x402. 3M+ hotels, settled on-chain in seconds. Works with Claude, ChatGPT, and any MCP client.

Free

Launch tags:Crypto•Travel•Artificial Intelligence

Launch Team

Intercom — Startups get 90% off Intercom + 1 year of Fin AI Agent free

Startups get 90% off Intercom + 1 year of Fin AI Agent free

Promoted

Maker

📌

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.

Report

3d ago

Forum Threads

p/trip1-mcp-x402

•

3d ago

AMA: building an MCP server with x402 payments

I built Trip1 MCP and spent the last few months getting x402 to work end to end for hotel bookings. Happy to take questions on any of it.

Things worth asking about:

How the x402 handshake actually runs inside an MCP tool call
Why we settled on Base and USDC
Supplier side: how a real hotel inventory system takes a transfer that wasn't signed by a human
What breaks when an agent doesn't have a wallet loaded
Why MCP rather than a REST API with API keys
What I'd change about the x402 spec if I could

Drop a question, I'll work through them.

p/trip1-mcp-x402

•

3d ago

What would you actually want an agent to book for you?

Hotels was an obvious first target for us, but I'm curious what else people would let an agent spend money on without them watching. Flights. Concert tickets. Groceries. A dentist appointment. A specific GPU hour on some obscure cloud.

p/trip1-mcp-x402

•

3d ago

How the x402 handshake fits inside a single MCP tool call

Short version of how purchase_hotel works end to end:

Agent calls the tool with a rate ID and guest details.
Server returns HTTP 402 with a payment challenge (amount, recipient, expiry).
Agent signs a USDC authorization on Base. No wallet UI, no user involvement.
Agent retries the same tool call with the signature attached.
A facilitator submits the transfer on-chain. It settles in ~2 seconds.
The server continues the booking inline and returns a confirmation.

View all