One Token, 3,000+ Tool Endpoints, No Provider Signup

You've got an agent that needs backlink data, or a TikTok profile, or a voice clip generated. The tool exists, but it's behind a $139/month Semrush subscription, a signup wall, or an invite-only API you'll never get into. What if you could just... call it? That's the idea behind Treg, a tool catalog for agents that works like OpenRouter does for models—one base URL, one token, and a whole lot of endpoints.

What It Does

Treg is a registry and proxy for agent tools. Point your agent at a single base URL with a single token, and it can call over 3,000 catalogued endpoints across 60+ providers—SEO and backlinks, social and trends, people and company enrichment, ads, scraping, image and video generation. Calls are priced per use, starting from a cent, and you don't need to sign up with any of the underlying providers. Treg carries those accounts and bills you fractions of a cent per call.

There are two kinds of tools here. The catalog covers external endpoints Treg serves with its own key or through a verified public route. Your own tools cover anything a teammate registers—a paid API account, an OAuth connection, a vendor CLI, a SKILL.md. The proxy relays requests, never models them, and injects auth server-side. That means it survives upstream API changes, and callers never hold keys. Your own key always wins over Treg's, and those calls are never metered.

Why It's Cool

• The pricing math actually works for one-off runs. The README lays it out plainly: Semrush at $139/month, Moz at $99/month, Crunchbase at $99/month, Apollo at $59/seat. Those are subscriptions nobody buys for a single run. Treg lets you pay per call instead, which is the right shape for agent work that's bursty and unpredictable.

• You ask for the task, not the tool. This is the part that changes how you think about agent tooling. You don't need to know which vendor sells backlink data or hold an account with them. You search for what you want to do, read the price, and call it. treg catalog search "backlinks for a domain" finds a tool by what it does, not by its name.

• Credentials never leave the server. For team tools, the proxy injects auth server-side. Every teammate's agent can call the same registered tool without anyone holding the key. That's a real security improvement over the usual pattern of passing secrets around in environment variables.

• Skills and CLIs are first-class. A registered tool can be an upstream endpoint with credential bindings (each binding injects one secret—a request can carry several, like an OAuth bearer and a developer-token header), or a vendor binary like stripe, gh, or vercel run with the credential injected. A skill or bundle packages a SKILL.md recipe, its secrets, and its tools together.

• It's self-hostable. Built for the Superdesign team and live at treg.to, but anyone can self-host. New verified accounts get $1.00 free once, when they create an eligible team.

How to Try It

The quickstart mirrors the dashboard's Getting started guide:

# 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)

Once you're in, you can inspect any catalog tool's inputs with treg catalog get <id>. For an example of a real call, here's Fish Audio's speech endpoint—binary stdout, so you redirect it to a file:

treg call fishaudio.tts.s2-1-pro --method POST --header model=s2.1-pro \
  --data '{"text":"Hello from treg","format":"mp3"}' > speech.mp3
treg call fishaudio.voices.discover --query self=false --query licensed=false --query language=en
treg resources list --provider fishaudio --kind voice

With your own Fish key, requests stay an unrestricted, unmetered upstream relay and Fish owns the account boundary.

The dashboard, sign-in, and every URL above live at treg.to. The source is at github.com/superdesigndev/treg.

Final Thoughts

Treg is best for teams running agents that need a wide range of external capabilities without buying a subscription for each one. The per-call pricing and the "ask for the task, not the tool" search model fit agent workflows well, and the server-side auth injection solves a real problem for teams sharing credentials. If you're building agents that touch SEO, enrichment, scraping, or media generation, it's worth a look—especially since you can self-host if you'd rather keep it in-house.