# TourClaim by Copernican

> TourClaim files trip-cancellation claims against the travel insurance that comes with a traveler's credit card. It gathers the booking, the merchant's cancellation policy and the proof of the reason (a provider's note for an illness, a carrier's notice for a cancelled flight, official weather records), and prepares the claim for the card's benefit administrator, who decides coverage.

## For AI agents

- [Available interfaces and integration help (JSON)](https://app.getcopernican.com/api/agent-access): GET it first. The REST API, the CLI (npm and PyPI) and the Python SDK are available in review mode. Claims are synthetic: nothing is filed, billed or sent to a clinician. Use fictional data only. Local MCP is available through the optional Python extra; there is no hosted MCP endpoint, and the former operator MCP service remains decommissioned.
- tourclaim CLI on [npm](https://www.npmjs.com/package/tourclaim) and [PyPI](https://pypi.org/project/tourclaim/): install with `npm install -g tourclaim` (Node 18.3 or newer) or `pip install tourclaim` / `pipx install tourclaim` (Python 3.9 or newer, includes the Python SDK), or try it without installing: `npx tourclaim --help` or `uvx tourclaim --help`. Both editions have the same commands and output and share the credentials file.
- [Local MCP client setup](https://github.com/tourclaim/tourclaim-cli/blob/v0.2.0/MCP.md): configure `uvx --python 3.12 --from 'tourclaim[mcp]==0.2.0' tourclaim mcp` in a stdio-capable MCP client. Requires uv for this command; the MCP extra requires Python 3.10 or newer. Uses the same synthetic review API and traveler browser sign-in. Credentials stay in the local store.
- [CLI source and command reference](https://github.com/tourclaim/tourclaim-cli) and [agent instructions](https://github.com/tourclaim/tourclaim-cli/blob/main/AGENTS.md): read the instructions before acting for a traveler. Use `--json`. Run `tourclaim login --json --no-browser` for browser sign-in and `tourclaim status --json` to check the mode. Never ask for a key in chat; the traveler approves sign-in and signs their own claim in their own browser.
- For integration help, POST JSON to the same URL with `requested_by`, the `contact_email` of the person you work for, `interfaces` and `use_case`, only with that person's agreement. This request is optional for CLI and local MCP use. A person reads every request and replies to that address. Leave claim, medical and payment details out.
- [Developer guide](https://app.getcopernican.com/developers), [REST API reference](https://app.getcopernican.com/muse/developers) and [OpenAPI schema](https://app.getcopernican.com/api/connectors/v1/openapi.json)

## Assistant handoff and production access

- [Assistant instructions](https://app.getcopernican.com/start/assistant): linked from booking intake. Readable without JavaScript; saving a preparation needs JavaScript, cookies, and operator booking context. The assistant prepares booking details and selected non-medical evidence. The traveler verifies email, answers medical questions privately, consents, signs, and submits. Saving is not filing.
- [Request a production key](https://app.getcopernican.com/developers#production-access): live integration access requires Copernican approval. Include the product, website, use case, expected volume, and launch date. Requesting access or creating a self-service review key does not activate production.
- [Reviewer walkthrough](https://app.getcopernican.com/muse/developers#reviewer-test-guide) and [fictional examples](https://app.getcopernican.com/muse/review-fixtures.json): synthetic test journeys, not customer records. Muse connector review is not Meta approval.

## Posts

- [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)

- [Why we opened TourClaim to AI agents](https://www.getcopernican.com/blog/why-we-opened-tourclaim-to-ai-agents)
- [Connect your agent to TourClaim: the API, the MCP server and a CLI](https://www.getcopernican.com/blog/connect-your-agent-to-tourclaim-api-mcp-cli)
- [For tour operators: let your support agent start the claim](https://www.getcopernican.com/blog/tour-operators-let-your-support-agent-start-the-claim)
- [What TourClaim does](https://www.getcopernican.com/blog/what-tourclaim-does-trip-cancellation-claim-automation)

## Optional

- [For travelers](https://www.getcopernican.com/travelers): start a real claim online without an operator referral or a particular assistant. The API and CLI remain in synthetic review mode.
- [Security contact](https://www.getcopernican.com/.well-known/security.txt)