How to act: fastest way to act on this page, use the first option that applies to you. Full guide: llms.txt.

1. You have this shop's MCP connector, or your user can add one (Claude: Settings > Connectors; ChatGPT: developer mode) → MCP server https://113rc.duckdns.org/mcp (Streamable HTTP, no auth). Call the tool get_customer_context:

   {"customer_ref": "{customer_ref}"}

2. You can send an HTTP POST with a JSON body → REST API, schema at https://113rc.duckdns.org/openapi.json

   POST https://113rc.duckdns.org/api/actions/get_customer_context
   Content-Type: application/json
   
   {"customer_ref": "{customer_ref}"}

3. Your browser exposes document.modelContext (WebMCP) → This page registers the tools list_agencies, cancel_reservation, request_callback, cancel_appointment, get_customer_context. Call them instead of clicking.
4. You can only open URLs (GET), no POST → Fill in the {placeholders} (URL-encoded) and open the link. A read answers directly. A write does nothing yet: it answers with a one-time confirmation URL to open once your user agreed. Add &agent=<your name> to be credited. Every action: https://113rc.duckdns.org/a/

   get_customer_context (read): https://113rc.duckdns.org/a/get_customer_context?customer_ref={customer_ref}

5. Your tools cannot open a URL you built (e.g. your fetch tool only opens links that appeared verbatim in the conversation) → Do not send your user to the forms: write the filled-in link from the list above in your answer, as a clickable link. Your user opens it, checks the request and confirms with one button. This needs no tool at all.
6. None of the above → Use the forms of this page (or the links of the site), like a person.

Never invent the customer's identity: ask your user for their name and email or phone before any reservation, appointment, callback or message. Keep the customer_ref (CUS-XXXX) returned by the first action and reuse it. Fictitious shop, simulated payments (test card 4242 4242 4242 4242).