What problem it solves

Agents often need tools that sit behind separate vendor subscriptions, signup walls, or unavailable public APIs. The project provides one catalog and token for accessing external capabilities by task, while also letting teams share their own endpoints, CLIs, skills, and credentials without exposing secrets to callers.

Key features

• Search tools by task — Find capabilities by the work they perform instead of needing to know the provider or hold its account.

  Source: README

• Access cataloged capabilities — Call catalog endpoints through a unified CLI and token, with prices visible during discovery and balance information available after a call.

  Source: README

• Share team-owned tools — Register paid API endpoints, vendor CLIs, and skills for team use while injecting credentials server-side.

  Source: README

• Relay upstream requests faithfully — The proxy relays requests rather than modeling them and injects authentication server-side, preserving caller headers while keeping keys away from clients.

  Source: README

• Support multiple agent workflows — The registry can be accessed through its CLI, Claude Code plugin, workflow skills, Claude.ai connector, and a self-hosted server.

  Source: README, docs

Quick start

Copied verbatim from the project's README.

# 1. install the CLI — also points it at the registry
curl -fsSL https://treg.to/install.sh | sh

# 2. sign in (GitHub default · --email for a one-time code · --token for agents/CI)
treg login

# 3. do something useful immediately — no key, nothing registered
treg catalog search "backlinks for a domain"     # find a tool by what it DOES
treg call tikhub.tiktok.user.profile --query uniqueId=tiktok
treg balance                                     # exactly what that cost

# (or `treg onboard` for the guided walkthrough)

Who it may suit

This project may suit teams and developers building agents that need access to external APIs, vendor CLIs, or shared internal skills. It may also suit self-hosters who want to operate a tool registry on their own infrastructure.

Topics to discuss

• Which task-oriented catalog search and discovery workflows should be added next?

• How should teams manage access control and auditing for shared endpoints, CLIs, and skills?

• Which agent integrations and workflow skills would be most useful for the community to build?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/superdesigndev/treg#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.