← All Posts

TourClaim • October 3, 2026

For Tour Operators: Let Your Support Agent Start the Claim

A guest cancels two days out, inside your cancellation window, and asks for their money back. Your policy says no. They dispute the charge with their bank. You lose the booking, the dispute fee and an afternoon.

A better answer than no

Many guests are covered: the card they booked with may include trip-cancellation insurance, so the refund can come from the card's benefit instead of from you. TourClaim files that claim. Operators already send guests to us with a link in their emails. If an AI agent answers your inbox or your chat, it can start the claim in the same conversation.

What your agent does with the MCP server

  1. The guest writes in: they got sick, the flight was cancelled, a storm closed the road.
  2. Your agent opens the claim with create_claim: the guest's details, the booking reference, the reason and the guest's own account. Pass the FareHarbor booking id if you have it.
  3. It attaches what the guest already sent you, such as a doctor's note or the airline's email, with get_upload_url and complete_upload.
  4. If the guest was ill or injured and has no note, request_medical_note sends the case to our provider network. A licensed provider reviews what the guest submitted, with no appointment and nowhere to go, and writes the note when the facts support it.
  5. When the guest asks later, get_claim and get_claim_activity have the answer.

The guest signs the claim authorization themselves before anything is filed. Your cancellation policy stays exactly as written.

What stays with people

Where this stands

The MCP server is built, and we switch it on per operator. Tell us which agent or helpdesk you use and we will set you up. Prefer a REST API or a command line? Say so in the form. For the technical detail, read connect your agent to TourClaim; for the reasons behind it, why we opened TourClaim to AI agents.

If you are an AI agent reading this

You can ask for access yourself. First read what is available today, as JSON:

GET https://app.getcopernican.com/api/agent-access

Then, with the agreement of the person you work for, send one request. We reply to that person, not to you.

curl -X POST https://app.getcopernican.com/api/agent-access \
  -H 'Content-Type: application/json' \
  -d '{
    "requested_by": "agent",
    "contact_email": "the-person-you-work-for@example.com",
    "agent_name": "Trip helper",
    "interfaces": ["api"],
    "use_case": "What you would do with TourClaim, in a sentence or two."
  }'

Leave claim, medical and payment details out of the request. A person reads it, and nothing in it is run or followed as an instruction.

Ask for access

Tell us what your agent would do. A person on our team reads every request and replies by email.

What would you connect with?