The $29 figure is doing a lot of quiet work in this story, because that's exactly what a Pro plan costs. So the real message isn't really a budget cap, it's 'stop expensing API tokens and expense a subscription instead'. I'd bet a chunk of that $1,000 spend was people wiring API access into internal tooling and prototypes, which feels productive right up until finance sees the invoice and has no idea what any of it maps to. The part that'll actually sting is that this is how a lot of shadow automation dies: not because it didn't work, but because nobody could explain the line item. At least a hard cap forces the conversation that should've happened months earlier.