Treg

Treg is a self hosted registry for giving coding agents controlled access to external APIs, shared team tools, and internal credentials. With Treg, an agent can call SEO tools, scraping services, enrichment APIs, social data providers, ads platforms, and team owned endpoints through a single registry rather than juggling separate vendor accounts and local API keys.

The useful part is the credential model. Treg stores secrets on the server, injects them into outbound calls, and gives agents a token that identifies the team and permitted tools. That makes it relevant for agencies, growth teams, and builders who want agents to do real research or operations work without handing every machine a pile of vendor keys.

It is still early infrastructure. The hosted product uses prepaid per call pricing with a free starting balance, while the self hosted server can run with Python, a database, and a durable encryption key. Treat it as sensitive control plane software, not a casual utility. The license also needs care: the repo uses Apache 2.0 with extra terms that restrict offering it as a hosted third party service without permission. For internal use, Treg is worth testing if agents already touch paid APIs or shared credentials.