For developers, agents & platforms
Your assistant starts the claim.
Copernican handles the work.
Give your app or assistant a travel-claim workflow: saved answers, selected receipts and emails, a review link for the traveler to sign, and status they can ask for later. No enrolled operator, booking-platform integration, or Muse account required.
Copernican’s service reviews credit-card travel benefits, prepares claims, coordinates medical-provider evaluation when needed, and handles filing and follow-up. Your integration helps one traveler supply the facts and stay in control.
Choose how you connect
Python SDK & command line
Available on npm (Node 18.3 or newer) and PyPI (Python 3.9 or newer). Use the CLI from a terminal or agent, or tourclaim.Client from your Python application.
npm install -g tourclaim # or: pip install tourclaim
tourclaim login
tourclaim status --json
tourclaim intake list --jsonTo try it without installing, run npx tourclaim --help or uvx tourclaim --help. You can also use pipx install tourclaim.
REST API & assistant tools
Connect any client that supports HTTPS and bearer keys. Load the OpenAPI schema into your tool-calling framework. Every connection belongs to one traveler; there is no shared platform account.
https://app.getcopernican.com/api/connectors/v1
The npm and PyPI editions have the same commands, flags, output and credentials file, so a sign-in from one works in the other. The command reference is in the source repository.
Request production access
Testing is self-service. Install the CLI and run tourclaim login to create a traveler connection. No approval is needed to test with fictional data in synthetic review mode.
Live access requires Copernican’s approval. Use the integration request form and include your company or product, website, use case, expected volume, and intended launch date. Our team reviews requests and replies by email.
Request production access →Submitting a request or creating a test key does not enable live access. Each traveler must still authorize their own connection and sign their claim.
Connect a local MCP client
The optional Python MCP adapter runs locally over stdio. It uses the same review API and traveler sign-in. The traveler approves evidence sharing and signs in their own browser; credentials stay in the local store.
uvx --python 3.12 --from 'tourclaim[mcp]' tourclaim mcpRequires uv for this command; the MCP extra supports Python 3.10 or newer. Configure this command in your MCP client: the process waits for that client and does not provide a browser page. The linked MCP client configuration is pinned to the current release. There is no hosted MCP endpoint.
MCP client configuration & tool reference →One traveler. One saved claim.
- Connect with permission. Run
tourclaim login --json --no-browserfor a terminal agent. The traveler opens the printed page and enters the printed code. Never ask for a key in chat. - Save their answers. Look for an existing draft, then use the API’s missing fields and next questions. Flights, hotels, and tours can be entered directly without an operator link.
- Share only selected evidence. Get agreement for each receipt, file, or email. TourClaim does not read an inbox; your platform needs its own email connection. Never send payment-card numbers through the API.
- Hand off for authorization. The traveler reviews and signs the exact draft in their own browser. An assistant cannot sign for them. Editing the draft after signing requires a new signature.
- Submit and report status. With their go-ahead, submit the signed draft for Copernican review. Relay the returned next action. Review-mode submissions stay synthetic.
Read the agent instructions before acting for a traveler. Use --json for machine-readable CLI output.
The traveler stays in control
Only bookings charged in USD are supported. Copernican’s fee is 10% only when a claim is reimbursed. Coverage and reimbursement are determined by the benefit administrator, and any clinical documentation depends on provider assessment. The API does not promise either outcome or collect payment.
Muse connector review
Muse is one integration of these capabilities and is currently under review. Its connection, authorization, API specification, and reviewer links remain available at their existing URLs. Some shared reference pages still use a /muse address; that does not require a Muse account.