Devdutt (@devdutt) header
Devdutt (@devdutt) profile picture

evolving

Manhattan, NY
Joined April 2008
Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)Photo by Devdutt (@devdutt)
Built from years of helping modernize APIs in the largest enterprises. A new stack for agents has emerged. The Agent Cloud.
At Kong we run half a quadrillion AI tokens a year, and I kept seeing agents stuck on clouds built for websites. So we built a cloud for agents. Volcano is live today: the self-healing agent cloud. Sandboxes, durable workflows, Postgres, hosting.
1
5
1
21
60,598
At Kong we run half a quadrillion AI tokens a year, and I kept seeing agents stuck on clouds built for websites. So we built a cloud for agents. Volcano is live today: the self-healing agent cloud. Sandboxes, durable workflows, Postgres, hosting.
163
150
144
1,571
2,740,689
146x YoY!!! 💥
For what we can see (which is a smaller subset) Kong AI Gateway is growing 146X yoy entering into the Quadrillions league soon.
175
Replying to @jsensarma
Is Starlink legal in China? He thinks he can dunk on India..
681
Still Day 1 for the Agentic Enterprise... and @kong AI Gateway.
1
10
281
Devdutt retweeted
If you are building or using agents, you are likely dealing with credential sprawl. With Passport, not only did we fix credential sprawl and eliminated risk, we also found out who is using which API across humans, machines, and agents. Read on to find out what we encountered at Postman and how we solved: 1. Building an inventory of secret sprawl 2. Identify human and agentic access 3. Control and enforcement through agentic workflows blog.postman.com/credential-…
5
12
763
this is @kong nuts!
1
1
3
347
Devdutt retweeted
.@getpostman is now natively available in your favorite coding agent! The new Postman CLI is designed to bring API engineering for agents: 1️⃣ Works in Git and your code repo - Just drop Postman where your agent lives and works. 2️⃣ No GUI - Work in your coding agent. Bring up the Postman UI for review and approval. 3️⃣ No sign-up - Get started right away. Sign-up when you have to save your work and want more. Install once, work in your agent. Run npm install -g postman-cli, then postman init. This loads Postman's skills into your coding agent so it can create collections, write tests, and much more. Available as a plugin for all coding agents! The skills cover the API lifecycle: find APIs your org already has, generate tests that catch regressions, mock an API before it exists, watch live endpoints for downtime and drift, run checks in CI on every commit, and run performance tests. You can also extend the abilities of your agent with the Context Graph. An agent often sees only the code that is accessible to them. The Context Graph API gives it a map of your team's infrastructure, APIs, and services, and how they depend on each other. As your agent works, you stay the reviewer. Your agent does the work from the command line. Open Postman when you want to review or approve it. Check out more at postman.com!
3
25
4
62
494,439
Agentic Infrastructure like no other.
I have been a little quiet on here recently because I was heads down working on a new product that I consider the most exciting product I have ever released. And today at Kong AI Summit we finally announced it. Introducing 🌋 Volcano. It provides the AI stack for building AI agents at scale: - Native Claude Code, Codex and Cursor plugins - Durable workflows + durable tracing - Branchable Postgres database + file storage - Unlimited user authentication + realtime capabilities - Distributed locking to coordinate agentic work across crews - Full blown Next.js hosting behind our CDN across multiple regions - Distributed backend hosting for APIs and MCP tools - Sandboxes GA in a month - Javascript, Typescript, Python and Ruby support You can use Volcano standalone, and you can also use it in combination with our Kong Konnect platform to govern, secure and discover AI agents (and APIs, MCP tools, and LLMs) at scale. You can get started for free at volcano.dev - I will be posting a lot about Volcano in the coming weeks as I am 100% obsessed by this product (..and I hope you will too).
1
1
664
#1! Thank you all. 🦍
2
2
13
824
I have been a little quiet on here recently because I was heads down working on a new product that I consider the most exciting product I have ever released. And today at Kong AI Summit we finally announced it. Introducing 🌋 Volcano. It provides the AI stack for building AI agents at scale: - Native Claude Code, Codex and Cursor plugins - Durable workflows + durable tracing - Branchable Postgres database + file storage - Unlimited user authentication + realtime capabilities - Distributed locking to coordinate agentic work across crews - Full blown Next.js hosting behind our CDN across multiple regions - Distributed backend hosting for APIs and MCP tools - Sandboxes GA in a month - Javascript, Typescript, Python and Ruby support You can use Volcano standalone, and you can also use it in combination with our Kong Konnect platform to govern, secure and discover AI agents (and APIs, MCP tools, and LLMs) at scale. You can get started for free at volcano.dev - I will be posting a lot about Volcano in the coming weeks as I am 100% obsessed by this product (..and I hope you will too).
5
8
2
34
4,018
Replying to @bhalligan
1-1 🤞🏽
1
38
A Hero That Trusted His Intuition. The problem wasn’t that Morgan Stanley didn’t believe him. Rick Rescorla had already been right once. After the 1993 basement bombing of the World Trade Center, the firm’s security chief walked the towers, studied the site, and reached a conclusion most people preferred not to hear: the World Trade Center was still a target. Next time, he said, it would not be a truck. It would be an airplane. An airplane. In a 1993 report. Executives listened. Then they looked at the lease. Morgan Stanley was the largest tenant in the complex—twenty-two floors of the South Tower, thousands of brokers, and a trading infrastructure that could not be packed into boxes and wheeled across the Hudson. They literally made it a trading center. The contract with the Port Authority ran until 2006. Walking away from premium Manhattan space of that scale would have meant penalties measured in the hundreds of millions, plus the operational chaos of relocating an entire downtown machine. So the company stayed. Rescorla adjusted. If they could not leave the building, they would learn to escape it. He built a protocol and treated it like doctrine. Unannounced drills. No exemptions. Brokers who billed by the minute were pulled off their desks and sent into the stairwells two by two, starting from the top floors, leaving a lane for firefighters coming the other way. People complained. He did not care. Practice, he believed, was the only thing that would beat panic. On the morning of September 11, 2001, American Airlines Flight 11 hit the North Tower. From the 44th floor of the South Tower, Rescorla could see the fire. Then the Port Authority came over the speakers: the South Tower was secure. Stay at your desks. Rescorla grabbed a bullhorn and ignored them. He started the drill his people already knew by heart. Floor by floor, two by two, down the stairs. He sang as he moved—Cornish songs from childhood, then “God Bless America”—keeping the line moving, refusing to let the stairwell become a stampede. Seventeen minutes later, the second plane struck the South Tower. By then, most of Morgan Stanley was already on the way out. Of the 2,687 employees in the building that morning, all but 13 survived. It was stunning. Rescorla could have been outside with them. He went back up instead. Colleagues told him to leave. He said he would, as soon as he was sure no one was left behind. He was last seen around the 10th floor, heading higher. The South Tower fell at 9:59 a.m. They never found him. He was one of the 13. He was a hero in every sense of the word. Remember Rick Rescorla, he remembered for us.
1,079
13,319
834
60,640
2,603,397
Replying to @sonicaghi
Zoom zoom!
1
54
I wrote about the "New Dawn" in enterprise software. It looks a lot like the cloud and API sprawl era we saw a decade ago, where adoption comes first and governance is an afterthought. But this time with AI workloads it's more dangerous and expensive. Some numbers from our platform that tell you what's really going on in the enterprise world: ▪️ Enterprise AI traffic as a share of total Kong platform traffic is up 7x in nine months. We're processing trillions of tokens, heading into quadrillions. ▪️ The model market is not settled. Claude held 56% of attributed request volume through Kong in June. By July, that dropped to 49.9%, with GPT climbing to 46.4%. Model share can flip in a single month. ▪️ 62% of orgs on Kong AI Gateway run 2+ models in production. 20% run six or more. One org is running 602 distinct model identifiers. ▪️ 97.8% of AI requests are going to third-party proprietary APIs — every prompt, every piece of context, leaving the company's perimeter. ▪️ Less than 1% of orgs running AI through Kong have any AI-specific governance in place. No prompt guards. No request or response controls. No route-level policy. Full breakdown, including the industry-by-industry model data: konghq.com/blog/enterprise/e…
1
7
365
Devdutt retweeted
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
54
357,162
Devdutt retweeted
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
1
13
1,054
And the gorilla has landed! @kong has been unleashing OSS software since day one and in the age of AI no better direction than open-weights. Especially for a 800 pounds gorilla. Now signatory: microsoft.com/en-us/corporat…
1
2
8
385