CEO and Founder, Postman (Postman.ai)

San Francisco, CA
Pinned Tweet
Excited to introduce Orbit - a new API specifically built for coding agents to discover, evaluate, and integrate public APIs. Orbit has two simple tools: search and integrate. All your agent needs to do is describe the task, and Orbit will generate a task brief to integrate the API. Best of all: it is completely free! No auth, no set up. Just add it to @claudeai, @cursor_ai, @opencode @devindesktop or any other coding agent. Check it out here: buildwithorbit.ai/welcome
11
13
96
481,781
Abhinav Asthana retweeted
Super pumped that @getpostman runs thier context graph ingestion in Daytona. Amazing to work together @a85 !
I am excited to announce the launch of the Postman Context Graph API! The Context Graph API lets an agent see your API ecosystem as a connected system. You do not need to replace your model, agent, or IDE. You give the tools you already use access to the graph, and they can reason across services, APIs, deployments, runtime calls, and external systems that were previously invisible to them.
2
22
3,028
I am excited to announce the launch of the Postman Context Graph API! The Context Graph API lets an agent see your API ecosystem as a connected system. You do not need to replace your model, agent, or IDE. You give the tools you already use access to the graph, and they can reason across services, APIs, deployments, runtime calls, and external systems that were previously invisible to them.
6
6
33
54,856
The model also did less work to get there. Across the benchmark, Opus cost 27% less with the Context Graph and Astra cost 20% less. On the HTTP-endpoint question, Opus went from $37 per run to $10, used about a quarter of the input tokens, and made half as many tool calls. Once the graph pointed it in the right direction, it did not need to burn time and tokens rediscovering the ecosystem one search at a time.
1
2
106
Checkout the Context Graph API here along with instructions to integrate your agents: postman.com/context-graph/
1
1
116
Abhinav Asthana retweeted
We have to build AI that murders us, because if we don’t, China will build it first, and I don’t want to get murdered by a computer that speaks Chinese. That would be ridiculous.
606
6,881
66,203
1,428,631
Abhinav Asthana retweeted
This is peak comedy I think we should put Ads on it asap. I think we are going to encourage our models to bite. Defend yourself
19
25
642
74,747
Works out of the box with @getpostman!
That's a small reminder! 👇 As of June 2026, HTTP has a new method - a GET with a `body` 😎 Meet QUERY (RFC 10008). It lets you send complex queries in the body (like POST) while staying safe, idempotent, and cacheable (like GET). Already works on servers (Node.js, Go, Laravel…). Browsers are still adding full support, usable now with care, with widespread adoption coming later in 2026+.
1
3
9
1,242
Abhinav Asthana retweeted
If you’re not reading the code, whether explicitly or through agentic inquiry, one or more of these is true: ○ You’re a beginner ○ Software is throwaway ○ You’re prototyping ○ You have no users / revenue ○ You’re taking on debt & risk ○ Your problems are basic And btw. All of this is fine. But the reality is that models are still not at the “full autonomy” stage yet. They make rookie mistakes, they go down bad architectural paths. I just had the best model in the world add a nonsensical 700ms delay to “settle” something and it told me “you’re right, I was cargo-culting” 🤨 I am on the camp that this need will diminish more and more. Most code is indeed going to be assembly-like. But we also have the global internet and software infrastructure riding on these models and narrative, and we have to respect that.
575
769
8,360
1,326,467
Agents do real world actions through APIs. Vibe coding APIs is not an option.
A man in Australia asked his agent (Claude running on OpenClaw) to book him a spot in a popular gym class. The agent found a software vulnerability that let it book the class weeks further ahead than should have been possible. When the user then asked if it could move him up the waitlist, the agent discovered the API had no authorisation checks on cancelling other people’s reservations, so it cancelled the person in the first spot and moved him up the list. Some people will call this misalignment, but his agent was perfectly aligned to him - it was only trying to help its user get what he wanted. The most important thing about this story, in my opinion, is that it gives you a window into what is about to start happening on a massive scale once millions of people have an agent trying to get their beloved users the best seats, bookings, appointments or reservations through absolutely any means necessary.
6
1,528
Abhinav Asthana retweeted
Me: *enter any prompt* Opus:
42
153
3,898
119,167
Postman Passport is entering early access today, and we're shipping a free CLI you can install right now to see which of your secrets your agents are already exposed to. Your agents are holding your API keys right now. Those keys live in .env files and bash profiles, and they get copy-pasted into Slack, Docs, and wherever else is convenient. Now that agents call APIs directly, they're reaching into all of it. A single dev machine can hold dozens of secrets, and most people have no idea which ones are exposed. So: do you know which secrets your agents hold? The free Passport CLI answers that. It runs a local proxy on your machine and routes your outbound requests through it, so it can inspect the traffic from your AI agents, scripts, and CLI tools and flag any API keys, tokens, and other credentials being transmitted. Everything stays on your machine. It never stores or sends your secrets anywhere, and it redacts anything it detects in its reports. Install it here: npmjs.com/package/@postman/p… Once you see what's exposed, Postman Passport is how you fix it: a secure way for humans, machines, and agents to call APIs without handling raw keys. Run the CLI, and if you want into the EA program, let me know.
3
8
55
357,096
Abhinav Asthana retweeted
Met a team who basically opens, updates and closes 100% of their Jira issues from Codex or Claude Code. The sessions cost ~$0.10 each. Or dollars / week / eng Which means they paying more to the labs each month to never have to open Jira, than they pay Atlassian for Jira
28
15
398
177,984
We benchmarked the latest Kimi-K3 and the Fable 5 models on the APIFlow-Bench and the results were surprising (or maybe not depending on where you stand!) Kimi K3 tied for #1 with GPT 5.5 in the benchmark. Not just that, most latest open-weight models are at par with frontier models and in many cases better. Fable 5 though is the worst performing model in this benchmark, refusing to do most actions designed in the benchmark. Fable's underperformance is probably due to the safety guardrails instituted on the core model (Mythos). Check out the updated leaderboard: postman.com/ai/apiflow-leade…
2
5
13
1,023
@Kimi_Moonshot Thought you'd like to see this.
226
API programs are undergoing one of their biggest changes they've ever faced: a completely new class of users. For decades, that user was a developer who read your docs, signed up, and emailed support when something was unclear. Today, agents can do that work. An agent can read your spec, wires up the integration, and ships, often without anyone visiting your site. And when it gets stuck, it doesn't open a ticket. It quietly moves to a competitor it can use, and you never find out. Most companies are already deploying AI agents, but only a quarter have designed their APIs for them. The teams that close that gap first are the ones that will pull ahead. So we built AI-Ready APIs, a free assessment that scores how ready your public API surface is for the agents already integrating it. Point it at your domain and get a graded, evidence-backed report of exactly where an agent gets stuck. All built from our team's years of experience embedded with some of the largest API programs in the world mobilizing towards agent readiness. Want to fix your agent experience? Postman's API Governance solutions keeps every API spec agent-ready, enforcing standards both at design time and in CI. Postman Workspaces become a curated context layer for partners (and their agents) to discover, execute, and integrate your APIs. Fern's platform help you transform your API specs into agent-ready docs, SDKs, and CLIs. Start optimizing your product for agents today. Links in the thread...
2
13
34
268,647