Kong's Move to API Commerce

This points to Kong trying to move from infrastructure vendor to transaction layer. The important shift is that Kong already sits in the path where APIs are authenticated, rate limited, observed, and now metered, so a marketplace is not just a catalog of tools. It can become the place where an agent discovers an API, gets permission to use it, pays for usage, and runs the call without the customer wiring each vendor separately.

• Kong has tried the marketplace model before. The earlier version relied on long tail third party APIs, weak reliability, and separate API key setup on provider sites. The current version starts from operating the gateway itself, which gives Kong direct control over provisioning, policy enforcement, and traffic visibility across millions of APIs.
  1 sacra 2 sacra
• The billing piece matters because agent commerce breaks if every tool has its own contract and checkout flow. Kong added usage metering and billing through its September 3, 2025 OpenMeter acquisition, which lets the same control plane track token use or API calls, apply pricing, and cut off or throttle usage when limits are hit.
  1 sacra 3 konghq 5 konghq
• The closest public analog is OpenRouter, but the business is different. OpenRouter aggregates model access behind one endpoint and charges platform fees on top of provider relationships, while Kong is aiming at enterprise controlled supply behind the firewall, where the value is governance, internal chargeback, and eventually a trusted directory for agents to buy from approved services.
  1 sacra 4 openrouter 6 openrouter

If this works, the next layer in API management becomes commerce and discovery for machine users. The winners will be the platforms that already control identity, policy, and payment at the traffic layer, because agents will need one trusted place to find tools, get access, and spend against a shared wallet instead of stitching together dozens of vendor relationships.