A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Rethinking The API Free Tier In The Agentic Age," Kin Lane, November 6, 2026, https://apievangelist.com/2026/11/06/rethinking-the-api-free-tier-in-the-agentic-age/
Marisol read the post on a Friday afternoon, between a failed deploy and a pricing meeting she had been dreading. She was a platform engineer at a company that sold a mid-sized API, and she had been avoiding the free tier question for weeks. The post was dated November 6th, and it landed in her feed with the kind of timing that made her suspicious of her own feed.
She agreed with the first part immediately, and that annoyed her. The author said the free tier had been a staple of plans and pricing for over 15 years and was now shriveling, and that the cause was an agentic denial of service rather than a company pulling up the ladder. Marisol had watched her own logs for a month. One key, signed up with a throwaway address, had hit her endpoints in a loop that never seemed to tire. She had called it a spike in a status update, which now felt like a polite word for it.
Then the post got to the part she liked less. The author wrote that part of the reason free tiers suffer is that most companies were doing them for the wrong reasons, looking to inflate numbers rather than incite innovation. She bristled. Her own team had reported signups every quarter, and she had been proud of the chart. She sat with that for a while, aware that the chart had never once told her whether anyone built anything.
The remedy was blunt. "Put a price tag on the front door." Then, a few lines later, "Require a corporate email." She winced at that one. She thought of the student in another country who had once emailed her a thank-you for a free key, the sort of developer the free tier was supposed to be for. The post did not seem to have much room for that person, though it did ask whether providers could still offer exploration of their APIs, their tools and their resources. She noticed the question was left open, and she appreciated that it was not pretending to have solved it.
She did not accept the whole argument. Charging for access as a filter for "freeloaders and riffraff" sounded to her like a description of customers she had never met, and she suspected that a credit card from day one would filter out plenty of honest people too. But she could not say the agent loop in her logs was an honest person. The author had written that he got why leadership wanted to close the front door, and that things had gotten noisy and aggressive. That was fair, she thought, and it was also exactly what her VP would say on Monday.
She did not draft a policy. She opened a blank page in the team doc and listed what the signup form currently asked for, line by line, which turned out to be an email address and nothing else. Beside it she left an empty column headed with the question of what each field would cost a real developer. She sent it to two colleagues with a single sentence asking them to fill in the second column before the meeting.