正在加载视频...

视频加载失败

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...

18,213 次观看 • 5 个月前 •via X (Twitter)

9 条评论

Vineet Gupta 的头像
Vineet Gupta5 个月前

We are kind of looking to roll out own own AI gateway, but would definitely be interested if we don't have to reinvent the wheel.

neil harrington 的头像
neil harrington5 个月前

ooooh! yes please!

Ronak Dinesh 的头像
Ronak Dinesh5 个月前

Interested

Yaser Hameed 的头像
Yaser Hameed5 个月前

Yes !!

Ashish Garg 的头像
Ashish Garg5 个月前

Definitely interested!

Pushkar Jain 的头像
Pushkar Jain5 个月前

Would love to try this out at @knowyourcompani We are pushing towards a MCP for our internal apis, this looks promising

Giovanni Toschi 的头像
Giovanni Toschi5 个月前

Interested

Gaurav Gupta 的头像
Gaurav Gupta5 个月前

this looks so interesting. i was thinking that we needed an api gateway that’s agents first, because agents call more api than i would. would love testing this out!

Shrawan Saproo 的头像
Shrawan Saproo4 个月前

It's Interesting to see the API network in sync with the Agent Infrastructure, I would love to try it out, as an early adopter!

相关视频

Today I'm excited to share Sigilum! This is Payman's solution for Auditable Identity for AI Agents. (think One Password-ish but for AI Agents) I recorded a quick walkthrough showing how it all works (video below). This answers three pains we've seen within Financial Services (Banking) AI Agents we've built and OpenClaw🦞 AI Agents we deploy. Security, Auditability, and Control. 1. Security Making sure keys are secure and not just freely given to an AI Agent is a big deal. When working with money, you can't just expose these or skip putting controls in place. Sigilum provides a local gateway that prevents access to keys by the AI Agent without explicit authorization from a person. We provide namespaces through the service so you always know who authorized what key, for what service, to which agent. 2. Auditability If I could hit on the importance of this 100 times I would. It comes up in every financial services conversation. Sigilum provides you with the answer to "Who authorized this AI Agent to act on my behalf?" Audit logs trace back to the person, the service, and the AI Agent. With more audit logs being built through our managed service, this will be the key source for determining how an AI Agent is behaving on your behalf. This is needed for agents from OpenClaw, and especially for banking/money movement. 3. Control Revoke keys, limit access, grant authorization. All seemingly simple things, but complex to implement and make elegant. These controls dictate what the AI Agent can or cannot do. Sigilum allows you to do all of this through the managed Dashboard. We've made Sigilum open source and encourage others to contribute and keep building on the gateway. It's been a source of a lot of visibility and productization of AI Agents for us. We'll keep contributing and adding to it. Link in comments. If you want to try it out, we do have a managed service that makes it easy to spin up. Go to to sign up. Note: even though we've been pushing 100+ commits a day to get this out to folks, there are still some noticeable areas for improvement we're working on, which should get resolved soon (by us or you!): - Deeper audit trails - More providers (currently supports all OpenClaw providers) - Deeper scanning of existing keys your agent is hiding from you (we'll find them) - OpenClaw gateway persistence - Auto-purging keys - And more... If you want to contribute or have feedback, please DM or go to the GH. Happy building!

tyllen

18,497 次观看 • 8 个月前