A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Gateways Count Every Token And Charge For Almost None Of Them," Kin Lane, October 23, 2026, https://apievangelist.com/2026/10/23/gateways-count-every-token-and-charge-for-almost-none-of-them/
Marisol read the post on a Friday afternoon, between a failed deploy and the end of her sprint. She is a platform engineer at a mid-sized freight-software company, and her team runs the gateway that sits in front of their new assistant feature. She had opened the post expecting a vendor comparison. It turned out to be a count.
The count was 884 policies across twelve gateways, sorted into eighteen areas. The AI row was the biggest, with 120 entries. The monetization row had ten, spread over four gateways. She read that twice. Six of the ten were hand-offs to someone else's billing system.
Her first reaction was mild irritation. She thought the author was treating a division of labor as a defect. Billing already lives in a billing system, finance owns it, and nobody on her team wants a gateway deciding what a customer owes. A policy catalog with an empty monetization row might simply mean people made a sensible choice.
Then she got to the part about cost controls. The post lists about two dozen of them, including token quotas, token metrics and semantic caches, and says of them: "Every one of these points inward." She thought of the dashboard her team had built the month before. It had a token ceiling per route and an alert when spend crossed a line. It was careful, and it was all about protecting the company's own bill. Nothing in it said what a call was worth to the person making it.
That was uncomfortable, because she had been proud of that dashboard.
She still didn't buy the post's whole argument. The author expects the monetization row to fill in over the next year, and Marisol wasn't convinced the gateway was the right home for prices. But she couldn't wave away the sentence she kept returning to: "A gateway that can compute the cost of a call but not attach a price to it is only doing half the work." Her team computed the cost, and then a nightly export carried that number to a system that wouldn't see it until the next day. The post had a line for that too. "Measuring cost tells you how much you lose on each call."
She didn't open a proposal or schedule a meeting. She opened a blank note and made two columns. In the first she listed every policy currently enabled on the assistant routes. In the second she wrote a plain yes or no: does this protect our bill, or does it help anyone be charged?
The first column had nine entries. The second column had no yeses beside anything that touched a price.
She saved the note in the team's shared folder with a one-line description, so that on Monday she would at least be arguing from a list. Then she closed the laptop and went to find out why the deploy had failed.