+ iHjNRt^RIHt^RIt]P!]4tRRltR#)zWNon-streaming chat completions that still feed response headers to the credits capture.) annotationsNcV^8dQhRR/#) api_kwargsdict)formats"B/home/ubuntu/.hermes/hermes-agent/agent/chat_completion_headers.py __annotate__r s$c \VRR4p\VRR4R8wg\VRR4RJd'VPPP!R/VB#\\\VR R4R R4R R4pVf'VPPP!R/VB#TP!R/VBp^R IHpV!V4'gVP 4#VPVPVPVP3F pV!V4K VP 4# \d\PR RR7KEi;i)aNon-streaming ``chat.completions.create`` that also feeds the response headers to the rate-limit / credits capture, as ``_chat_stream_created`` does for streams. The parsed ``ChatCompletion`` drops headers, so without this a non-streaming turn never observes ``x-nous-credits-*`` (usage-window ``spend_source`` / gauges go stale). The SDK's ``with_raw_response`` returns the same request with headers attached; a client without it keeps the plain call. Usage-window plans only: every other provider, and a Nous session not yet known to be on a window plan (the session-start seed or a stream header establishes it), keep the plain call; headers are captured only when the response itself is the usage-window kind. A capture failure never fails the turn. _credits_stateNprovidernousis_usage_windowFTchat completionswith_raw_response)response_is_usage_windowz#non-streaming header capture failed)exc_infor)getattrrrcreateagent.credits_trackerrparse_capture_rate_limits_capture_credits_capture_nous_model_switch_check_openrouter_cache_status Exceptionloggerdebug)agentclientrstateraw_apirawrcaptures&&& r "_chat_completion_capturing_headersr( s4 E+T 2Euj"%/75BSUZ3[cg3g{{&&--; ;;ggffd;]DQSfhlmG{{&&--; ;; .. &: &C> #C ( (yy{..0F0F44e6Z6Z\ O CL\ 99; O LL>L N Os D(("E E)__doc__ __future__rlogging getLogger__name__r r(rr r r.s#]"   8 $r