๐ค For AI agents
How assistants and other programs can use Edi's Resorts. Everything here is public; partner MCP credentials are issued privately.
Rules: answer only from our data (8 fictional resorts; nothing about other hotels, weather, flights or visas). Prices and availability come from the API and are re-checked in the cart. Demo only: no real payments; use the test card 4242 4242 4242 4242.
Machine-readable summary: /llms.txt ยท Full reference: integration guide
Search (Ask Edi)
Free-text search over resorts, rooms, experiences, events and extras with live availability and prices. Rules first; vague questions get a clarifying question; an AI model may only rank our own records.
curl -s -X POST https://resorts.edisprojects.com/api/v1/search -H 'Content-Type: application/json' \
-d '{"q": "spa weekend in February for two"}'Response: tier (rules | clarify | ai), filters, results (resorts, rooms, experiences, events, extras), bundles (with total_eur from the cart's pricing and add_items), clarify, not_in_data, focus + display (how many of each list to show before "Show more"). Follow-ups: send history (up to 4 earlier questions) and asked (clarify slots already asked). Limits per IP: 60 searches / hour; AI-ranked answers 10 / hour and 30 / day (HTTP 429 with Retry-After).
JSON API
# availability for dates
curl -s "https://resorts.edisprojects.com/api/v1/availability?check_in=2027-01-15&check_out=2027-01-18&season=winter"
# cart: create, add a search bundle in one call (all or nothing), check out with the test card
CART=$(curl -s -X POST https://resorts.edisprojects.com/api/v1/carts | sed 's/.*"cart_id":"\([^"]*\)".*/\1/')
curl -s -X POST https://resorts.edisprojects.com/api/v1/carts/$CART/items -H 'Content-Type: application/json' \
-d '{"items": [{"kind":"room","hotel_id":"velmora","room_id":1,"check_in":"2027-02-05","check_out":"2027-02-07","guests":2,"meal_plan":"BB"}]}'
curl -s -X POST https://resorts.edisprojects.com/api/v1/carts/$CART/checkout -H 'Content-Type: application/json' \
-d '{"first_name":"Test","surname":"Guest","email":"test@example.com","card_number":"4242424242424242"}'All read-only endpoints (resorts, facilities, availability, experiences, events, extras, offers, home) are listed in the integration guide.
MCP server
Streamable HTTP at https://resorts.edisprojects.com/mcp. Partner login: OAuth 2.1 with PKCE (S256), dynamic client registration; metadata at /.well-known/oauth-authorization-server. Without login: read-only tools search_resorts, get_resort, list_experiences, get_experience_slots, list_extras, list_events, list_offers and ask_edi (Ask Edi search, rules only, no AI model). Cart tools (create_cart, add_room, add_experience, add_extra, view_cart, remove_item, checkout, get_order, cancel_order; demo bookings, no card): with partner login, and without login when the operator enables public writes. Each cart result links to /cart/open/โฆ to finish on this website. Hosts with MCP Apps support show interactive cards (resorts, rooms, experience times, cart). With partner login also the older booking tools search_hotels, get_room_availability, create_booking, cancel_booking, list_bookings (deprecated).