o d6itU @sdZddlZddlZddlZddlmZmZddlmZmZm Z ddl m Z ddl Z e eZdZdZdZGd d d Zdad efd d Zddededed efddZd efddZdS)a Puja API Cache Manager This module handles fetching, caching, and refreshing puja information from the backend API. Cache is stored in a JSON file and refreshed weekly or on-demand. TOKEN OPTIMIZATION: - Extracts lightweight index (names, IDs, categories only) - Uses simple keyword matching first - Optionally uses LLM for complex queries (with minimal context) - Fetches full details only for matched pujas N)datetime timedelta)DictListOptional)Pathzdata/puja_api_cache.jsonz/https://karishyewebbackend.divami.com/all-pujasc @seZdZdZefdefddZdeefddZ dedd fd d Z deefd d Z d#de deefddZ dedeefddZdeededeefddZdedeedeefddZd$dede de deefddZd#d eede defd!d"Zd S)% PujaAPICachez9Manages caching of puja information from the backend API. cache_filecCs2tt}|jjj|_|j||_tddS)zInitialize the cache manager.z[PUJA CACHE] Cache initializedN)r__file__resolveparent project_root cache_pathloggerdebug)selfr current_filer@)timeoutNz/[PUJA CACHE] Successfully fetched data from APIz[PUJA CACHE] HTTP error: z&[PUJA CACHE] Error fetching from API: )rrhttpx AsyncClientr#API_URLraise_for_statusr info HTTPErrorr'r(r)r&)rclientresponser0r.rrr_fetch_from_apiUs&  ( zPujaAPICache._fetch_from_apiF force_refreshcs|s|}|rtd|dStd|IdH}|r(|||Std|}|r=td|dStddS)z Get puja data from cache or API. Args: force_refresh: If True, bypass cache and fetch fresh data Returns: Dictionary containing puja information or None if failed z&[PUJA CACHE] Returning data from cacher0r;Nz=[PUJA CACHE] API fetch failed, trying stale cache as fallbackz3[PUJA CACHE] Returning stale cache data as fallbackz[PUJA CACHE] No cache available)r/rrr#rEr:warningr')rrFr+api_datarrr get_puja_datais$         zPujaAPICache.get_puja_data puja_datac Csg}t|tr|ddkr|dg}ngS|D]A}|dd}|dgD]2}|dgD])}|di}||d |d|d ||d|d pPdd d dq/q'q|S)z Extract a lightweight index of all pujas (just names, IDs, categories). This is sent to LLM for initial matching to save tokens. Returns: List of lightweight puja summaries statussuccessr0name subCategoriespujasubcategorymappingspujasidurl_name descriptionNd)rRrMrScategory subcategorydescription_preview isinstancedictr#append) rrJindex categoriesrV category_name sub_categorymappingpujarrr_extract_puja_indexs(   z PujaAPICache._extract_puja_index puja_indexqueryc szAddlm}ddd|ddD}d|d |d }||IdH}|j}ddl}||} t d t | d | WSt ya} zt d t | jgWYd} ~ Sd} ~ ww)a- Use LLM to intelligently match user query to puja IDs. Sends only lightweight index to save tokens. Args: puja_index: Lightweight index of pujas query: User's search query Returns: List of matched puja IDs r) general_agent c SsBg|]}d|dd|dd|dd|ddd d qS) zID: rRz | Name: rMz | Category: rVz | Preview: rXN2...r).0prrr s4z1PujaAPICache._llm_match_pujas..NrUzgGiven this list of pujas and a user query, identify the most relevant puja IDs (up to 3). PUJA INDEX: z USER QUERY: u Return ONLY a JSON array of puja IDs (integers) that best match the query. Consider semantic meaning, not just keywords. Examples: - "marriage" or "wedding" → find "Marriage Engagement", "Vivaha", or wedding-related pujas - "cost of wedding" → find "Vivaaham" or "Marriage" pujas - "baby naming" → find "Naamakaranam" - "new home" → find "Gruhapravesham" - "obstacle removal" → find "Ganapati Homam" - "engagement" → find "Marriage Engagement" or engagement-related ceremonies IMPORTANT: Look for partial word matches too. "marriage" should match "Marriage Engagement". Return format: [4, 15, 23] If no good match, return: [] z[LLM MATCH] Matched z pujasz[LLM MATCH] Error: )app.agents.agentsrfjoinrunoutputstripr loadsrrlenr&r'r(r)) rrdrerf index_textpromptresultmatched_ids_textr matched_idsr.rrr_llm_match_pujass,     zPujaAPICache._llm_match_pujaspuja_idsc Csg}t|tr|ddkr|dg}ngS|D]9}|dd}|dgD]*}|dgD]!}|di} | d |vrPi| ||ddd } || q/q'q|S) a Get full detailed information for specific puja IDs. Args: puja_data: Full API data puja_ids: List of puja IDs to fetch details for Returns: List of full puja objects with all details rKrLr0rMrNrOrPrQrR)rVrWrY) rrJrzdetailed_pujasr^rVr_r`rarbpuja_with_contextrrr_get_detailed_puja_infos*      z$PujaAPICache._get_detailed_puja_infouse_llminclude_pricingcs2|IdH}|s dS||}|sdStdt|d|d||gd}tfdd |Dr=d g}|D]k}|d pId } |d pRd } |dp[d } |dpdd } } d}| D]}t|dkrxqo|| vs|| vs|| vs|| vr|d7}qodd| D}|sqAt dt|d}||kr| |dqAtdt|d|r| ||dd}|r|j ||d}tdt|d|S|r|std| ||IdH}|r| ||}|r|j ||d}tdt|d|Stdd |d!S)"a Token-optimized search with optional LLM enhancement. WORKFLOW: 1. Extract lightweight index (names, IDs, categories only) - saves tokens 2. Try simple keyword matching first (fast, free) 3. If use_llm=True and no matches, use LLM with minimal context 4. Fetch full details only for matched pujas Args: query: Search query (puja name, category, pricing info, etc.) use_llm: If True, use LLM for intelligent semantic matching when keyword search fails include_pricing: If True, include pricing details in response; if False, only spiritual/ritual details Returns: Formatted string with matching puja information Nz`I apologize, but I'm unable to fetch the puja information at the moment. Please try again later.zSI apologize, but the puja information format is unexpected. Please try again later.z[SEARCH] Searching z pujas | LLM: z | Include Pricing: )marriageweddingvivahvivahashaadikalyanam engagementc3s|]}|vVqdS)Nr)rjsyn query_lowerrr 2sz+PujaAPICache.search_puja..z# marriage engagement vivah kalyanamrMrNrXrVrSrcSsg|] }t|dkr|qS)r)rs)rjr3rrrrlLsz,PujaAPICache.search_puja..r4rRz [SEARCH] Keyword matching found z matches)rz[SEARCH] Returning z results from keyword matchingz%[SEARCH] Trying LLM semantic matchingz results from LLM matchingz[SEARCH] No matches foundz/I couldn't find specific information matching 'zh' in our current puja catalog. Could you try rephrasing your question or ask about a specific puja name?)rIrcrrrsloweranyr#splitmaxr\r}_format_puja_resultsry)rrer~rrJrdmarriage_synonymssimple_matchesrb puja_name puja_descrVrS query_words match_countwordmeaningful_words thresholdresultsformatted_results llm_matchesrrr search_pujasf          zPujaAPICache.search_pujarQcCs|sdSg}|ddD]N}|dd}|dd}|dd }|d d }|d d } |d g} d |d} |rC| d|d7} |ra|dkrat|dkrW|dddn|} | d| d7} |rk| d|d7} | rw| d| d7} | rVt| dddD]\} }|dd}|dd}|dd}|rdnd }|dg}|r| dt|d |d!7} |D]}|d"i}|d#d$}| d%|d7} q| d&7} | d'|d(7} | d)|d7} |rQ|d*d}|d+}|d,}|d-}| d.7} | t|ttfr d/|d0dnd1|d7} |dus#|dus#|durQ| d27} |dur5| d3|d0d7} |durC| d4|d0d7} |durQ| d5|d0d7} | d7} || q d6d|d7S)8a@ Format puja data into a readable string. Args: pujas: List of puja dictionaries to format include_pricing: If True, include pricing information; if False, only spiritual/ritual details Returns: Formatted string with puja information zNo results found.NrrMz Unknown PujarTzNo description availablerVrNregionlanguage pujamodelsz**z** z Category: rgi,riz Description: zRegion: z Language: rr durationHrszN/A noOfPujarisisPopularModelFu ⭐ (Popular) proceduresz **Sacred Rituals (z rituals)z:** proceduretitleUnknownu • z **Service Details:** u • Duration: z hours u • Number of Pujaris: modelSellingPrice pujariCost samagriCost serviceFeez **Pricing Information:** u • Total Price: ₹,u • Total Price: z **Price Breakdown:** u. • Guru Dakshina (goes 100% to pujari): ₹u0 • Samagri (pure organic puja materials): ₹u • Service Fee: ₹z> ============================================================ z<============================================================) r#rsr enumeraterZintfloatr\rn)rrQr result_partsrbrMrTrVrr puja_models puja_infodescidxmodelduration num_pujaris is_popular popular_tagr proc_dataprocrprice pujari_cost samagri_cost service_feerrrrqsn                     .    z!PujaAPICache._format_puja_results)FFF)r) __module__ __qualname____doc__ CACHE_FILEstrrrrr/r:rEboolrIrrcrryr}rrrrrrr s $"; $ cr rcCstdurtatS)z(Get or create the global cache instance.N)_cache_instancer rrrrget_cache_instancesrFrer~rcst}|j|||dIdHS)a Convenience function to search puja information with optional LLM enhancement. TOKEN OPTIMIZATION: - By default (use_llm=False): Uses fast keyword matching, zero LLM tokens - When use_llm=True: Falls back to LLM for semantic matching if keyword search fails - LLM only sees lightweight index (names, IDs, categories), not full data - Full details fetched only for matched pujas SPIRITUAL-FIRST APPROACH: - include_pricing=False (DEFAULT): Returns ONLY spiritual/ritual details - include_pricing=True: Returns spiritual details + pricing breakdown Args: query: Search query for puja information use_llm: Enable LLM-based semantic matching for complex queries (default: False) include_pricing: Include pricing information in response (default: False) Returns: Formatted puja information Examples: # Spiritual details only (no pricing) await get_puja_info("Ganapati Homam") # With pricing information await get_puja_info("Ganapati Homam", include_pricing=True) # Complex semantic search with LLM fallback and pricing await get_puja_info("puja for new baby", use_llm=True, include_pricing=True) )r~rN)rr)rer~rcacherrr get_puja_infos rcs"t}|jddIdH}|duS)zv Force refresh the puja cache from API. Returns: True if refresh successful, False otherwise T)rFN)rrI)rr0rrr refresh_cachesrr)rr loggingosrrtypingrrrpathlibrr= getLoggerr)rrr$r?r rrrrrrrrrrs(   9$