Credit Card Travel Perk Aggregator

WHAT IT DOES

This script scans credit card comparison and travel perk pages—The Points Guy, NerdWallet, CreditCards.com, and others—for travel-related perks including airline credits, hotel credits, lounge access, travel insurance, baggage benefits, and annual fees. It displays a floating overlay aggregating and comparing perks across multiple cards. Perk data is extracted from the page, organized by card, and displayed in a comparison matrix with color-coded indicators: green for included, red for not included, yellow for limited. A summary of total value of perks by card is provided, along with identification of overlapping benefits and unique perks that only appear on one card. Users can export perk data as CSV or JSON. All perk comparison snapshots are stored per domain locally for tracking over time.

WHERE IT RUNS

Works on any credit card comparison or travel perk page—The Points Guy, NerdWallet, CreditCards.com, Bankrate, or any page displaying credit card offers with travel benefits. The script detects card containers and perk data using common patterns and selectors, making it compatible with most credit card comparison sites.

HOW TO USE

The panel appears automatically when you visit a card comparison page. It detects cards and their travel perks, then displays a comparison matrix with cards as columns and perks as rows. Perks are color-coded: green checkmarks for included perks, red crosses for not included, and currency values for credits and fees. The "Unique Perks" section highlights benefits that only appear on one card, helping you identify differentiators. Click "Refresh Data" to rescan for updated card information. Export perk data as CSV for spreadsheet analysis or as JSON for programmatic use. Use "Clear History" to reset stored snapshots for the current domain. The panel automatically saves a snapshot each time you visit, building a history of card comparisons.

TECHNICAL MECHANISM: CREDIT CARD TRAVEL PERK EXTRACTION WITH COMPARISON MATRIX AND UNIQUE PERK DETECTION

The script uses a comprehensive detection strategy. It searches for card containers using selectors (.card, .credit-card, .card-offer, .card-comparison) and falls back to scanning divs with card-related keywords (amex, chase, citi, capital one, annual fee, credit, travel, perk, benefit). For each card, it extracts the name from card-name elements or by identifying capitalized text. Perks are extracted using a defined list of perk definitions: annualFee, airlineCredit, hotelCredit, loungeAccess, travelInsurance, baggageBenefits, priorityPass, globalEntry, hotelStatus, carRental, transferPartners, foreignTransactionFee, signupBonus. For each perk, the script checks the text for the perk label and extracts the value: currency values for fee/credit perks, boolean values (true/false) for included/not included perks, and text values for status and partner perks. The comparison matrix is built by collecting all perk keys across cards and rendering them as table rows. Unique perks are identified by counting how many cards have each perk; perks with a count of 1 are marked as unique and highlighted. The export function generates CSV with cards as columns and perks as rows, including all perk values. Each snapshot stores the card list with perks, capped at 30 entries per domain.

THE PANEL

The travel perk aggregator appears in a draggable, resizable panel that remembers its position per site. The panel shows the comparison matrix with color-coded indicators, unique perks summary, and history. Drag by the header to reposition, collapse to a compact icon with a click, and resize using the bottom-right corner. The panel snaps to screen edges for tidy placement and closes with the Escape key. All settings—panel position—persist per website using GM_setValue, so your view returns exactly as you left it.

PLEASE NOTE

This script requires the free BotGentz extension to run. The script relies on common card comparison page structures—if a site uses a non-standard layout, perk detection may be incomplete. The script does not access your financial account credentials—all data is read from the visible page and stored locally. The perk detection uses pattern matching; some perks may be missed if the page uses different labels. The unique perk detection identifies perks that appear on only one card; this is based on the detected cards on the current page. All data is stored locally in your browser via GM_setValue and never transmitted.