Open-source Treg gives AI agents one URL and token for thousands of tools

One token, thousands of endpoints

A new open-source project called Treg is billing itself as "OpenRouter for agent tools." According to the project's README, which surfaced on Hacker News's front page on 7 October, an agent pointed at a single base URL with a single token can reach a catalog of thousands of endpoints curated across many providers: SEO and backlink data, social and trend services, people and company enrichment, advertising, scraping, and image and video generation. Calls are metered individually, starting at a cent, without the caller signing up with any provider. The hosted service runs at treg.to (on Render, per the README), and the whole thing is self-hostable.

The pitch is that you search for the job you want done, check the price, and fire the call — no need to know which vendor sells backlink data or to hold an account there. The README demonstrates the flow with a TikTok profile lookup and a Fish Audio text-to-speech call working right after sign-in, with a balance command reporting exactly what each one cost.

Built to get around subscription walls

The stated motivation is that tools agents need for real work are locked behind subscriptions nobody buys for one job. The README names figures such as Semrush at $139 per month, Moz at $99 per month, Crunchbase at $99 per month and Apollo at $59 per seat, along with services that are invite-only, partner-only or app-review-only with no public API at all. Treg holds those provider accounts itself and charges sub-cent amounts per call against a prepaid balance.

How a call gets served

Two kinds of tool share the one token. The first is the public catalog: external endpoints that Treg can serve either with its own key or via a verified public route requiring no provider key at all. Paid catalog calls draw on a team's prepaid balance, anonymous-route calls are free, and newly verified teams get a one-off $1.00 credit.

Catalog requests follow a fixed order of precedence, per the README: first a tool the team registered for that provider; then a stored provider secret injected into the request; then a verified free public route; and only in the last case Treg's own key, billed to the balance. A team's own key always takes priority and is never metered, and caller-supplied provider headers pass through so callers can spend their own credits. Endpoints without a published price are refused rather than served for free — the team is told to connect its own key instead. Where multiple providers offer one capability, search results list them side by side with prices, and the project says it never silently picks one or fails over between them; if its own provider account runs dry it may relay through a Treg-owned account, disclosed in the response, with a team-level opt-out.

The second kind is everything a team brings itself: a paid API account, an OAuth connection, a vendor CLI like stripe or vercel, or a SKILL.md recipe. Once registered, every teammate's agent can call it, and credentials are injected server-side so they never reach the caller.

Relay-first design and agent integrations

The architecture rests on one rule: the proxy relays requests rather than re-implementing the upstream, and injects authentication on the server, which the project says keeps it working when upstream APIs change while callers never see the underlying secrets. Tools take two forms — endpoints, meaning an upstream base URL plus credential bindings, and CLIs, meaning vendor binaries executed with credentials injected. A skill or bundle packages a recipe, its secrets and its tools together.

Integrations include a curl-installed CLI with GitHub, email-code or CI-token sign-in; a zero-configuration Claude Code plugin; ready-made workflow skills such as lead-signals, which surfaces likely buyers from public signals like complaints, job changes and funding, and make-ugc for AI-generated presenter videos; the same skill shipped via the MiniMax Plugin Marketplace; and an MCP surface listed in the Claude Connectors Directory that exposes only curated catalog endpoints and separates reads from writes so clients receive accurate safety signals.

Why it matters

OpenRouter demonstrated what happens when a fragmented provider market gets a single API and a single meter: it turns into default plumbing. Treg applies the same shape to the tool layer, where the friction is arguably worse — per-seat SaaS contracts and closed APIs rather than per-use pricing. If the catalog holds up, agents can be composed against capabilities instead of vendors, teams get centralized credential custody rather than keys scattered across laptops and CI, and occasionally needed tools stop demanding monthly commitments.

The trade-offs are just as clear. Routing every call through a third-party relay concentrates trust in one operator and inserts a middleman into billing, reliability and data flows. The project's answers — published prices, refusal of unpriced calls, disclosure of relay accounts, bring-your-own-key support — are policy commitments, and any team adopting it will want to audit them. Self-hosting moves the trust boundary but hands the burden of carrying provider accounts back to you.