---
title: "Beyond Code Generation: API Context for Agentic Engineering"
category: "talks"
date: "2026-06-30"
time: "2:25pm-2:45pm"
track: "Expo Stage 2 NW"
room: "Expo Stage 2 NW"
speakers: ["Kamalakannan Nandagopal"]
sourceLabels: ["Official conference schedule", "Public YouTube metadata"]
scheduleTrack: ""
scheduleRoom: "Expo Stage 2 NW"
scheduleLabels: ["Expo Stage 2 NW", "session", "confirmed"]
---
# Beyond Code Generation: API Context for Agentic Engineering

## Conference Context
- Date/time: 2026-06-30 · 2:25pm-2:45pm
- Track/room: track TBD · Expo Stage 2 NW
- Speaker(s): Kamalakannan Nandagopal
- Session type/status: session · confirmed

- Track: track TBD
- Room: Expo Stage 2 NW
- Session type: session
- Status: confirmed

## Session Description
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

## Media Evidence
No related AI Engineer channel video found yet.

## Evidence Graph
This evidence graph is generated from currently linked source material: official schedule text, related video pages, cached transcripts, visible slide text, dense/reconstructed slide pages, and AI slide-classification audits.

### Media Signals
No linked video, transcript, or slide source has been attached yet.

### Agent Reading Notes
Use these signals to refine the synopsis, topic links, people/company context, and method notes. If a source is a related external video rather than an exact official recording, keep it framed as supporting evidence.

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

## People
- [[kamalakannan-nandagopal]]

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

## Synthesis
### Synthesized Breakdown
# Beyond Code Generation: API Context for Agentic Engineering ## Conference Context - Date/time: 2026-06-30 · 2:25pm-2:45pm - Track/room: track TBD · Expo Stage 2 NW - Speaker(s): Kamalakannan Nandagopal - Session type/status: session · confirmed - Track: track TBD - Room: Expo Stage 2 NW - Session type: session - Status: confirmed ## Session Description 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.

### Speaker And Company Context
- [[kamalakannan-nandagopal|Kamalakannan Nandagopal]] — Staff Software Engineer at [[postman|Postman]].

### Topics Covered
- [[agent-security]]
- [[agentic-search]]
- [[coding-agents]]

### Derived Links And Source Material

### Novel Concepts / Clever Methods
- No highlighted novel concept has been detected yet.

### Evidence Boundary
This synthesis is based on the official schedule and linked source pages. It should be revisited when exact session recordings or transcript-backed secondary sources are available.