Beyond Code Generation: API Context for Agentic Engineering

Official Schedule Context

Maintaining production systems involves a lot more than generating code. APIs are the interfaces

between systems and that surface gets out of control fast, as endpoints multiply and new consumers

come online. Once an API is in use, changing it becomes incredibly hard. We felt this acutely at

Postman. As our engineering organization scaled and we leaned more on AI agents for day-to-day work,

we kept hitting the same wall: agents that could write code struggled with what came next who's

calling this endpoint, what conventions does the rest of our API surface follow, what breaks if we

change this contract. The context wasn't in the code, so the agent didn't have it. So we built an

API context graph a continuously updated view of our entire internal API landscape and gave our

agents access to it. This talk is about what changed in our own engineering as a result: how API

design got faster and more consistent; how discovering and integrating with internal services

stopped being detective work; how change requests came with a blast-radius report before any code

shipped; how incidents got traced past the first stack trace, all the way down to root cause

No official session recording transcript was found by exact title match on the AI Engineer YouTube channel during this run.

Pending transcript synthesis when an official recording or confirmed matching video is available.