README

Treg (OpenRouter for Tools)

!treg — the tool catalog for your agent

OpenRouter, but for agent tools instead of models. Point an agent at one base URL with one token
and it can do the job: a curated catalog of thousands of endpoints across many providers — SEO and backlinks,
social and trends, people and company enrichment, ads, scraping, image and video generation —
priced per call, from a cent,
with no provider signup. Plus your own team's keys, skills and CLIs, callable by every teammate's
agent without the credential ever leaving the server.

Ask for the task, not the tool. You do not need to know which vendor sells backlink data, or to
hold an account with them. Search for what you want to do, read the price, call it.

Built for the Superdesign team, live at treg.to — anyone can self-host.

 Why it exists

The tools an agent needs for real work sit behind subscriptions nobody buys for a single run —
Semrush $139/mo, Moz $99/mo, Crunchbase $99/mo, Apollo $59/seat — behind signup walls, or behind no
public API at all (invite-only, partner-only, app-review-only). treg carries those accounts and
bills fractions of a cent per call.

 Two kinds of tool, one token

- The catalog — external endpoints treg can serve with its own key or through a verified public
  route that needs no provider key. Own-key calls use the team's prepaid balance; anonymous calls
  are free. No account with the provider is needed. New verified accounts receive $1.00 free
  once, when they create an eligible team.
- Your own tools — anything a teammate registered: a paid API account, an OAuth connection, a
  vendor CLI, a SKILL.md. Your own key always wins over treg's, and those calls are never
  metered.

The vocabulary for the second half:

- tool = something the registry calls for you with the org's credential. Two kinds:
  - endpoint — an upstream base_url + credential bindings (each binding injects one
  secret into the request; a request can carry several, e.g. an OAuth bearer and a
  developer-token header).
  - CLI — a vendor binary (stripe, gh, vercel, ...) run with the credential injected.
- skill / bundle = a recipe (SKILL.md) + its secrets + its tool(s), registered together.

The one rule: the proxy relays, never models the upstream, and injects auth server-side
— so it survives upstream API changes and callers never hold keys.

---

 Part 1 · Using the registry

Visit treg.to (hosted on Render) — the dashboard,
sign-in, and every URL below live there.

 Quickstart

Same flow as the dashboard's Getting started guide:

bash
 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