Luggage Claim

What Luggage Claim is for

"My bag didn't arrive, what do I do?", "how long do I have to file a damaged-baggage claim?", "is my $6,000 lost-bag claim within the liability limit?" — the exact steps, the exact documents, and the real numbers behind an airline baggage claim, not vague reassurance.

What it does

process_steps gives the ordered filing process for one issue type — lost, delayed, or damaged — starting with what to do at the airport baggage service desk before you ever leave, because that's where the Property Irregularity Report (PIR) that everything else depends on gets created. required_documentation lists what you'll need to support that specific kind of claim. checklist puts both together in one view. claim_deadline_check applies the Montreal Convention's real written-notice deadlines for international flights — a strict 7 days for damaged baggage, a more forgiving 21 days for delayed baggage — to however many days have actually passed, and tells you plainly if you've already missed it. montreal_convention_limits gives the current per-passenger SDR liability caps for baggage, delay and injury, effective from the December 2024 revision, alongside the prior 2019 figures so you can see how much they moved. us_domestic_baggage_limit gives the equivalent US domestic cap under 14 CFR Part 254. compare_liability_limits lines the two regimes up side by side. sdr_to_currency_estimate converts a Special Drawing Rights figure to an indicative dollar amount. reimbursement_estimate sums an itemized list of lost or damaged contents and flags whether your total exceeds the cap that actually applies to your flight. luggageclaim_glossary explains PIR, SDR, excess valuation declaration, WorldTracer and more.

What it is not

Not a claims service — it doesn't contact any airline or file anything on your behalf, and not legal advice. The Montreal Convention baggage liability figures (1,519 SDR, effective 28 December 2024) and the US domestic figure ($4,700, effective 22 January 2025, under 14 CFR Part 254) were verified against ICAO's five-year revision cycle and the DOT's own final rule as of this reference's build date — both are revised periodically for inflation, so check the current number before relying on it for a real claim of meaningful size. Whether a specific claim actually succeeds depends on facts — what really caused the damage, whether it's "ordinary wear and tear," what the airline's own contract of carriage says for domestic flights — that only the airline and, if it comes to that, a regulator or court can settle.

Luggage Claim — Privacy Policy

Effective 26 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Luggage Claim is. Luggage Claim is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated, fully local baggage claim-process guide and liability-limit reference and calculator. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup or calculation.

What we receive. The arguments of each tool call — an issue type, a number of days elapsed, an SDR amount, or an itemized list of lost/damaged items and their claimed values — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs. We do not ask for or need your name, PIR reference number, or airline booking details to answer any of these questions, and an itemized loss list you provide for a reimbursement estimate is used only to compute that one response.

Everything is answered from a bundled, hand-curated reference file and computed locally, and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query, including any itemized list you provide, is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and every calculation runs locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Luggage Claim is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Luggage Claim — Terms of Service

Effective 26 September 2026. These terms govern use of the Luggage Claim connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Luggage Claim returns a hand-curated, fully local lost/delayed/damaged baggage claim-process guide and liability-limit reference and calculator, covering the Montreal Convention (international) and 14 CFR Part 254 (US domestic). It is accessed through an AI assistant or directly over MCP or HTTP.
2. General information, not legal advice, not a claims service. The Service is an independent reference and calculator, not a lawyer, not a claims agent, and not affiliated with any airline. It does not file a PIR, submit a claim, or represent you in any dispute. Liability limits and deadlines reflect the build date stated in the Service's own data and are revised periodically by treaty (Montreal Convention) or regulation (14 CFR Part 254) — verify the current figure before relying on it for a real claim, especially one near the cap.
3. Not a guarantee of outcome. Whether a specific claim succeeds, and for how much, depends on facts (true cause, documentation, the airline's own contract of carriage for domestic flights) that this Service cannot verify and that airlines sometimes dispute. A result here is not a determination by any airline or regulator.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time, including to reflect regulatory or treaty changes.
6. Data. Our Privacy Policy describes what we process. In short: your query, including any itemized list you provide, is computed from a bundled reference file and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or damage arising from use of, or reliance on, the Service, including a claim denied or underpaid in reliance on a result from this Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/luggageclaim

Luggage Claim support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://luggageclaim.connectorbay.com/mcp
• REST API: https://luggageclaim.connectorbay.com/openapi.json
• Live status: https://luggageclaim.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Luggage Claim never asks for them.