Treg.to

What treg.to does

treg.to gives agents one place to discover and invoke tools from many providers. The catalog covers tasks including keyword and rank tracking, backlink research, AI visibility, social and trend data, people and company enrichment, advertising, measurement, scraping, and image, video, or audio generation. Teams can also register their own paid APIs, OAuth connections, vendor CLIs, and SKILL.md-based workflows.

The service is designed around task discovery rather than vendor selection. An agent can search for an operation such as finding a work email or backlinks for a domain, inspect the matching tool's inputs and price, then call it through the same authenticated interface.

How it works

A caller uses a shared token, sent as the X-Treg-Token header, across the available tools. For a catalog request, treg.to selects credentials in this order: a team-registered tool, a team-stored provider secret, a verified public route, or treg.to's own provider account. The last option is charged against the team's prepaid balance; verified public routes can be free, and team-owned calls are not metered.

Authentication is injected on the server, so provider credentials stay out of the agent's possession. The proxy relays upstream requests instead of modeling each provider's API, which lets callers use the catalog through a consistent tool interface. Endpoint tools can inject multiple credential bindings, while CLI tools run vendor binaries with credentials supplied by the registry.

Setup and configuration

Install the treg CLI with the install script, then authenticate with treg login. Login supports the default GitHub flow, a one-time email code, or a token for agents and CI. Search the catalog with treg catalog search, inspect a tool with treg catalog get, and invoke it with treg call.

The CLI also supports treg mcp install, which connects an agent to treg.to's MCP surface. A Claude Code plugin can be installed from the treg marketplace without initial configuration; its skill guides the user through login and MCP setup. Workflow skills can be installed individually or as a set with the skills CLI or treg skill bootstrap.

Teams can inspect shared tools with treg tool ls, check credential status with treg health, and review usage with treg balance. Fish Audio examples demonstrate that binary responses can be redirected to a file and that generated voices can be listed as team resources.

Tools and capabilities

• Search the catalog by the task an agent needs to complete.
• Inspect tool parameters, declared query fields, prices, and example responses.
• Call catalog endpoints through treg call, including requests with query parameters, headers, methods, and request bodies.
• Relay team-owned API endpoints, OAuth connections, vendor CLIs, and registered skills.
• Run workflow skills for web access, lead signals, recruiting, UGC creation, and other documented tasks.
• List team resources and inspect shared tool or credential health.

Catalog tools marked strict_query validate query parameters and request bodies against their declarations. The Claude connector surface at /mcp/v2/ restricts access to curated catalog endpoints and separates read operations from writes; the existing /mcp/ surface also supports team tools and imported skills.

Limitations and notes

Provider coverage and behavior depend on the catalog entry and its available credential route. Catalog calls using treg.to's own accounts consume prepaid balance, while a team's own provider key takes precedence and remains unmetered. The caller must follow each tool's declared inputs when strict_query is enabled.

The proxy does not normalize upstream APIs into a shared provider-specific model; it forwards requests and supplies authentication. Some workflow skills and media operations therefore have their own input or output behavior, such as binary speech output from Fish Audio. The hosted service is available at treg.to, and the project can also be self-hosted.