Internal developer platforms have become a tangled web of orchestration tools, CI runners and deployment systems that rarely speak the same language. Every new integration adds another translation layer, and as AI-driven automation starts to plug into those pipelines, the lack of a shared vocabulary for what is actually happening across the software delivery lifecycle becomes a real bottleneck. Without a consistent way to describe build, test and deploy events, both humans and agents are left stitching together logs and webhooks from systems that were never designed to interoperate. Dadisi Sanyika of the Continuous Delivery Foundation sat down with Mike Vizard to walk through how CDEvents is tackling that fragmentation. CDEvents defines a common event specification — essentially a standardized set of receipts that tools like Jenkins, Tekton and other delivery systems can emit as work moves through the pipeline. That shared semantic layer gives platform teams a reliable way to wire h...
Imagine handing the same master key to every contractor who works on your building. No names, no records, no way to know who came and went. If the key gets copied, passed around or lost, you’d have no idea. You’d only find out something went wrong after the damage had been done. That’s essentially what API keys do for your AI agents , and for prototypes, that’s fine. However, the moment your agent moves into production, accessing real data, taking real actions and operating inside real systems, that master key becomes a liability you can’t afford. The Risks and Benefits of API Keys Developers are under a huge amount of pressure to build faster. Every organization wants to benefit from agentic AI, and devs play an integral role in making that happen. Given this, it’s easy to see the appeal of API keys: They’re simple to use and can get you to a proof of concept almost instantly. The problem is that they’re severely lacking from a security standpoint. API keys work by ...