Agent loop ka kharch "ek call guna turns ki sankhya" nahi hai, aur farq chhota nahi. API ki koi smriti nahi, isliye har turn pehle ka sab kuchh dobara bhejti hai: system prompt, tool definitions, aur har message tatha tool ka nateeja. Aathvi turn wo sab bhejti hai jo pehli se saatvi ne bheja, saath mein wo bhi jo unhone banaya. Isse kharch conversation ki lambai ke saath nahi, uske varg ke saath badhta hai — isiliye jo loops aazmane mein saste lagte hain wo hote nahi. Yahaan loop turn-dar-turn chalaya jaata hai, cache wahin lagayi jaati hai jahaan wo sach mein lagti hai, aur wo turn named hoti hai jis par window bhar jaati hai.
Features
Har turn alag se aanki jaati hai, dobara bheje history samet
Cache sirf sthir prefix par laagu — yahi imaandaar model hai
Tulna ke liye wahi loop bina cache ke bhi aanka jaata hai
Sirf smritiheenta ki wajah se dobara bheje tokens ginta hai
Wo turn named karta hai jis par context window bhar jaati hai
Bulk rate ek switch se
Turn-dar-turn dand-chitra, taaki badhat dikhe
Jaanch ki tithi ke saath rates
Agent Loop Cost Estimator kaise use karein
Model aur apekshit turns chuniye
Sthir prefix, output aur tool nateejon ke aakaar bhariye
Yatharthvadi cache hit rate tay kijiye
Kul, bachat aur bhar jaane ka bindu padhiye
Example
Input
8 turns, 4K prefix, 1.5K tool results
Output
Turn 8 sends 19.4K tokens — turn 1 sent 4.5K
Badhta history hai, kaam nahi.
Common errors aur troubleshooting
Mera asli bill isse zyada hai. — Aam taur par tool ke nateeje: wahi sabse bada aur sabse kam anumanit input hain. Saamanya nahi, sabse bade nateeje ka aakaar lijiye.
Cache ki bachat bahut achhi lag rahi hai. — Sirf sthir prefix ko cache yogya maana jaata hai, jo pehle se hi satark maanyata hai. Aapka prefix turns ke beech badalta ho to hit rate ghataiye.
Kehta hai window bhar jaati hai. — Loop khatam hone se pehle conversation model se badi ho jaati hai. Compression, context ka editing, ya tool nateejon ka aakaar ghatana — asar ke isi kram mein.
Apne token aakaar kaise jaanoon? — Ek asli turn token counter se naapiye aur wahi aankde lijiye. Jawab ka aakaar sateekta se zyada maayne rakhta hai.
Aksar pooche jaane wale sawaal
Wahi kaam ek call mein karne se loop mehnga kyun hai?
Kyunki har turn poori conversation dobara bhejti hai. Das turns yaani das input calls nahi, balki badhti hui conversation ka jod — isiliye kharch ki rekha upar mudti hai.
Kharch sabse zyada kya badhata hai?
Tool nateejon ka aakaar, aam taur par bade antar se. Output tokens prati nag mehnge hain par bahut kam hote hain; har turn ek panna JSON lautane wala baatooni tool hi saste loop ko mehnga bana deta hai.
Kya 90% hit rate yatharthvadi hai?
Sthir system prompt aur tay tools list ke liye haan. Prefix mein kuchh bhi prati-request badalta ho to wo shunya ke kareeb hai; ye pata karne mein cache planner madad karta hai.
Kya bulk rate leni chahiye?
Sirf tab jab kaam antahkriyatmak na ho. Wo bill aadha kar deti hai aur beech mein dakhal dene ki gunjaish le leti hai, jo evaluation aur bulk processing ke liye theek hai, kisi prateekshart agent ke liye nahi.
Ye kitna sateek hai?
Ye ek model hai, koi quotation nahi. Ye aapke aankdon se sahi aakaar batata hai — badhat, cache ka asar, bhar jaane ka bindu. Prakashit rates badalti hain, isliye jaanch ki tithi saath dikhti hai.