Superdesign's treg gives agents one token for thousands of API tools
The Superdesign team has published treg on GitHub, a registry and proxy that its README calls "OpenRouter, but for agent tools instead of models." An agent is pointed at one base URL with one token. From there it can reach a curated catalog of thousands of endpoints across many providers, priced per call from a cent, with no signup at each provider. The listed categories are SEO and backlinks, social and trends, people and company enrichment, ads, scraping, and image and video generation. The same token also covers a team's own keys, skills and CLIs, which every teammate's agent can call without the credential leaving the server.
The pitch is "ask for the task, not the tool." The README argues that the tools agents need for real work sit behind subscriptions nobody buys for a single run, and it cites Semrush at $139/mo, Moz at $99/mo, Crunchbase at $99/mo and Apollo at $59/seat. Others sit behind signup walls or have no public API at all (invite-only, partner-only, app-review-only). Treg carries those accounts and bills fractions of a cent per call. The hosted version lives at treg.to, built for the Superdesign team, and the README says anyone can self-host.
There are two halves. The catalog is made of external endpoints that treg serves with its own key or through a verified public route that needs no provider key. Calls on treg's own key use the team's prepaid balance; anonymous calls through a public route are free. New verified accounts get $1.00 free once, when they create an eligible team. The second half is a team's own tools: a paid API account, an OAuth connection, a vendor CLI or a SKILL.md. Your own key always wins over treg's, and those calls are never metered. A tool is either an endpoint (an upstream base URL plus credential bindings, where each binding injects one secret) or a CLI such as stripe, gh or vercel, run with the credential injected. A skill or bundle is a SKILL.md recipe plus its secrets and tools, registered together. The stated design rule is that the proxy relays, never models the upstream, and injects auth server-side, so it survives upstream API changes and callers never hold keys.
A catalogued call follows a credential ladder: first the team's own registered tool for that provider; then a secret the team stored, injected through a virtual tool; then, if the endpoint has a verified public route, no provider key and no charge; otherwise treg's own key, billed to the team's prepaid balance. An endpoint with no published price is refused rather than served free, and the caller is told to connect their own key. Where several providers serve one capability, catalog search lists them side by side with prices, and the choice is the caller's: treg does not silently pick or fail over between providers. The exception is treg.
Getting started is a curl install script, then treg login (GitHub by default, a one-time email code, or a token for agents and CI), then commands such as treg catalog search "backlinks for a domain", treg call tikhub.tiktok.user.profile --query uniqueId=tiktok and treg balance. A Claude plugin installs with /plugin marketplace add superdesigndev/treg; other agents can use npx skills add superdesigndev/treg -s treg. The README also says the skill ships through the MiniMax Plugin Marketplace. A Claude Connectors Directory surface at /mcp/v2/ exposes only curated catalog endpoints and separates read calls from write calls; the older /mcp/ surface stays available for catalog endpoints, team-owned tools and imported skills.
For sharing a team's own credentials, treg scan previews what could be registered and treg upload registers it, encrypted server-side. Upload matches .env keys against about 80 known providers and also picks up skill subdirectories and installed catalog CLIs. Agents can use an upstream by prefixing the real URL with the proxy (GET https://treg.to/call/ followed by the upstream URL, with the X-Treg-Token header, which is stripped before the upstream sees it). treg run executes a vendor CLI locally or, with --server, on the registry, and treg runs is the audit log. Two public comparison pages are also described: Enrich Arena, where enrichment answers are compared by cost and speed (browsing is public, submitting needs login and uses team credits), and Web Arena, which compares Web Search, Web Fetch and Sitemap providers, with a live leaderboard over a rolling 30-day window. An account can own up to 10 teams.
Key facts
- Treg is described by its README as OpenRouter for agent tools: one base URL and one token reach a curated catalog of thousands of endpoints, priced per call from a cent.
- Team-registered keys, skills and CLIs are callable by every teammate's agent with credentials injected server-side; your own key always wins and those calls are never metered.
- Catalog calls follow a credential ladder: own tool, stored secret, free verified public route, then treg's own key billed to a prepaid balance. New verified accounts get $1.00 once.
- Endpoints without a published price are refused rather than served free, and treg does not silently pick or fail over between providers, except for treg.
routed endpoints. - Hosted at treg.to and self-hostable; the CLI sends anonymous usage data to PostHog when using treg.to, and this can be turned off.
Why it matters
Agents doing real work often need data and services locked behind per-seat subscriptions, signup walls or partner-only access. Treg tries to turn that into one token and a per-call price, the way OpenRouter did for model access. Its search-by-task approach means an agent does not need to know which vendor sells a given kind of data. The README's examples of what that replaces are Semrush at $139/mo, Moz at $99/mo, Crunchbase at $99/mo and Apollo at $59/seat, figures the README itself supplies.
Who it affects
Teams building or running agents that need SEO, enrichment, scraping, social or media-generation APIs without holding accounts at each vendor. It also reaches teams that want to share keys, skills and vendor CLIs (stripe, gh, vercel and others) across teammates' agents without handing out raw credentials. Claude users are addressed directly through a plugin and a Connectors Directory surface, and the README mentions MiniMax Code and MiniMax Agent users too.
How to use it
Install the CLI with the curl script from treg.to, run treg login (GitHub by default, --email for a one-time code, --token for agents and CI), then search with treg catalog search and call with treg call. Check spend with treg balance and add funds with treg topup. Claude Code users can run /plugin marketplace add superdesigndev/treg and /plugin install treg@treg; others can use npx skills add superdesigndev/treg -s treg. To share your own credentials, run treg scan to preview and treg upload to register. Anyone can also self-host. New verified accounts get $1.00 free once on creating an eligible team, and anonymous calls through a verified public route are free. No licence is named in the visible text, only that anyone can self-host.
How solid is it
The source is the project's own README, so every claim is the authors' description and none is independently verified; that includes the competitor subscription prices. The visible text gives no launch date, version number or release date. No usage figures, customer counts or adoption numbers appear in the visible text. The exact number of catalog endpoints is not given beyond "thousands", and the visible text does not list per-call prices for specific endpoints beyond "from a cent" and "fractions of a cent". The source text is truncated mid-sentence, so anything after the teams and org scoping paragraph is not covered here.
Risks and caveats
Treg sits in the path of every call and holds credentials server-side, so using the hosted service means trusting treg.to with those secrets; self-hosting is offered as the alternative. The CLI sends anonymous command usage (no arguments or credentials) to PostHog when using treg.to; setting TREG_TELEMETRY=0 or DO_NOT_TRACK=1 disables it. Choosing between providers for a capability is left to the caller, with no silent failover, except on treg.
“Ask for the task, not the tool.”
— treg README