How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ISO Standards MUST NOT Be Behind A Paywall

November 17th, 2026 · Kin Lane
ISO Standards MUST NOT Be Behind A Paywall

I have a lot of advice for the ISO and other standards bodies about what they need to do to modernize their approach and keep meeting their mission. I’ve had many conversations with classic standards bodies that are stuck in old technical, business and political models, trying to figure out how to reach a more modern audience without being rendered obsolete.

I’m currently working through my advice for the ISO on its approach to APIs, and as a result its approach to AI, building on my work with APIs.io and the Kin Score. But the most important piece of advice I have comes before any of the technical details. The ISO MUST stop putting standards behind a paywall.

Humans shouldn’t have to pay to learn a standard

As a human, you shouldn’t have to pay money just to learn about a standard. As a company planning your road map, you shouldn’t have to pay to learn and understand what is possible. And domain experts like me shouldn’t have to pay to be able to tell stories, publish examples, and develop the content, code and artifacts that amplify and support a standard.

Every one of those people is someone who would spread the standard for you. The paywall turns them away at the door.

Agents can’t be fluent in what they can’t read

If you want agents to speak and know your standard, it needs to be crawlable, indexable and available for training. So does all the content, the artifacts and the other material domain experts publish about the benefits of the standard.

If an agent can’t access the standard, it won’t be fluent in the standard. Developers increasingly ask an agent how to implement something before they ever go looking for a specification. If the answer is vague or wrong because the standard was locked away, the agent will reach for whatever it does know, and that’s often something else. A standard that agents don’t know isn’t much of a standard in this new AI-powered landscape.

Charge for certification, not for the PDF

I get it. You need to generate revenue, and you do that by selling access to the PDFs. You’ve told yourselves this for years. That business model needs to change.

You should charge for certifying against the standard, and let everything else become your marketing and education. This is the API way. Give away the documentation, the contract and the examples, and charge for the thing that carries real value and trust. It’s also how the desktop, web, mobile and other applications you already use get done what they get done with standards. The specifications those platforms run on are open, and the money is made elsewhere.

The revenue from certification will be greater than the revenue from gatekeeping PDFs, because the playing field will be so much larger. More people learning the standard means more companies implementing it, and more companies implementing it means more of them who need to prove they did it right. You’ll better achieve your mission by making this one change to your business model.

What comes next

I have a lot more advice. Unfortunately, the business and licensing model of your standards prevents me from demonstrating what that advice is and championing the possibilities, because I can’t openly publish examples and artifacts built from standards I’d have to pay to read and am not licensed to share. So I’ll pick one of your more open standards and start that conversation next.