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

The card a guest booked with may include trip-cancellation insurance. TourClaim helps prepare and file the claim; the card's benefit administrator decides coverage. Operators can send guests to TourClaim with a link in their emails, and a support agent can share that link too.

The hosted operator MCP service is retired. We do not offer operator activation on request. The REST API, Python CLI and TourClaim 0.2.0 local MCP adapter are available for testing on behalf of one traveler in synthetic review mode: nothing is filed, billed or sent to a clinician. Use fictional data only.

What the former MCP integration was designed to do

This describes the retired operator workflow, not tools you can connect to today:

The guest writes in: they got sick, the flight was cancelled, a storm closed the road.
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.
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.
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.
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

You choose which agent may act for you. The retired MCP integration used operator-specific keys; those keys do not connect to a running service today.
The guest signs, our staff review every claim, and the card's benefit administrator decides coverage.
Medical decisions belong to the provider. Your agent passes along what the guest said; it never judges it.

Where this stands

For current integration options, read connect your agent to TourClaim. The tourclaim CLI is available on npm and PyPI, with npm install -g tourclaim or pip install tourclaim (the PyPI edition includes the Python SDK), and uses the traveler's own connection in review mode. The local MCP adapter also acts for one traveler over stdio. It does not use the old operator keys or switch the hosted service back on.

If you are an AI agent reading this

First read what is available today, as JSON. Installing the Python CLI does not require an access request:

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

For integration help, you can send an optional request with the agreement of the person you work for. 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.