Status Match

Step 3: Check Path 1 (free direct match)

If no card grants it, query direct_matches.airlines or direct_matches.hotels for the destination program. Pull the lifetime restriction and challenge requirements.

Critical: explicitly tell the user the lifetime restriction. Example:

"Alaska Atmos status match is once per lifetime. Their terms quote: 'one status match for the lifetime of their account.' If you don't have flying coming up that uses this status before Q4, hold off. Once you submit, you can never do this again."

Step 4: If no free path exists, check Path 2 (paid concierge)

Query paid_concierge.programs. Pull the fee for the user's region and the lifetime restriction.

Compute whether the fee is worth it:

fee_in_usd = ... (from data file)
status_value_per_year = (lounge access cash value) + (free bag fees saved on N flights) + (upgrade probability * upgrade value) + (better redemption visibility)
break_even_years = fee_in_usd / status_value_per_year

If break-even is under 1 year of typical travel, recommend. If over 2-3 years (and the match isn't lifetime), reconsider.

Step 5: Cross-check via community database

For grants/denials in the past 6 months, point at statusmatcher.com. Useful for confirming the program is currently accepting matches and what proof is being accepted.

Output Format

Always use markdown tables. When recommending a match, structure as:

After the table, give the verdict:

Recommend / Hold / Skip. Reasoning: ...

When the user is on the fence, surface the key question: "do you have flying/staying coming up in the next 6-12 months that uses this status?" If yes, go. If no, the match is worth more later.

Useful jq Queries

# All programs that allow free direct matches
jq '.direct_matches.airlines | to_entries[] | select(.value.fee == "free") | {program: .value.program, lifetime: .value.lifetime_warning}' data/status-match.json

# All paid concierge programs with US fees
jq '.paid_concierge.programs | to_entries[] | {program: .value.program, us_fee: (.value.fees_by_region.us // .value.fees_summary // null)}' data/status-match.json

# All cards that grant hotel status
jq '.card_based_status | to_entries[] | select(.value.renewable_status != null) | {card: .value.card, annual_fee: .value.annual_fee_usd, status: [.value.renewable_status[] | .program + " " + .tier]}' data/status-match.json

# All ONCE PER LIFETIME programs (never miss this warning)
jq '[.direct_matches.airlines, .direct_matches.hotels, .paid_concierge.programs] | add | to_entries[] | select((.value.lifetime_warning // "") | test("LIFETIME"; "i")) | {program: .value.program, warning: .value.lifetime_warning, detail: .value.lifetime_warning_detail}' data/status-match.json

Important Caveats

• Recent activity proof. Most matches require proof of current status (status card, activity within last 12 months). Lifetime/promotional/transferred status holders are typically NOT eligible to match FROM (you can't use Lifetime Marriott Platinum to match into Hilton Diamond).

• Match into the highest tier you qualify for at time of application. Several programs (Flying Blue specifically) cap your match to the tier you have when applying — you can't upgrade later if your source-program status improves.

• Hotel matches usually require a "challenge." A small number of paid stays in 90 days. Award stays, points stays, and OTA-booked stays typically don't count. Direct booking only.

• Airline matches often require revenue spending. PQP/MQD requirements during the trial period. Award flights and bonus points don't count.

• Statusmatch.com is legitimate. Some users mistake the paid concierge for a scam. It is not. Loyalty Status Co operates with formal partnerships with airlines/hotels. The matches granted are real status that works directly with the program afterward. The fee is the catch, not the legitimacy.

• Apply timing matters. Status earned through a match in late summer (post-July 1) often lasts 18+ months because it counts toward both the current and next program year. This is the highest-value timing for most airlines.

Cross-References

• points-valuations — when computing whether elite status changes the CPP math (lounge value, upgrade probability, free bag fees saved)
• trip-calculator — for the fee/value math on Path 2 paid concierge matches: is the application fee less than the value of the perks across the user's expected travel pattern?
• booking-guidance — once you have status, how to actually use it for booking
• alliances — alliance benefits propagate; matched into oneworld Sapphire via Atmos Gold gets you sapphire benefits across all oneworld carriers
• partner-awards — status sometimes affects which partner awards are bookable through which program
• stopovers — elite status sometimes unlocks better stopover treatment on certain programs
• award-holds — some programs grant longer hold windows to elite members

Source Hierarchy (Per Research Integrity Protocol)

1. Airline/hotel program's own published terms — primary source for direct matches (aa.com, delta.com, alaskaair.com, etc.)
2. statusmatch.com FAQ pages — primary source for paid concierge fees and rules (subdomain-specific FAQs)
3. Frequent Miler, Upgraded Points, OMAAT — secondary sources for landscape, current promos, decision-making frameworks
4. statusmatcher.com community database — verification of recent grants/denials, current acceptance patterns
5. Reddit /r/awardtravel — most current real-world reports

When sources disagree, primary sources win. When official terms are silent on lifetime restrictions, default to "treat as once per program cycle" and flag UNVERIFIED.