Configuration
The plugin uses the registry token in TREG_TOKEN for its MCP entry. Without that variable, the MCP row stays disabled. The CLI uses the same token through its X-Treg-Token request header after treg login; the README lists GitHub sign-in, a one-time code with --email, and --token for agents or CI.
Commands
| Command |
Purpose |
treg catalog |
List catalogue platforms, busiest first. |
treg catalog search "..." |
Search endpoints by the task they perform. |
treg catalog get <tool> |
Display parameters, price and an example response. |
treg call <tool> [path] |
Call a catalogue or registered tool; --query supplies query values. |
treg balance |
Show remaining credit, calls in flight and recent spend. |
treg topup |
Add funds or configure automatic top-ups. |
treg tool ls |
List tools shared with the team. |
treg health |
Check credential health. |
treg scan |
Preview keys, skills and CLIs that an upload would register. |
treg upload |
Register detected items; --replace updates existing ones. |
treg secret add |
Store a secret for later injection. |
treg add |
Register an endpoint using --base-url and --secret. |
treg calls |
View the call audit log. |
upload env --select can select known providers from .env; the scanner matches keys against roughly 80 providers and examines skill subdirectories and installed catalogue CLIs.
How it behaves
For a catalogue call, credential selection prefers a team-registered tool, then a team-stored provider secret, then treg's own key. Team credentials are not metered; calls using treg's key use the team's prepaid balance. When no published price exists, the endpoint is refused. If several providers match, the caller chooses rather than receiving silent failover. An out-of-balance response is HTTP 402 and includes balance_micro, estimated_cost_micro and topup_url.
Requirements
The README documents the hosted registry at treg.to and says it can be self-hosted. The Claude Code installation loads the skill as treg:treg; its first run guides CLI setup, sign-in and treg mcp install. The command-line examples require a working treg CLI and credentials.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub