)jSWdZddlmZddlZddlZddlmZmZmZddl m Z ddl m Z ddl mZejeZedd g Zdd ZGd d ZeZddddZdddZej1deefddZej1deefddZej7ddZej1dddZy) u routers/tavus.py — Tavus CVI live video roleplay integration Endpoint: POST /api/tavus/start-session All credentials come from config.py / .env — never hardcoded here. ) annotationsN) APIRouterDepends HTTPException) JSONResponse)settings)get_current_userz /api/tavustavus)prefixtagsc|sy|j}t|dk\r%|d|dk(r|ddvr|ddj}|S)Nr)"')striplen)rawss g/Users/priyanka/Documents/AI_Agent_Assessment/pepole_hub_candidate/people_hub_candidate/routes/tavus.py _clean_envr sO  A 1v{qtqu}1); aGMMO HcLeZdZedZedZedZedZy)_TavusSettingsc4ttjSN)rr TAVUS_API_KEYselfs r tavus_api_keyz_TavusSettings.tavus_api_key-s'1(2H2H'I Irc<ttjxsdS)Nhttps://tavusapi.com/v2)rrTAVUS_BASE_URLr s rtavus_base_urlz_TavusSettings.tavus_base_url/s'1(2I2I'J'gNg grc4ttjSr)rrTAVUS_REPLICA_IDr s rtavus_replica_idz_TavusSettings.tavus_replica_id1'1(2K2K'L Lrc4ttjSr)rrTAVUS_PERSONA_IDr s rtavus_persona_idz_TavusSettings.tavus_persona_id3r*rN)__name__ __module__ __qualname__propertyr"r&r)r-rrrr,s: II gg LL LLrrrdefaultcX|D]$}|j|}|dvst|cS|S)uGRead the first non-empty value from any of the given dict keys. The People Hub external roleplay API returns scenarios in a loose snake_case-or-camelCase shape — we accept both styles here so the Tavus persona prompt comes out the same regardless of which convention the upstream uses for a given field. )Nr)getstr)rr4keyskvs r_pickr;9s3 GGAJ J q6M Nrct|dddddd}t|dd d d d }t|d ddd}t|ddddd}t|ddd}t|dddddd}t|dd d!d"d#}t|d$d%d&d'} |xsd(j} d(} | rd)| d*|d+| d,|d- } d.|d/|| d0|d1|d2|d3|d4|d5| d6S)7ulMap an external roleplay scenario (raw dict from the People Hub API) directly into the Tavus persona system prompt. Everything we need lives on the dict already — we do NOT need a Pydantic Scenario object, and we do NOT need to look anything up in the local data/scenarios.json store. The same dict shape is what the lobby renders and what voice / video role play already consume, so passing it straight through guarantees the Live AI flow uses the same scenario the candidate actually picked. ``candidate_name`` is the candidate's display name (from the People Hub login envelope, stashed on the frontend). When provided, it is woven into the prompt so the AI opens with "Hi , …" instead of asking the candidate to type their name — that was the "the AI keeps asking who I am" bug we saw in user testing. ai_character aiCharacter characterpartnernpcz AI Characterr3contextscene background descriptionzHave a realistic conversation.ai_personality aiPersonality personalityz6Be realistic and challenging. Stay fully in character. learner_role learnerRole user_roleuserRole Candidate difficultylevel Intermediate cat_labelcatLabelcategory_label categoryLabelcategoryGeneral language_name languageName lang_namelangNameEnglishturns max_turnsmaxTurns8ru> IMPORTANT — CANDIDATE IDENTITY: - The candidate's name is z. They are the z.. - Greet them BY NAME at the start (e.g. "Hi u, ..."). - Do NOT ask the candidate to introduce themselves or to state their name — you already know who they are. - Do NOT ask what their role is — you already know they are playing the z<. - Jump straight into the scenario in your very first turn.zYou are z>, a character in a professional training roleplay. SCENARIO: z YOUR PERSONALITY & BEHAVIOUR: z> RULES: - You are speaking with someone playing the role of: z - Difficulty: z - Category: z - Language: u - This is a training simulation — be realistic but constructive. - Never break character. Never reveal you are an AI unless directly asked. - Keep responses conversational and appropriately emotional for your character. - Aim for z conversation exchanges total.)r;r) rcandidate_namer=rBrFrIrNrUrWr\nameidentity_blocks r_build_system_promptrcHsm$3 {IW\ftuL3 7L-YyzG3 0/=[STN3 {J`klL3 g~NJ3 Z9I?\fpyzH3jbklM3j#NE  b ' ' )DN ))-ol^L<<@6B!"./I  J  <.!Y~./**8)9:@@L~N# %j!$o&G9 ; rz/start-sessioncKtjs tdd|jdxsi}|jdxsdj }|jdxs|xsijdxsdj }|jdxs|xsijd xsdj }t |t r|s td d t|d d xstj}t|ddxstj}t|dd ddd}|s tdd|d|d} |r|| d<nt||dd| d<tjd|r|dddznd|xst|dd ||xsd i| d| jdddd!t| jddd!kDrdndzitjxsd"jd#} | d$} t!j"d%&4d{} | j%| tjd'd(| )d{} dddd{ j.d/vr| j0r| j0dd0nd1}tj)d2| j.| ||xsd |d}| j.}|d3k(rd4}n|d5k(rd6}n|d7k(rd8}n|d9k(rd:}td+d;|d<|d=| | j3}|jd@d}|jdAd}|sbtj)dB|td+dCt |t rt7|j9nt;|j,tjdD|t=||dES77k7^#1d{7swYoxYw#t j&$rF}tj)d*| |td+d,| d-|j*j,d.|d}~wwxYw#t4$r1tj)d>| j0dd9td+d?wxYww)Fu Start a Tavus CVI live video session for a scenario. Returns { conversation_url, conversation_id } to embed in the frontend iframe. Source of truth for the scenario is the request body. Scenarios for the role-play lobby come from the People Hub external API (NOT from data/scenarios.json), so we accept the full scenario object inline — same shape the lobby renders and that voice / video role play already consume. We do NOT consult the local JSON store here; if the client sends the scenario, we use it. This avoids the earlier 404s where data/scenarios.json had different ids than what the lobby was actually showing. Body shape: { "scenario": { ...full roleplay dict from the People Hub API... }, "access_key": "", # optional, for logging "scenario_id": "" # optional, for logging } zoTavus CVI is not configured. Set TAVUS_API_KEY in your .env file. See /tavus-guide for full setup instructions.detailscenario scenario_idr access_keyr`razdscenario object is required. Reload the lobby and pick a scenario again, then try Live AI Role Play.r)tavusReplicaIdr-tavusPersonaIdtitleRoleplayr3N<zLive AI Role Play is not fully configured: no Tavus replica id is set. Add TAVUS_REPLICA_ID to .env, or set tavus_replica_id on the scenario object.u RolePilot · ) replica_idconversation_name persona_idi conversational_contextzM[Tavus] starting session ak=%s scenario=%s replica=%s persona=%s body=%s…z(none)idz(inline)xr$/z/conversations4@timeoutapplication/json x-api-keyz Content-Typeheadersjsonz'[Tavus] network error talking to %s: %sCould not reach Tavus at zR. Check your network connection and the TAVUS_BASE_URL setting. Underlying error: : iX (empty body)u<[Tavus] API error %s at %s — replica=%s persona=%s body=%sz1 Likely cause: TAVUS_API_KEY is wrong or revoked.iz> Likely cause: your Tavus plan is out of conversation minutes.izL Likely cause: replica_id or persona_id doesn't exist on this Tavus account.iuN Likely cause: request shape rejected — check that the replica_id is active.zTavus API returned HTTP .z Tavus response: z![Tavus] response was not JSON: %sz#Tavus returned a non-JSON response.conversation_urlconversation_idz+[Tavus] no conversation_url in response: %szQTavus accepted the request but did not return a conversation_url. Response keys: z+[Tavus] session started conversation_id=%s)rr)_sr"rr6r isinstancedictr;r)r-rcloginforr&rstriphttpx AsyncClientpost RequestErrorerror __class__r. status_codetextr Exceptionlistr8typer)body current_user raw_scenariorirjr`rqrsrnpayloadbaseurlclientrespexc body_previewhintscdatarrs rstart_tavus_sessionrs.    @  88J'-2LHH]+1r88:K    B # #L 1   eg  !"   B # #F +   eg  lD )  E   l.0@A    l.0@A    , DSb IE  ?  $(,UG4G  *  -A~,^_d`d,e()HHW$.BQ% HDu\4DJ,* i7 i,gkk:RTV.WX\Y\.]jmnunyny{SUWoXkY\_k_afeg/h i     :!: B B3 GDV> "C $$T22f$&$4$4$6 %D32* z)+/))tyy#  J   c:z/GZ   9FD 3YSD 3YaD 3YcD *2$av6##/.2  Oyy{ xx 2B7xx 126O  ?F 4(24(>4 $DJDWDWXZ  HH :OL -=Rab ccU33222      ;S#F +D62..1mm.D.D-ERuN    \ O 5tyy#GC(MNNOsHQ0 O#N8$O')ON;O O N>!O%BQ0<P3 B,Q08O;O>OOO OOP0*AP++P00Q03:Q--Q0z/create-personac :Ktjs tdd|jdxsi}|jdxsdj }t |t r|s tddt|}t|d d d d d}tjd4d {}|jtjdtjdd||ddd {}d d d d {jdvr*tdd|jd|jd d|jjdd}|rt j#d||xs||||dS777#1d {7swYxYww)u  Pre-create a Tavus persona for a scenario. Call this from the admin panel when publishing a scenario to speed up future video session starts (persona carries the system prompt). Accepts the scenario inline in the request body — same shape as /start-session — so admins paste the People Hub scenario JSON and don't depend on the local data/scenarios.json being up-to-date. A legacy scenario_id is also accepted; when given it is logged only (no lookup) so the persona_name reflects what the admin sees. rezTAVUS_API_KEY not configuredrfrhrirrkzscenario object is requiredrnraror3NPrzr{z /personasr}r~full) persona_name system_prompt pipeline_moderrrz$Tavus persona creation failed: HTTP u — rrsz3[Tavus] persona created persona_id=%s scenario=%s)rsrir)rr"rr6rrrrcr;rrrr&rrrrr) r_rrirrrrrss rcreate_tavus_personarWs   C(FGG88J'-2LHH]+1r88:K lD )C(EFF(6M,LSbQL  ..&[[  ! +-- 2 !-!.!' !   /. z) 9$:J:J9K5QUQZQZ[_\_Q`Pab  r2J  A  3| ""$ A/  /...s[B,F.F/F2>F0F1F5 FFBFFFF F FFz/healthc rKtj}tjxsdjd}|st ddd|dSt |dk\r|d d d |d d d t |d}ndt |d} t jd4d {}|j|dd|id {}d d d d {j}|jr|jd dnd}|dk(rg} |j} t| t r%t| jdt"r| d}nt| t"r| }dd||t |tj&xsd tj(xsd d!Sd"} |d#k(rd$} n|d%k(rd&} t ddd'|| d(|||dS777#1d {7swYxYw#t j$r9}t ddd|d|jjd|||dcYd }~Sd }~wwxYw#t$$rYwxYww))uDiagnostic endpoint — verifies the configured TAVUS_API_KEY is accepted by Tavus, without starting a (billable) conversation. Returns a JSON status so an operator can curl this from the box: curl http://localhost:8000/api/tavus/health Status meanings: • ok=true → key is valid, replicas list reachable • ok=false → field `detail` explains what went wrong Intentionally public (no auth dep) because the whole point is to let operators debug misconfiguration before any user can log in. The response NEVER leaks the API key itself — only its length and first/last few characters are echoed so the operator can confirm the .env value matches the Tavus dashboard without a copy-paste mistake. r$ryreFz>TAVUS_API_KEY is empty. Set it in .env and restart the server.)okrgr)rcontentNrvz (len=)z(len=z, too short to redact safely)g$@r{z /replicasr)rrrr)rrgkey_fpri,rrrTzTAVUS_API_KEY is valid.z (not set))rrgrr replica_countconfigured_replica_idconfigured_persona_idrru — Tavus rejected this exact key. Double-check the value in .env against the Tavus dashboard, ensure there are no surrounding quotes / whitespace, and RESTART the server after editing .env (Python doesn't hot-reload env vars).iuY — the key is recognised but lacks permission for /replicas. Check the Tavus plan tier.zTavus returned HTTP z Body: )rr"r&rrrrrr6rrr.rrrrrrrr)r-) keyrrrrrrrreplicasrrs r tavus_healthrsv&  C    :!: B B3 GD Z   3x1}G9CBCzCz;S "?@ $$T22f  & "$c*$D 32(   B&*ii499Tc?^L Sy 99;D$%*TXXf5Et*L<D$'#7$"!(m%'%8%8%GK%'%8%8%GK   D Sy G sj ,RDgl^L   q3  3222     5dV2cmm>T>T=UUWX[W\]      0   sA?H7GF;G G<F>=G G G G0H7AH(A"H7;G>GGG G GGH%,.H H%H7 H%%H7( H41H73H44H7z/webhookcK|jdd}|jdd}tjd|||dk(rD|jdg}|jdd}tjd t||d d iSw) z Receive Tavus webhook events (conversation.ended, transcript_ready). Register this URL in your Tavus dashboard: POST https://your-domain.com/api/tavus/webhook eventrrz-[Tavus] webhook event=%s conversation_id=%szconversation.ended transcriptduration_secondsrz-[Tavus] session ended turns=%d duration=%dsrT)r6rrr)rrrrdurations r tavus_webhookrskk'2.Ekk"3R8OHH rs # 55** g! ,gY 7  MM13 :z 7>?O7PNdNdb -45E-F< <~IiiXZr