Top Sites>A perfect getaway to Crete Greece - Corissia Resorts

User-agent: *
Allow: /.well-known/
Allow: /hotels/sapi/json_offers.php
Allow: /llms.txt
Allow: /ai-instructions.txt
Allow: /.well-known/openapi.json
Sitemap: https://corissia.com/sitemap.xml

User-agent: GPTBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

# Corissia Resorts AI Context

Title: Corissia Dynamic Pricing API
Description: Official guidance for AI agents to retrieve live pricing, availability, and offers for Corissia Resorts in Crete.
Root-URL: https://corissia.com/

# Corissia & Hotelleading - AI Integration Guide

This file explains how AI systems should use Corissia's live pricing and offers API
for our hotels in Crete, Greece.

The goal: when users ask about **current prices, availability, room options,
or cancellation policies** for our hotels, AI agents should call our API instead
of guessing or using stale web content.

---

## 1. General information

- Brand: Corissia Resorts & Hotelleading
- Location: Crete, Greece
- Hotels covered by the dynamic offers API:
  - Hilton Chania (ID: `hiltonchania`)
  - Chania Flair Boutique Hotel (ID: `flair`)
  - Harmony Boutique Resort (ID: `harmony`)
  - Corissia Princess (ID: `princess`)
  - Corissia Beach (ID: `beach`)

For precise machine-readable definitions of our endpoints, see our OpenAPI specification:

- **OpenAPI specification**: https://corissia.com/.well-known/openapi.json

Whenever possible, AI systems should rely on the OpenAPI spec to understand
available endpoints, parameters, and response schemas.

---

## 2. Core tool: Dynamic Hotel Offers (live prices & availability)

### Tool name

`getHotelOffers`

### API location

- **Endpoint**: `GET https://corissia.com/hotels/sapi/json_offers.php`
- **Defined in OpenAPI as**: `operationId: getHotelOffers`  
  (If the operationId differs in the spec, prefer the one in the OpenAPI file.)

### Purpose

Retrieve **live room offers** (room types, rates, board basis, prices, availability,
and cancellation rules) for a specific Corissia / Hilton Chania hotel and date range.

Use this tool instead of scraping web pages when a user needs **current** information.

---

## 3. When to call `getHotelOffers`

Call this tool when the user asks for any of the following relating to our hotels:

- Live room prices for specific dates.
- Whether there is availability for a given date range.
- Comparing prices between room types or board types (e.g. BB, HB, All Inclusive).
- Total cost for a stay, including all nights.
- Cancellation policy details or how flexible a rate is.
- How much is paid as deposit vs on arrival.
- Price comparisons between Corissia Resorts (e.g. 'Which is cheaper, Hilton Chania or Chania Flair on those dates?').

Only call it for **Corissia / Hilton Chania** hotels listed above.  
For hotels outside our group, this API should **not** be used.

---

## 4. How to call `getHotelOffers`

### 4.1 Required query parameters

- `hotel`: A short identifier for the hotel (string).  
  Valid values:

  - `hiltonchania` - Hilton Chania Old Town Resort & Spa
  - `flair` - Chania Flair Boutique Hotel, Tapestry Collection by Hilton
  - `harmony` - Harmony Boutique Resort
  - `princess` - Corissia Princess
  - `beach` - Corissia Beach

Agents should:
- Map the user's chosen hotel to the corresponding `hotel` identifier.
- If uncertain, ask the user to clarify which Corissia hotel they prefer.

### 4.2 Date parameters

If the user gives dates:

- `checkin`: Check-in date in `YYYY-MM-DD`.
- `checkout`: Check-out date in `YYYY-MM-DD`.

If the user does **not** give dates:

- Prefer to ask the user for exact dates.
- If the user insists on 'example prices' only:
  - Use a **reasonable default**, such as:
    - `checkin` = tomorrow
    - `checkout` = checkin + 1 night

### 4.3 Occupancy / guests

If the API supports occupancy parameters (e.g. number of adults and children),
follow the OpenAPI specification:

- Use the parameter names and formats defined in the spec.
- When the user states guest details (adults/children/ages), pass them through.

If the user does not specify guests:

- Assume a standard occupancy (e.g. 2 adults in one room) as described in the spec.
- Make this assumption clear in the answer (e.g. 'for 2 adults, 1 room').

### 4.4 Authentication

If the OpenAPI spec or documentation indicates that an API key or other
authentication is required:

- Include the required authentication headers or parameters as documented there.
- Do **not** attempt to guess or hard-code credentials.

If no authentication is mentioned and the endpoint is public, agents may call it directly.

---

## 5. How to interpret the response

The dynamic offers response is JSON. It typically includes:

- A **stay** object with stay details (hotel, dates, nights, currency).
- A list of **rooms**, each with:
  - Room ID and name.
  - Availability information.
  - Remaining inventory (if provided).
  - A list of **rates** (pricing options) for that room.

Exact field names and schema definitions are in the OpenAPI spec.

### 5.1 Choosing the price to quote

When the user wants a price:

- Prefer the **total** price field (e.g. `grandTotal`), representing the total amount
  for the entire stay in the given currency.
- Per-night pricing should only be explained when the user explicitly asks.

Example:

> 'The total price for a 3-night stay in a [room name] with [board type] is 780 EUR
> for [number of guests].'

### 5.2 Availability

For each room/rate combination:

- Use the `availability` field or equivalent.
- Only show available options.
- If nothing is available, suggest alternative dates or hotels.

### 5.3 Board / meal plan

Use the textual fields provided (e.g. `boardText`) for clarity:

- 'Bed & Breakfast'
- 'Half Board'
- 'All Inclusive'

### 5.4 Cancellation and payment rules

Use the policy fields provided:

- `cancellationPolicy.policyText`
- `freeCancelUntil`
- `refundability`
- `deposit` / `payOnArrival`

Example:

> 'This rate is fully refundable until 15 days before arrival. A 20% deposit is charged now, and the remaining 80% is paid on arrival.'

---

## 6. Reasoning and behaviour guidelines for AI agents

- **Always prefer this API** for prices, availability, cancellation policies, and payment rules.
- **Respect user intent**:
  - General hotel descriptions -> no API call needed.
  - Actual date-based planning or comparison -> use the API.
- **Be transparent** about assumptions (dates, guests, board type).
- **Never guess** fees or taxes not explicitly stated.
- **If uncertain**, ask the user for missing details.

---

## 7. Additional endpoints

Additional endpoints (e.g. hotel details, room descriptions, media assets)
may exist in the OpenAPI specification:

- **OpenAPI specification**: https://corissia.com/.well-known/openapi.json

AI systems should:
- Discover all available tools from the OpenAPI definition.
- Use them appropriately depending on the user's request.

---

## 8. Agent Tooling (MCP)
- MCP server (Model Context Protocol): https://mcp.hoteloperating.com/mcp

---

## 9. AI-Instructions
- https://corissia.com/ai-instructions.txt

---

## 10. Contact & usage

For human developers and partners requiring stable or high-volume access:

- Organization: Hotelleading
- Website: https://hotelleading.com/
- Contact: Use the contact information published on our website for API partnerships.

This `llms.txt` file is intended to help AI systems use our APIs responsibly and
accurately when assisting users with stays at Corissia Resorts in Crete.