Treg wants to be OpenRouter for tools, and the unlock is that your agent holds no keys
superdesigndev/treg is trending at 197 stars today, and the pitch is one line: OpenRouter, but for agent tools. One proxy in front of 3,000-plus endpoints across 60-plus providers, with authentication injected server-side.
The problem it points at is real and mostly unspoken. The tools that do actual professional work sit behind subscriptions and signup walls β Semrush at $139 a month, Moz at $99, and a long tail of partner-only APIs your agent will never get near. Treg carries those accounts itself and bills fractions of a cent per call. If your agent needs a keyword volume lookup twice a week, you were never going to buy the seat.
The architectural claim is the part worth chewing on: the proxy relays, it never models the upstream, and it injects auth server-side, so callers never hold keys and the integration survives upstream API changes. Both halves of that are load-bearing. Every MCP server that wraps and re-shapes an upstream API breaks the week the upstream ships v3. And every credential you hand an agent is a credential that can walk out through a conversation β see this week's Muse filesystem export for what that looks like in practice.
Alongside the catalog you can register your own APIs, OAuth connections, vendor CLIs and skills under your org's credentials, which is what makes it a registry rather than a reseller. License is Apache 2.0 with a carve-out: self-host freely, but reselling it as a competing hosted service needs written permission. Using the hosted treg.to inside your product is fine.
https://github.com/superdesigndev/treg
← Back to all articles
The problem it points at is real and mostly unspoken. The tools that do actual professional work sit behind subscriptions and signup walls β Semrush at $139 a month, Moz at $99, and a long tail of partner-only APIs your agent will never get near. Treg carries those accounts itself and bills fractions of a cent per call. If your agent needs a keyword volume lookup twice a week, you were never going to buy the seat.
The architectural claim is the part worth chewing on: the proxy relays, it never models the upstream, and it injects auth server-side, so callers never hold keys and the integration survives upstream API changes. Both halves of that are load-bearing. Every MCP server that wraps and re-shapes an upstream API breaks the week the upstream ships v3. And every credential you hand an agent is a credential that can walk out through a conversation β see this week's Muse filesystem export for what that looks like in practice.
Alongside the catalog you can register your own APIs, OAuth connections, vendor CLIs and skills under your org's credentials, which is what makes it a registry rather than a reseller. License is Apache 2.0 with a carve-out: self-host freely, but reselling it as a competing hosted service needs written permission. Using the hosted treg.to inside your product is fine.
https://github.com/superdesigndev/treg
Comments