"In a previous post on agent experience (AX), we wrote that “Artificial intelligence tools are bad at inferring context or reading between the lines,” and that “content designed for consumption by AI should look less like a blog post and more like a legal contract. Great agent experience is all about being as clear and predictable as possible.”

Where possible, we need to eliminate assumptions that only make sense to human readers. LLMs aren’t as forgiving of undocumented constraints, inconsistencies, or vague descriptions as a human reader might be. If you’re struggling with that, we can lean on AI tools — it makes sense that AI would know what AI likes, right? — for identifying some of these gaps.

When we covered AI assistants for API developers, for example, we identified LintGPT as a useful tool for its ability to automate the creation of an API style guide, enforce specification standards, and even catch breaking changes before deployment.

API specifications are no longer just documentation. They’re living contracts with machines, which increasingly have the power to read and interact with said contracts. Improving clarity, consistency, and precision might create a few initial headaches, but it opens the door to smarter tooling, faster iteration, and APIs taking pride of place in an increasingly AI-driven ecosystem."

https://nordicapis.com/how-llms-are-changing-the-way-we-build-api-specifications/

#AI #GenerativeAI #LLMs #APIs #APIDesign #APISpecifications

How LLMs Are Changing the Way We Build API Specifications | Nordic APIs |

How LLM-powered AI agents are changing API specification design and why machine-readable no longer means machine-optimized.

Nordic APIs

"In October 2025, from a total of 61 members of the technical steering committees of popular open-source API formats, about 54% are there acting for their employers. More than half of all committee members are there, supposedly, representing the interests of their employers. And this is the norm. To the point that some companies proudly publish it as a requirement on their job ads. “Foster influence across open-source, enterprise, and partner communities” was in a recent role description for a Head of Developer Relations job. It further explained that nurturing relationships with open-source specifications, to help influence future versions, was part of the role’s objectives. Companies big and small, many of them API vendors, sponsor open-source API specification formats. In exchange, they get a few seats at steering committees, making it possible to drive the direction of those projects."
https://apichangelog.substack.com/p/the-hidden-trust-problem-in-api-formats

#API #APIFormats #APISpecifications #SoftwareDevelopment #OpenSource #APIDesign

The Hidden Trust Problem in API Formats

How much should you trust OpenAPI and other formats?

The API Changelog
Introducing Cadl: Microsoft’s concise API design language

With Cadl, you can write a 500-line OpenAPI definition in 50 lines of code. It’s a logical way for architects and developers to construct and constrain APIs.

InfoWorld