TravasoMCP

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 lets an AI agent quote hotel rates, create checkout links, check reservations, and cancel eligible offers when the operator asks. The key used for checkout attributes the booking and earnings to its partner.

How much can an agent earn on a hotel booking?

Free earns 3% of positive booking margin. Monthly and Annual earn 10–20% of positive booking margin, depending on the offer. The traveler pays the rate shown at checkout.

Earnings begin as pending and become eligible for payout after a completed stay. Check the earning status in get_offer_status or the agent ledger. The booking key owner receives the earnings.

The money path

  1. The traveler asks for a hotel.
  2. The agent collects the required trip and traveler fields.
  3. The agent calls search_competitive_hotel_quotes.
  4. The agent shows 2-4 relevant hotel options.
  5. The traveler approves one specific option.
  6. The agent calls create_offer_checkout_link.
  7. The traveler completes checkout.
  8. The agent stores the returned offerId.
  9. The agent calls get_offer_status for follow-up.

Current tool surface

search_competitive_hotel_quotesSearch hotel options and return recommendationId values for checkout.
create_offer_checkout_linkCreate a tracked Stripe checkout URL after the traveler approves one option.
get_offer_statusCheck payment, booking, earning, payable, and paid status for an offerId.
cancel_offerCancel eligible offers only when the operator explicitly asks.

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.
  • Check for a booked or completed status before telling a traveler their hotel is confirmed.
  • 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 compare matching hotel offers and create a tracked checkout link after approval.
- 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 the traveler’s total, booking terms, and a comparable public rate when available.
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.
- Check get_offer_status to distinguish card payment from supplier confirmation and to verify payout readiness.
- Use cancel_offer only when the operator explicitly asks.
Next step

Connect one agent and test the loop.

Start with one hotel search, one traveler-approved option, one checkout link, and one offer status lookup.