Abhinav Asthana

I have been blown away by the response from customers and developers about the new Postman launch! The new Postman is AI-native and it is reflecting in adoption. We just crossed more than 3 million developers now using AI and Agent Mode in Postman. Not just in terms of usage, the rate of new customers buying our paid plans has grown by more than 500% since launch. More than 2/3rds of our new customer cohorts are using AI features in Postman and the rate is only growing. While we are excited about this, we are working on many exciting capabilities: 1️⃣ Long-running and autonomous modes for agents in Postman 2️⃣ Bringing the right context across thousands of APIs and services and millions of datapoints for the agent to access. 3️⃣ Execution sandboxes for agents to do their work securely. 4️⃣ Simulations to allow agents to know the outside world without touching real APIs. All of this is possible with the work we have done over the last few months with v12 and the new Postman. If you missed the announcement, you can read it here: blog.postman.com/new-postman-is…

We’re seeing teams evaluating alternatives to Stainless. Companies are looking for a solution that's dedicated to the API developer and agent experience for the long-term. @buildwithfern, by @getpostman, provides enterprise-grade SDKs and CLIs that are trusted by companies like Square, Auth0, and ElevenLabs. We’re helping teams migrate from Stainless to Fern, and our engineers are ready to support the transition end-to-end. If you’re exploring options, we’d love to help: buildwithfern.com/book-demo

Today we're introducing Postman Fabric Gateway—an AI-native agent gateway. Here's why it matters: agents will consume APIs at several orders of magnitude beyond traditional apps. Traditional API Gateways are not designed for AI agents. While many legacy vendors have tried to support agentic workloads, Postman customers have been asking us about something that is AI-native and doesn’t have the baggage of pre-AI architecture. Postman Fabric has been designed from the ground-up for agents with support for MCPs, CLIs, as well as APIs - both AI and deterministic APIs. We are building this with a modular architecture as we are still in the early innings of AI and there are many new patterns that are likely to emerge. One thing is certain though, agents are driven by APIs, and you can’t have agent-ready APIs without a purpose-built gateway. Through Postman Fabric, customers will be able to: 1️⃣ Have a single plane to manage all MCP servers - public or private 2️⃣ Expose internal APIs as MCP tools 3️⃣ Centralize SaaS credentials 4️⃣ Govern agent traffic and run policies at a consumer, route, or service level 5️⃣ Deploy on cloud or in a hybrid model We are opening up early access soon - let me know if you are interested in the comments or a DM!

@bhalligan Some of the use cases that you highlight are useful and eye opening. Things go to the next level when these agents start interacting with each other!

No matter what kind of company you are...start making your internal company data legible to AI. Today. As a founder, you are essentially building two versions of your company: the one humans work in and the digital twin that AI agents navigate to do the heavy lifting for you.

Doing exactly that at Postman and the results are extraordinary.

API Design for agents is a critical part of building autonomous systems. Most APIs are not ready for agents as well as people who have come to rely on these agents to be safe and trusted by default.

New blog: Building agents that reach production systems with MCP. When should agents use direct APIs vs CLIs vs MCP? Plus patterns for building MCP servers, context-efficient clients and pairing MCP with skills. claude.com/blog/building-…

No browser required. Our API is the UI. 🔓 Salesforce Headless 360 just exposed our entire platform — apps, workflows, metadata, Agentforce & Slack — as unified APIs, MCP tools & CLI. Build on any surface. Give Agentforce deep, trusted context. Stop just using Salesforce. Start building with it. 🚀 cio.com/article/415953…

Hype: Software written over the last two decades is going to be replaced by AI-solutions. Reality: AI software written over the last 3 years is most likely to be replaced due to easy cost of switching between LLMs, lack of business context, and lack of workflow and system integration. As we are building and deploying our own agents, I find most existing AI software to be quite crappy. It is far easier to modify the skillset of an agent that I have created to know my entire business versus telling a vendor to acquire my business context. Most solutions are still buyer-centric. Support agents are selling to people managing support. Sales agents are selling to the CRO. Nobody is building a true business agent that a CEO actually needs. That’s why AI solutions are failing to deliver value. Opportunity for systems of record to step up and provide real AI solutions and open up APIs. Every company is building agents and if you don’t have APIs, you will be replaced by someone else.

