Original Summary

I’ve been building this since late June and I’m almost ready to release it. Before I do, I want a reality check from people actually building agents. The idea is basically a control layer between AI agents and APIs/tools. You can connect/import your own APIs, expose selected endpoints as tools, and the gateway handles things around them like credentials/OAuth, tool permissions, policies/approvals, rate limits, and execution logs. Basically: AI agent ↓ control gateway ↓ permissions / credentials / policies ↓ your APIs & custom tools I know a good dev can just build an MCP server/connector themselves, which is exactly why I’m asking: Is there genuinely a need for a simple way to connect custom tools to AI + control how agents use them, or am I spending months solving something developers would rather build themselves? Second question: what if developers could also build and combine custom tools on top of this layer , not just import APIs? For example: a controlled connector that lets an AI work with your codebase; knowledge-graph tool + processing tool → a new tool that gives the AI compact context and saves tokens; community-built tool packs that others can install and connect to their agents. Would you actually build/use tools like this? If yes, what would the platform need to provide so you wouldn't just build and host the whole thing yourself? SDK? Hosted execution? Credentials? Sandboxing? Permissions? Marketplace/distribution? Composing tools? Something else? I’m almost done and will release it soon. If you actually have this problem, would you be interested in trying the early version and tearing it apart? No need to be nice — negative feedback is useful too.   submitted by   /u/Decent_Progress7631 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/13 16:33:37