We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman

Coding agents are great inside one repo. Postman has 115 microservices and thousands of endpoints. Kamalakannan Nandagopal, staff engineer at Postman, shares how Postman made coding agents work across a real distributed system. Docs go stale, skills and MCPs are only as good as their context, and agent memory stays stuck with one person. Borrowing from Postman's go-to-market team, they realized APIs are the context layer, and built an API context graph that maps every service, endpoint, implementation and call, all the way down to databases, with every data point grounded in code or production telemetry. He shares evals built from real PRs and design decisions: big wins on API discovery, redesign and impact assessment, an honest failure when the graph went stale, the finding that 75% of PRs touched APIs, and a 21-page architecture review the agent produced on its own. In this talk: • Why coding agents struggle with distributed systems and microservices • Building an API context graph grounded in code and telemetry • Eval results on API discovery, redesign and impact assessment • Why keeping the graph fresh matters as much as building it SPEAKER Kamalakannan Nandagopal, Staff Engineer, Postman LinkedIn: https://www.linkedin.com/in/kamalakannan-nandagopal-3650818a/ LINKS Postman Context Graph API: https://blog.postman.com/introducing-the-context-graph-api-one-map-of-your-api-ecosystem/ Context Graph docs: https://learning.postman.com/docs/use/context-graph/get-started Postman: https://www.postman.com Postman on X: https://x.com/getpostman CHAPTERS 0:00 Intro 0:32 115 microservices 1:02 From autocomplete to autonomous agents 1:42 Real systems are distributed 2:12 Docs go stale 2:36 Skills, MCPs and agent memory 3:21 What the go-to-market team learned 4:01 APIs are the context layer 4:36 Building the API context graph 5:36 Grounded in code and telemetry 5:56 What the graph revealed 6:25 Evals from real PRs 7:35 Reading the results 8:20 Use case: API discovery 9:05 Use case: API redesign 11:54 Use case: impact assessment 12:29 A failure: stale data 13:38 75% of PRs touch APIs 14:28 A 21-page architecture review 15:03 What's next 15:38 Takeaways Recorded at the AI Engineer World's Fair 2026 in San Francisco. Subscribe for more talks from the engineers building with AI. AI Engineer: https://ai.engineer YouTube: https://www.youtube.com/@aiDotEngineer X: https://x.com/aiDotEngineer LinkedIn: https://www.linkedin.com/company/aidotengineer/ #CodingAgents #APIs #AIEngineer