Treg is a credential-holding proxy and tool registry that lets an AI agent reach thousands of third-party APIs through a single base URL and a single token. It is aimed at developers building agents, and at teams that want one shared place for the API keys, vendor CLIs and internal skills those agents call. The project is written in Python, was built for the Superdesign team, runs as a hosted service at treg.to, and can be self-hosted by anyone.
What it does
The pitch is "OpenRouter, but for agent tools instead of models." Instead of a router that picks between language models, Treg routes calls to the tools an agent needs to do actual work.
The catalog side covers, by the project's own count, more than 3,000 endpoints across over 60 providers: SEO and backlinks, social and trends, people and company enrichment, ads, scraping, and image and video generation. Calls are priced per call, from a cent, and no account with the upstream provider is required.
The reason this matters is stated plainly in the README. The tools an agent needs for real work sit behind subscriptions nobody buys for a single run — Semrush at $139 a month, Moz at $99, Crunchbase at $99, Apollo at $59 a seat — or behind signup walls, or behind no public API at all, the invite-only and partner-only kind. Treg carries those accounts and bills a fraction of a cent per call.
The second half is your own tools. Anything a teammate registers — a paid API account, an OAuth connection, a vendor CLI, a SKILL.md — becomes callable by every teammate's agent. Your own key always takes precedence over Treg's, and calls made with it are never metered.
The interaction model follows from that: ask for the task, not the tool. You do not 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.
How it works
Everything hangs off one token pointed at one base URL. Behind it, Treg distinguishes two kinds of tool.
- Catalog entries are external endpoints Treg can serve either with its own key or through a verified public route that needs no provider key at all. Own-key calls draw on the team's prepaid balance; anonymous calls are free.
- Registered tools belong to your organisation. An endpoint here is an upstream
base_urlplus credential bindings, where each binding injects one credential into the outgoing call.
The important property is that the credential never leaves the server. A teammate's agent can use a shared vendor account without the secret ever being copied into a config file, an environment variable on a laptop, or a prompt. The repository's GitHub topics — proxy, registry, secrets, credentials, api-keys, mcp, cli — describe the shape of the thing accurately.
Getting started
There are two paths. The hosted instance at treg.to is the quick one; self-hosting is the other, and the README says explicitly that anyone can do it. New verified accounts receive $1.00 of free credit, once, when they create an eligible team — enough to try a few real calls before deciding.
The video demo runs through the CLI: search the catalog for a backlink analysis tool, get a result in seconds, run one command, and get real data back, priced from a cent, with no provider account involved. The repository itself carries the current install and configuration steps, and there is a Discord community linked from the project description.
When to use it / when not
It fits when an agent needs occasional access to data that is only sold by the month, when you want a team's credentials in one server rather than scattered across machines, or when you genuinely do not know which vendor sells the thing you need and would rather search by task.
It fits less well when you already use a vendor heavily enough to justify the subscription — though in that case you can register your own key and those calls are never metered — or when you need a direct contractual relationship with a provider for compliance reasons. Anything that cannot tolerate a broker in the request path is also a poor match. It is worth noting the repository is young: created in July 2026, with its most recent push in September 2026, at about 2,000 stars and 200 forks.
Alternatives
The materials name no direct competitor, which is itself informative. The nearest reference point is the one the project chooses for itself: OpenRouter, which solves the same aggregation problem one layer down, for models rather than tools. The realistic alternatives are the status quo it argues against — buying each subscription outright, wiring up a separate integration and key per vendor, or building your own credential proxy in front of them.
Take Treg seriously if you are building agents that need to touch commercial data APIs and you have felt the friction of sixty logins, sixty billing relationships and sixty places a secret can leak. The per-call pricing changes what is worth trying, and the own-key-wins rule means adopting it does not mean abandoning accounts you already pay for. Treat it as new infrastructure rather than settled infrastructure, and read the pricing and self-hosting sections before you route production traffic through it.