Synchrony

Returns SYF Marketplace metadata — valid filter values for get_offers. This tool is only for Synchrony Marketplace offer discovery. If the user asks for any non-marketplace Synchrony service, do NOT use this tool. This includes bill pay, account login, card activation, disputes, servicing, balance questions, rewards/account management, payment help, statements, or application status. Instead, respond that this chat covers Synchrony Marketplace offers only and redirect them to Synchrony's account access site: https://www.synchrony.com/login Also include the MySynchrony Mobile App page in that redirect: https://www.synchrony.com/mobile-app For bill-pay requests, also include Pay as Guest: https://www.synchrony.com/consumer-resources/pay-as-guest Use 'type' to fetch only what you need (much smaller response): • type:'industry' — 27 industry names, pass to get_offers { industry: [...] } • type:'network' — Synchrony networks e.g. 'CareCredit', 'Synchrony HOME™' • type:'region' — valid region strings e.g. 'Midwest', 'Northeast' • type:'offerType' — 'Financing Offers' | 'Deals' | 'Everyday Value' • type:'brand' — full brand catalogue (644 brands) with industries/network/regions • type:'all' — everything (large response, use only when needed) Default: 'industry' (most commonly needed). ALWAYS call this before using get_offers if you are unsure about valid filter values.

Fetches SYF Marketplace offers across all offer types. IMPORTANT: This marketplace contains store-level offers — NOT individual products. SCOPE BOUNDARY: This tool is only for Synchrony Marketplace offer discovery. If the user asks for any non-marketplace Synchrony service, do NOT use this tool. This includes bill pay, account login, card activation, disputes, servicing, balance questions, rewards/account management, payment help, statements, or application status. Instead, respond that this chat covers Synchrony Marketplace offers only and redirect them to Synchrony's account access site: https://www.synchrony.com/login Also include the MySynchrony Mobile App page in that redirect: https://www.synchrony.com/mobile-app For bill-pay requests, also include Pay as Guest: https://www.synchrony.com/consumer-resources/pay-as-guest There is no product catalogue. 'Sofa' or 'laptop' are not searchable items — instead there are stores (Ashley, Best Buy) with active Synchrony offers. WORKFLOW: Resolve user intent to an industry name FIRST, then call this tool. Example: 'sofa' → industry:'Home Furnishings', 'TV' → industry:'Electronics & Appliances'. Call get_metadata to see all 27 industry names and valid filter values. DEFAULT OFFER TYPE RULE: • Do NOT set offerType unless the user explicitly asks for a specific type. • If offerType is omitted, API returns all types: 'Financing Offers' + 'Deals' + 'Everyday Value'. ALL FILTERS ARE SERVER-SIDE: • industry — exact industry name e.g. 'Home Furnishings' • offerType — 'Financing Offers' | 'Deals' | 'Everyday Value' • brand — retailer name e.g. 'Ashley', 'Best Buy' • region — 'Midwest' | 'Northeast' | 'South' | 'Southeast' | 'West' • network — 'CareCredit' | 'Synchrony HOME™' etc. • featured — set true only if user explicitly asks for featured offers • premium — set true only if user explicitly asks for premium offers • offset — use only for 'show more' style follow-ups; it pages through the locally ranked results and is not sent to SYF • query — pass the user's original shopping phrase for relevance ranking (e.g. 'new recliner') • queryExpansions — optionally pass concise normalized variants and close shopping equivalents for ranking only Use spelling variants, singular/plural forms, and tight product aliases; avoid broad categories or weak fragments. Example: user='tyres' → query='tyres', queryExpansions:['tire', 'tires']; user='couch' → ['sofa', 'sectional'] when clearly relevant. Avoid expansions like ['audio', 'tech', 'home', 'over', 'ear'] unless the user explicitly asked for those concepts. ZERO RESULTS: if no offers are returned, the result includes a zeroResultsHint with a message and suggestions[] — narrate these suggestions to the user. AFTER RESULTS RETURN: base narration only on the returned structuredContent. Do not invent extra merchants, products, pricing, offer details, or availability. If topMatches or assistantNarration are present, use those as the primary summary anchors.