Hi, I’m Abhinav, one of the founders and CEO of Postman. We’ve just launched a suite of tools to simplify working with APIs and LLMs in agent workflows, leveraging our network of 100K APIs to enhance and scale agent capabilities.
Hey Abhinav, DX is such a critical component to a successful API, and historically "developer" has meant "human." As agents become important consumers of APIs, what are your thoughts on how DX evolves? Is "agent experience" or "machine experience" different than developer experience?
Hello... I work on the Flows product at Postman. Love this question.
I believe wholly that the definition of a developer is rapidly changing (arguably has already changed). It's clear that it won't mean people who are "classically" trained in software development. I particularly like the view point that we're evolving from developers to conductors (SpecStory did a nice write up on this [1]) where we are more focused on orchestrating Agents.
I also think that APIs will either need to be ready for AI (trusted, solve for authentication, have clear specification, lots of examples) or will be AI dependent to fix them up and put a new layer on top. Discovering the right API to solve the problem is central to the dynamic logic agents introduce to workflows.
I've been building agents for both personal use and for automating internal processes within my team/across the company, and the DX has not felt all the foreign from typical development... an idea, a quick prototype, a tight inner loop for rapid feedback, then a graduation to a deployed asset. While not foreign, doesn't mean there isn't plenty of room for innovation. The DX is where we're really focused today, particularly with Flows.
Hi, I’m Abhinav, one of the founders and CEO of Postman. We’ve just launched a suite of tools to simplify working with APIs and LLMs in agent workflows, leveraging our network of 100K APIs to enhance and scale agent capabilities.
Here’s a workspace (https://www.postman.com/ai-on-postman/postman-ai-agent-build...) if you’d like to explore more - would love to get feedback and thoughts from this community as we continue to build.
Hey Abhinav, DX is such a critical component to a successful API, and historically "developer" has meant "human." As agents become important consumers of APIs, what are your thoughts on how DX evolves? Is "agent experience" or "machine experience" different than developer experience?
Hello... I work on the Flows product at Postman. Love this question.
I believe wholly that the definition of a developer is rapidly changing (arguably has already changed). It's clear that it won't mean people who are "classically" trained in software development. I particularly like the view point that we're evolving from developers to conductors (SpecStory did a nice write up on this [1]) where we are more focused on orchestrating Agents.
I also think that APIs will either need to be ready for AI (trusted, solve for authentication, have clear specification, lots of examples) or will be AI dependent to fix them up and put a new layer on top. Discovering the right API to solve the problem is central to the dynamic logic agents introduce to workflows.
I've been building agents for both personal use and for automating internal processes within my team/across the company, and the DX has not felt all the foreign from typical development... an idea, a quick prototype, a tight inner loop for rapid feedback, then a graduation to a deployed asset. While not foreign, doesn't mean there isn't plenty of room for innovation. The DX is where we're really focused today, particularly with Flows.
[1] https://newsletter.specstory.com/p/getting-started-with-soft...
yea, this is gonna be pretty interesting to watch play out. DX tools moving to a hybrid approach...
Seems cool, what is the top use case?