People using RLS need to pick up a book on APIs.

RLS was a mistake and folks exposing that level of complexity to less technical users is asking for trouble. It was a mistake in Firebase. It’s a mistake in Supabase. It will be a mistake in the next product too. I personally - even knowing how to secure it - would never touch it. It’s the worst security footgun you can imagine. One small mistake and your data is available to the world.

We want to thank all the early adopters who’ve given us a ton of feedback. We shipped a number of improvements and capabilities in the last couple of weeks: - New Agent Blueprint Experience - GitHub Auto-Build - Variable/Secret Store - Live Log Streaming astropods.com

AI-native === API-first

Welcome Salesforce Headless 360: No Browser Required! Our API is the UI. Entire Salesforce & Agentforce & Slack platforms are now exposed as APIs, MCP, & CLI. All AI agents can access data, workflows, and tasks directly in Slack, Voice, or anywhere else with Salesforce Headless 360. Faster builds, agentic everything. 🚀 #Salesforce #Agentforce #AI venturebeat.com/ai/salesforce-…

Today, we are excited to announce our $150M Series C led by Khosla Ventures with strong participation from Sequoia Capital, Blackstone, Insight Partners, Evantic Capital, Abstract Ventures, 20VC, NEA, and Mantis VC. This puts our valuation at $1.5B and will accelerate our investment in research, product, and global go-to-market. Long live developers.

CLIs have emerged as one of the most popular ways for coding agents to work with APIs. The reason is simple, CLIs were designing for human input and LLMs are good at generating text for humans. However, if you are still stuck designing your CLI though, no need to wait more. We just introduced the capability to generate a CLI for your API right within Postman. You can now go from Spec or a Postman Collection to CLI in a few seconds. Check out the demo video! Docs: learning.postman.com/docs/cli-gener…

Creation (and evolution) of new AI agents has become so fast now that we already have 5-10 agents per employee at @getpostman and I expect it’ll probably 10X from here. Not only are these agents proliferating, they are also hyper-customized for our use cases. Building them is like hiring interns, and with every week, they are getting more intelligent. Some of these agents are present in @SlackHQ. Some of them are skills with @claudeai. Some of them write summaries and thoughts in @NotionHQ databases. Some of them have their own UIs even! All of these plug into our existing systems of record through APIs managed on @getpostman and we are running them on @astropods_. (Humans are still needed to verify ground truth in systems we have to ensure that agents stay connected to the real world) Thanks to this we have unprecedented visibility across product, engineering, marketing, sales, and other functions. We have dedicated teams now focused on making every aspect of our business and operations AI-native. I’ll be sharing and open-sourcing many of these in the coming weeks. Stay tuned!

The founder of Postman says you have to kill your existing org chart, especially if you're still operating with a pre ai hierarchy arrangement. The modern org chart, according to @a85: - wide span of control (even within exec team) - work directly with ICs, not through layers - either you're building, or you're selling Projects are led by staff/principal engineers with high agency. They see across the board as well as deep in the stack. Product managers are building APIs and prototyping in Claude instead of writing PRDs. Designers are shipping PRs through Cursor directly instead of relying solely on Figma. Everyone is building. And the management's job is to develop better judgment.

Excited to announce Postman’s @getpostman collaboration with @AnthropicAI! @claudeai is now the default model in Agent Mode with full context of your workspace, collections, environments, and code. It runs on @awscloud Bedrock for enterprise security and compliance. We also brought Postman into Claude: 1. Claude Code plugin: find APIs, generate code, run tests, sync collections 2. MCP connector + Skill: live Postman API context into Claude.ai Postman is where APIs are built. Now it's where AI-native development happens too. Check out the deep dive here: blog.postman.com/announcing-the… and read the story on Claude's website: claude.com/customers/post…

🌉 🌉 We had an incredible time at our March 26th Agents & APIs SF Developer Meetup with @ToolhouseAI, @render (@ojusave!), Attian (@ParitoshKulk!), and Postman (@uditvasu!) presenting! Join us on April 30th when @bwarrn of @mesa_dot_dev and @BenBackus4 of @greptile demo what they're working on! More details and sign up here! 👉luma.com/agents-AI-apis…