Postman is launching one of the most significant updates to our product - the AI Engineer.

You can run it on command through Postman, in Slack, via the API, and soon through the CLI. Wherever your team already works, the AI Engineer will be available.

The Redpoint InfraRed 100 is now live. These are the companies building the infrastructure that powers everything happening in AI right now, from world models and agent runtimes to the sandboxes, databases, and security tools agents depend on. Congratulations to this year's honorees! Read the full 2026 InfraRed Report: our state of the union on AI and cloud infrastructure 👉 redpoint.com/reports/the-inf…

Honored to see @getpostman recognized in @Redpoint's 2026 InfraRed 100. As software goes AI-native, APIs matter more than ever. Proud of our team building the infrastructure layer powering modern AI. Congrats to all featured. redpoint.com/infrared/report…

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!

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-age…

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/4159536/sale…

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/salesforc…