Skip to main content

Postman Adds AI Agent to Automate API Development and Governance

Postman added an artificial intelligence (AI) agent to its portfolio of tools and platforms for building and governing application programming interfaces (APIs) that can autonomously perform tasks ranging from development and documentation to exploration and setting up integrations with continuous integration/continuous deployment (CI/CD) environments.

Company CEO Abhinav Asthana said the Autonomous API Engineer significantly reduces the total cost of building and maintaining APIs by automating time-consuming tasks that have historically created bottlenecks in software engineering workflows.

In fact, the AI agent developed by Postman will make it significantly simpler to integrate API development and testing within those workflows, said Asthana.

Designed to be triggered from a pull request, Slack, Postman command line interface (CLI) or the Postman app, the Autonomous API Engineer spins up a secure, sandboxed environment. It then executes tasks and returns verified artifacts, including collections, test results, specs, run logs, pull requests, and a temporary cloud workspace—that teams can review and ship.

For example, the Autonomous API Engineer can run API and quality assurance (QA) tests on every pull request and then post results back into existing developer workflows. It can also investigate API issues and accelerate root cause analysis, tracing dependencies across services, actively testing APIs, and returning actionable hypotheses with reproduction steps.

The Autonomous API Engineer leverages an existing Postman Context Graph database that captures how an API was built, changed, and governed over time. The Autonomous API Engineer then uses that context to generate more reliable output than a general-purpose AI agent, said Asthana.

It’s not clear to what degree the building and management of APIs has been integrated into DevOps workflows, but in the age of AI it will be simpler to achieve that goal as the boundaries that exist between various tools and platforms become easier to bridge. In fact, in many cases the AI agent created by Postman will be communicating directly with AI agents created by providers of other DevOps platforms to complete a task, noted Asthana.

Each DevOps team will, of course, need to determine what types of tasks to assign to one AI agent over another, but it’s clear many tasks once performed manually by DevOps engineers will be performed by a small army of AI agents. The issue then becomes finding a way to put the right orchestration framework in place to manage all those AI agents.

In the meantime, DevOps teams should pay careful attention to how any given AI agent performs those tasks, said Asthana. In the absence of access to some type of method that provides context, an AI agent is likely to burn tokens needlessly investigating how to perform a task when that information is readily available in a graph, he added. At a time when organizations are becoming more concerned about the cost of AI, a graph is going to prove to be an essential element of an effort to rein in those costs, said Asthana.

Regardless of approach, the issue now isn’t so much whether to incorporate AI agents into DevOps workflows but rather to what degree to rely on them based on how they were actually constructed.



from DevOps.com https://ift.tt/sG8Xuvd
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

Documentation is Dead. Long Live Documentation.

I’m going to say something that will make every engineering manager uncomfortable: Stop asking your team to write documentation . Not because documentation doesn’t matter. It matters more than ever. But because asking humans to document their work after they’ve done it is a process that has failed consistently for thirty years, and no amount of “definition of done” checklists or documentation sprints is going to fix it. The people who know the most write the least. The docs that get written are stale within weeks. And the knowledge that matters most — the decisions, the gotchas, the “why” behind the code — rarely makes it into a document because it’s not the kind of thing you sit down and write. The Documentation Death Spiral I’ve watched this cycle play out on every team I’ve been part of: Week 1: “We need to document this.” Everyone agrees. Someone creates a Confluence space. Week 4: A few pages exist. They’re pretty good. Written by the one person who cares about docs. Week...
Post a Comment
Read more