<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-Design on A Field CTO Perspective</title><link>https://gaberger.github.io/tags/api-design/</link><description>Recent content in Api-Design on A Field CTO Perspective</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 09 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://gaberger.github.io/tags/api-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Delivering APIs for AI</title><link>https://gaberger.github.io/2026/07/delivering-apis-for-ai/</link><pubDate>Thu, 09 Jul 2026 00:00:00 +0000</pubDate><guid>https://gaberger.github.io/2026/07/delivering-apis-for-ai/</guid><description>&lt;p>The rise of AI agents and autonomous systems is fundamentally changing how we design and deliver APIs, shifting from human-centric interfaces to AI-native integration patterns that require new architectural thinking.&lt;/p>
&lt;h3 id="the-inflection-point">The Inflection Point&lt;/h3>
&lt;p>Technology innovation has repeatedly transformed how we build systems. From the fourth-generation programming languages (4GL) of the 1990s that abstracted database operations to today&amp;rsquo;s AI-powered code generation, each wave has forced us to rethink fundamental assumptions. We now stand at another such inflection point: the transition from human-interface (HI) APIs to agent-interface (AI) APIs.&lt;/p></description></item></channel></rss>