explaingit

superdesigndev/tools-registry

Analysis updated 2026-05-18

56PythonAudience · developerComplexity · 3/5Setup · moderate

TLDR

Treg is a shared registry that lets a team's AI agents call APIs and CLIs using centrally stored credentials, so keys never get pasted or leaked.

Mindmap

mindmap
  root((Treg))
    What it does
      Shared credential vault
      API proxy
      CLI credential injection
      Shared agent skills
    Tech stack
      Python
      FastAPI
      SQLite
    Use cases
      Secure agent API calls
      CLI without login
      Team skill sharing
    Audience
      Developer teams
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let AI agents call services like Stripe or Intercom without ever seeing the raw API key.

USE CASE 2

Run vendor command line tools such as gh or stripe with credentials injected automatically.

USE CASE 3

Share a reusable AI agent skill, along with its secrets and tools, across a whole team.

USE CASE 4

Control which team members can access which tools using role-based permissions.

What is it built with?

PythonFastAPISQLiteuv

How does it compare?

superdesigndev/tools-registryblue-guardrails/cheap-ocreadmin2/jarvis_ai
Stars565656
LanguagePythonPythonPython
Setup difficultymoderatehardhard
Complexity3/54/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Self-hosting the server needs extra dependencies like FastAPI and a database, the hosted version only needs the CLI.

The explanation does not state a license, so terms of use are unclear.

In plain English

Treg, short for Tool Registry, is a shared vault for a team's API keys, command line tools, and reusable AI agent skills. The problem it solves is that people building with AI agents often end up pasting API keys directly into an agent's context or sharing them in chat messages, which risks leaking those keys. Treg gives a team one place to store that information, so agents and coworkers can use shared tools and secrets without ever seeing the actual keys. There are three kinds of things a team can register with Treg. An endpoint is a web API, like Stripe or Intercom, along with the credential needed to call it, requests get routed through Treg, which quietly attaches the right key before sending the request on to the real service. A CLI is a command line tool such as the GitHub or Vercel command line programs, which Treg can run on your behalf with the correct login already injected, so you never type or store the credential yourself. A skill is a bundled recipe, written as a file called SKILL.md, together with whatever secrets and tools it needs, so an entire capability can be shared and kept up to date in one place rather than copied around. Setup starts by installing a command line tool that talks to a hosted or self hosted Treg server, signing in, and then running a scan command that looks at a project's environment file and installed tools to suggest what could be shared. Everything in Treg belongs to an organization, and each person's access token identifies both who they are and which organization they belong to, with roles like owner, admin, member, and viewer controlling what they can do. Treg is aimed at teams building with AI agents who want those agents to call real services like Stripe or GitHub directly, with every call logged, instead of the agent ever holding a raw API key. The project can be used as a hosted service or self hosted, and it is written in Python, installed with pip, with a full server setup requiring extra dependencies such as a web framework and a database. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Walk me through installing the treg CLI and signing in for the first time.
Prompt 2
Show me how to register a Stripe endpoint with treg and call it through the proxy.
Prompt 3
Explain the difference between an endpoint, a CLI, and a skill in Treg.
Prompt 4
How do I self-host the Treg server locally for development?

Frequently asked questions

What is tools-registry?

Treg is a shared registry that lets a team's AI agents call APIs and CLIs using centrally stored credentials, so keys never get pasted or leaked.

What language is tools-registry written in?

Mainly Python. The stack also includes Python, FastAPI, SQLite.

What license does tools-registry use?

The explanation does not state a license, so terms of use are unclear.

How hard is tools-registry to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is tools-registry for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.