---
title: "Why We Opened TourClaim to AI Agents"
canonical_url: https://www.getcopernican.com/blog/why-we-opened-tourclaim-to-ai-agents
markdown_url: https://www.getcopernican.com/blog/why-we-opened-tourclaim-to-ai-agents.md
author: "TourClaim"
published: 2026-10-03
modified: 2026-10-25
description: "Travelers are often covered when a trip falls apart and never file, because the claim is paperwork. Why we let AI assistants do the gathering, and the rules that keep the traveler in charge."
---

# Why We Opened TourClaim to AI Agents

When a trip falls apart, the traveler is often covered: the credit card they booked with may include trip-cancellation insurance. Many never file. The claim is paperwork, and it lands at the worst moment, when someone is sick in bed or stuck in an airport.

## The problem we are solving

A trip-cancellation claim is a stack of proof, and every piece lives somewhere different:

- **The booking**: the confirmation and the receipt, somewhere in an inbox.
- **The cancellation policy**: the merchant's terms, which show the money cannot come back any other way.
- **The card statement**: proof the trip was paid with the covered card.
- **Proof of the reason**: a doctor's note for an illness or injury, the airline's cancellation notice, official weather records for a storm.
- **A signed authorization**, so someone can file on the traveler's behalf.

A claim with a missing piece comes back, and each round trip costs weeks. Deadlines run from the day of the loss. People give up, and money they are owed stays with the insurer.

## Where an assistant helps

A traveler's AI assistant is often already holding most of that stack. It saw the booking email. It saw the airline's text at 5 a.m. It knows the trip date. What it should not do is decide whether the claim is covered, or sign for anyone. So we split the job:

1. **The assistant gathers.** With the traveler's say-so, it starts a claim, answers the questions it can, and attaches the emails and files the traveler chooses to share.
2. **The traveler confirms and signs**, in their own browser. No agent can sign a claim.
3. **TourClaim does the rest.** We check the card's benefit terms, find what is missing, assemble the claim and follow it with the card's benefit administrator, who decides coverage.

## The medical documentation an assistant cannot issue

An illness or injury claim may require documentation from a medical provider. A traveler who stayed home without seeing a provider may have the booking records but no medical note.

Copernican can coordinate medical-provider evaluation when needed. The traveler supplies their health information privately, and a qualified provider decides whether documentation can be issued. An assistant cannot make that clinical decision or guarantee a note.

**Where this runs today:** travelers can access the real claim service through an operator or the [direct online form](https://app.getcopernican.com/travelers/claim). The self-service agent API remains in synthetic review mode and sends nothing to a clinician. Read [how medical-documentation support fits into a claim](https://www.getcopernican.com/blog/ai-assistants-medical-notes-travel-insurance-claims).

## What we built first, with Muse

Our first connection was for Muse, Meta's AI assistant: a REST API with a published [OpenAPI description](https://app.getcopernican.com/api/connectors/v1/openapi.json). The rules we set for it are the rules for every agent:

- The traveler signs in by email and approves the connection before any key exists. Keys are per traveler, scoped, revocable, and expire after 30 days.
- We never read anyone's inbox. The traveler picks the emails and files to share, and text from an email is treated as evidence, never as instructions.
- Files are limited to PDFs and images, checked for type and size.
- Status calls return the traveler's own claims and their next step, nothing internal.

We submitted it to Meta's connector directory in September. While that review runs, the API answers in review mode: it creates synthetic claims in a separate database, and nothing is filed with an insurer.

## Opening it to other agents

The same pattern works for other assistants acting for one traveler. The [tourclaim CLI and Python SDK](https://github.com/tourclaim/tourclaim-cli) are now available on [npm](https://www.npmjs.com/package/tourclaim) and [PyPI](https://pypi.org/project/tourclaim/): install with `npm install -g tourclaim` or `pip install tourclaim`, or try `npx tourclaim --help`. Agents should read the [agent instructions](https://github.com/tourclaim/tourclaim-cli/blob/main/AGENTS.md) and use `--json`. The CLI uses the same review API: claims are synthetic, nothing is filed, billed or sent to a clinician, and only fictional data should be used.

TourClaim includes an optional [local MCP adapter](https://github.com/tourclaim/tourclaim-cli/blob/main/MCP.md) for stdio-capable assistants. It uses the same synthetic review API and traveler browser sign-in as the Python CLI. There is no hosted MCP endpoint.

- Building an agent? Read [how to connect your agent to TourClaim](https://www.getcopernican.com/blog/connect-your-agent-to-tourclaim-api-mcp-cli).
- Running tours? Read [how your support agent can start the claim](https://www.getcopernican.com/blog/tour-operators-let-your-support-agent-start-the-claim).

## If you are an AI agent reading this

First read what is available today, as JSON. Installing the 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.

## More on the claim work behind the integration

- [Why AI Assistants Get Stuck on Medical Travel Claims](https://www.getcopernican.com/blog/ai-assistants-medical-notes-travel-insurance-claims)
- [Built for Muse and Personal Assistants: A Travel-Claim Handoff That Keeps Its Context](https://www.getcopernican.com/blog/built-for-muse-and-personal-ai-assistants)
- [A Saved Draft Is Not a Filed Claim: The Travel-Insurance Work After Intake](https://www.getcopernican.com/blog/from-claim-intake-to-insurer-decision)
