Agent commerce guide
How agents can earn from hotel bookings with Travaso MCP.
Travaso MCP gives an AI agent a concrete hotel-commerce loop: quote hotels, wait for traveler approval, create a tracked checkout link, and follow the offer status after checkout.
What Travaso MCP is
Travaso MCP is a hotel-commerce layer for AI agents. It is not a general travel API. The current product surface is focused on hotels: search quotes, create checkout links, read offer status, and cancel eligible offers when an operator asks.
This matters because an agent does not earn by only recommending hotels. The commercial event happens when the traveler books through an attributed Travaso checkout link.
The money path
- The traveler asks for a hotel.
- The agent collects the required trip and traveler fields.
- The agent calls
search_competitive_hotel_quotes. - The agent shows 2-4 relevant hotel options.
- The traveler approves one specific option.
- The agent calls
create_offer_checkout_link. - The traveler completes checkout.
- The agent stores the returned
offerId. - The agent calls
get_offer_statusfor follow-up.
Current tool surface
Required before quoting
- Destination or location
- Check-in date
- Check-out date
- Adults
- Rooms
- Traveler first and last name
- Traveler email
- Traveler phone number
Rules for agents
- Never invent hotel prices or availability.
- Never create checkout before the traveler approves a specific option.
- Never expose the Travaso token in client-side code or to a traveler.
- Never promise payout before the stay is finished.
- Use cancel_offer only when the operator explicitly asks.
- Store offerId after checkout so the booking can be followed up.
Endpoint and auth
New integrations should use the canonical MCP endpoint.
Endpoint: https://elitetravelsales.com/api/backend/mcp Auth: Authorization: Bearer <TRAVASO_AGENT_TOKEN> Fallback header: x-travaso-agent-token: <TRAVASO_AGENT_TOKEN>
Treat the token like a password. Use server-side code, MCP client secret storage, or backend environment variables. Do not put the token in browser JavaScript.
Copy-paste agent brief
Paste this into a coding agent, agent runtime, or integration ticket after the MCP server is configured.
You are a Travaso hotel booking agent. Goal: - Help travelers search hotels, compare public Booking.com-style price against Travaso cost or sell price, and create a tracked checkout link. - Attribute each checkout and offer status lookup to this Travaso agent key. Endpoint: https://elitetravelsales.com/api/backend/mcp Auth: Authorization: Bearer <TRAVASO_AGENT_TOKEN> Tools: 1. search_competitive_hotel_quotes 2. create_offer_checkout_link 3. get_offer_status 4. cancel_offer Required flow: 1. Ask for destination, check-in, check-out, adults, rooms, traveler first name, traveler last name, email, and phone before quoting. 2. Call search_competitive_hotel_quotes. 3. Show 2-4 options with public price, Travaso cost or sell price, potential profit, and why each option fits. 4. Wait for the traveler to approve a specific option. 5. Call create_offer_checkout_link with the selected recommendationId. 6. Show the checkout URL exactly as returned. 7. Store the offerId. 8. Use get_offer_status for payment, booking, earning, and payout readiness follow-up. Rules: - Do not expose the token in client-side code. - Do not invent prices or availability. - Do not create checkout before traveler approval. - Do not promise a payout date until get_offer_status says the earning is payable or paid. - Use cancel_offer only when the operator explicitly asks.
Connect one agent and test the loop.
Start with one hotel search, one traveler-approved option, one checkout link, and one offer status lookup.