The only other pricing data available suggests its the context cache that's eating usage. If you have a big context on a 5 min cache (default) you're essentially sending the whole context every time you take a break from the api. You can configure 1 hr TTL which should help if you run long heavy sessions like me. That's been my theory lately. Still need to get my company admin to let me test lol.