Contents

• Principles of the IGT-API Framework

• Interesting Content for the week

• Product updates/New releases

• FeedBack & Share

• Upcoming Conferences

Principles of IGT-API

In my previous post, I wrote about the values of the IGT-API framework. As I mentioned in that post, the IGT-API a framework to help organisations create and refine their API delivery operating models. IGT-API has ten principles, an dI introduce the first two below.

1. Production: Map your current and target API production workflow and lifecycle.

What it involves: Map out the steps API developers go through to create an API. These steps can be grouped into the lifecycle stages (for example, design, development, documentation, testing, deployment, monitoring, deprecation, and sunsetting). Also, note what technologies are used in these stages. Use this workflow and lifecycle map to get cross-team alignment on areas of inefficiency, time waste, and developer frustration. Based on this, create a target state workflow map, detailing improvement interventions.

Why this is important: Understanding the current state of the API production workflow helps you identify the priority areas for intervention, a target state workflow, and an action plan.

2. Consumption: Map your current and target API consumption workflow and lifecycle.

What it involves: Map out the steps API consumer developers go through to discover and integrate with your API. These steps can be grouped into API consumption lifecycle stages, for example: discovery, onboarding, integration, testing, deployment, operation, maintenance, and sunsetting. Also, note the categories of consumers and what technologies they use. As in the Production Principle, use this workflow to get consensus on areas of inefficiency and poor consumer developer experience. Create a target state map with improvements applied.

Why this is important: Understanding the current state of your API consumption workflow helps you identify the priority areas for intervention, a target state workflow, and an action plan.

In future posts, I’ll explore the other IGT-API principles. In the meantime, enjoy the set of curated links we have prepared for you this week!

Interesting Content for the week

Runtime AI Governance

Inaugural MCP Dev Summit Charts AI Integration's Future: The article covers the first-ever Model Context Protocol (MCP) Dev Summit held in San Francisco in May 2025. This summit focused on the future of AI integration and gathered developers working on MCP.

Beyond the Noise: Achieving Accurate API Inventory with AI: Eric Schwake discusses the growing challenge of managing and securing APIs in a rapidly evolving digital landscape, particularly with the advent of AI-generated APIs. The article highlights the critical need for a unified and accurate API inventory to mitigate security risks and ensure compliance.

Monetizing MCP (Model Context Protocol) Servers with Moesif: This article explains the importance and methods of monetising MCP servers using Moesif, given MCP's role as a foundational layer for AI systems enabling LLM and AI agent interactions with external tools and data.

When AI Agents Go Rogue: What You’re Missing in Your MCP Security: Salt Security’s Roey Eliyahu discusses a significant shift in how software operates, moving towards Agentic AI and its implications for security, particularly concerning the MCP.

Hackers Are Using Robots to Break Your Business: Damilola Akinsola, warns that AI and automation are fundamentally transforming cyberattacks, especially those targeting APIs, rendering traditional security measures inadequate.

 Controlling costs when building with AI : Ed Stephinson discuss incident.io’s cost control approach to building with gen AI applications. The central theme is achieving granular control and visibility over AI spending.

API Production Governance

The Top API Architectural Styles of 2025: J Simpson discusses the significant diversification of API architectural styles since REST's introduction in 2000. While REST remains dominant, used by 92% of organisations, the growing need for real-time data has propelled other architectures to prominence.

Overhaul of Agent Gateway supporting A2A, MCP, and Kubernetes Gateway API: Christian Posta and John Howard announces a major overhaul of Agent Gateway, transforming it into a comprehensive AI-native gateway. This aims to facilitate structured, secure, and scalable communication between AI agents, tools, and large language models (LLMs), addressing limitations of traditional API gateways in agentic environments.

Ambassador Labs + Gravitee: What Our Acquisition Means for You: Steve Rodda announces the acquisition of Ambassador Labs by Gravitee. The acquisition is a strategic move that positions Ambassador’s products under the Gravitee umbrella.

 Amazon API Gateway Adds Dynamic Routing Based on Headers and Paths: Introduction of new dynamic routing capabilities for Amazon API Gateway, allowing users to route API requests based on HTTP header values, either independently or combined with URL paths. This significantly simplifies previous methods that often led to complex API structures.

Videos

Leading up to a FINOS Architecture as Code meeting, James Gough, Distinguished Engineer at Morgan Stanley and O’Reilly author, demos some experimental work on integrating the Common Architecture Language Model (CALM) and tools into LLM platforms like Claude using MCP. For the code for this demo, see the GitHub repo.

Product updates/New releases

Rebranding Speakeasy: This isn’t a product update or release, but we thought we would stick this news item in this section. Speakeasy, erstwhile known for producing API SDKs, is shifting its focus to “… becoming the MCP company to help every API platform successfully transform into an AI platform.“ The rebranding aims to align the company's visual identity with its evolved mission of transforming API platforms into AI platforms.

Announcing Kubernetes Ingress Controller 3.5: Kong Ingress Controller (KIC) version 3.5, focusing on new features and deprecations designed to enhance efficiency and align with the evolving Kubernetes Gateway API.

Princess Beef Heavy Industries (pb33f) Launches Workspaces for OpenAPI Doctor: pb33f, the maker of the Vacuum API linter, OpenAPI Doctor (for OpenAPI description editing, exploration and governance) and the WireTap API diagnostics tool, has rolled out a new "Workspaces" feature for OpenAPI Doctor. Announced in the 21st July issue of the pb33f newsletter (so we don’t have a direct link to it), this update introduces authentication for OpenAPI Doctor which unlocks the workspaces feature. With workspaces, users can now create and manage up to five private, persistent work areas where all their changes are automatically saved (see screenshot below). This feature marks a clear step towards a more personalised and secure experience for OpenAPI Doctor users.

Feedback & Share

I appreciate your feedback. If you find my newsletter useful, please forward and share it with a friend.

Upcoming API Conferences

 GraphQLConf 2025: Date: September 8th-10, 2025, Location: Amsterdam, Netherlands.

APIdays London: Theme: “No AI Without APIs” Conference Date: September 22nd - 24th, Location: Convene 155 Bishopsgate, London EC2M 3YD

Platform Summit 2025: Date: October 13-15, Location: Stockholm, Theme: Engineer Next-Gen API Architectures Register to get your tickets.

Kong API Summit Live 2025: Join developers, leaders, and visionaries from around the world as we explore the latest innovations around APIs, microservices, and AI. Date: Oct 14 - 15, 2025, Location: New York City

API Conference Berlin: Theme: The Conference for Web APIs, API Design & Management, Date: October 20 - 22, 2025. Register to get your tickets.

API World Conference 2025: Date: Sept 3-5 Location - Santa Clara, CA, Sept 10-12 - Live Online, Register to get your tickets

API Governance Consulting