Insanely expensive and ended abruptly. Got: ` Unexpected token 'd', "data: {"id"... is not valid JSON` Weird. Okay, I think your node isn't taking care of cache pricing as it's a custom upstream. I see that the response contains the cache read data in it. The current main fixes this for some direct upstreams like deepseek, maybe it also works for custom upstreams. \ @Thefux In the usage chunk i got: ``` \"usage\": {\"prompt_tokens\": 45763, \"completion_tokens\": 193, \"total_tokens\": 45956, \"prompt_tokens_details\": {\"cached_tokens\": 43520, \"orchestration_input_tokens\": 0, \"orchestration_input_cached_tokens\": 0}, \"completion_tokens_details\": {\"reasoning_tokens\": 77, \"orchestration_output_tokens\": 0} ``` But i was charged full prompt token price here.