Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

treg

A pay-per-call tool registry for agents: one token reaches thousands of third-party API endpoints, with keys held on the server.

Reviewed by ReviewRamble editors · Updated

View on GitHub Pay per use

Our rating

3.6/5

A clever answer to the subscription wall around agent data, if you are comfortable handing a young service both your spend and your API keys.

What is treg?

treg describes itself as OpenRouter for agent tools. An agent gets one base URL and one token, searches a catalog by the job it wants done (backlinks, people enrichment, social trends, scraping, image and video generation), reads the price and calls the endpoint. The hosted service at treg.to lists 4,100+ endpoints from 127 providers and bills a prepaid team balance per call, with no provider sign-up.

Teams can also register their own API keys, OAuth connections, vendor CLIs such as stripe and gh, and SKILL.md recipes; the server stores the secrets encrypted and injects them into each request, so teammates' agents never hold the key. Access is by CLI, HTTP proxy, MCP server or Claude Code plugin. It is written in Python by Superdesign, self-hostable, and at v1.0.0-beta.2 (12 November 2026).

Is treg worth it?

treg solves a real problem for anyone running agents on business tasks: the data an agent needs sits behind subscriptions nobody buys for one run. The README cites Semrush at $139 a month, Moz at $99 and Crunchbase at $99. treg holds those accounts and resells single calls, such as $0.0018 per Semrush keyword or $0.01 per Crunchbase call, from a balance topped up in advance. Search is by task, not vendor, and when several providers serve one job the catalog shows their prices side by side.

The second half is a credential broker for a team. You register a key or an OAuth connection once, and treg injects it server-side into each request, so the agent never sees the secret and every call lands in an audit log. treg upload scans a project's .env against about 80 known providers and uploads what you approve, encrypted with a Fernet key. That is convenient and also the main risk: the registry becomes one place that holds every key your team owns, and on treg.to that place is someone else's server. Self-hosting keeps it in-house, but losing the Fernet key loses every stored secret, and leaving it unset gives an ephemeral key that does not survive a restart.

The catch: this is beta software moving at speed, with 7,908 stars, 311 open issues and pull requests, and a v1.0.0-beta.2 tag. The homepage calls it 100% open source under Apache 2.0, but the LICENSE adds a term that forbids offering it as a hosted service to third parties without permission, so it is source-available rather than open source in the strict sense. The CLI sends anonymous usage data to PostHog unless you set TREG_TELEMETRY=0, and no data-retention policy or SOC 2 report is published.

Our take: for one-off research runs, paying cents per call beats a $99 seat, and the price shows before you spend it. Keep production keys for systems that matter on a self-hosted instance, or out of the registry entirely, until the project leaves beta.

Where it earns its place

  • A two-person SEO agency

    Pull backlink and keyword data for a client audit without three monthly seats

    treg catalog search "backlinks for a domain" lists providers with prices; the agent calls them on the prepaid balance, at $0.00018 per Moz backlink row in the homepage's example.

  • A 15-person startup sharing a Stripe and Intercom account

    Let every engineer's agent call internal APIs without copying keys into .env files

    An admin runs treg add stripe with a stored secret; agents call through treg.to/call/ with their own token, and treg calls lists each request for audit.

  • A recruiter at a 50-person company

    Turn a LinkedIn job post into a ranked shortlist with cited evidence

    The bundled recruit skill runs people search, filters and contact lookups through treg under a per-candidate spend cap, writing a run file of counts and vendors used.

Before you commit

Setup
curl -fsSL https://treg.to/install.sh | sh, then treg login with GitHub, email or a token; or /plugin install treg@treg in Claude Code. Self-hosting needs Python with the server extra, Postgres in production and a TREG_SECRET_KEY.
Integrations
CLI, HTTP proxy at /call/, MCP endpoints (/mcp/ and a curated /mcp/v2/ for Claude.ai), Claude Code and MiniMax plugins, skills via npx skills add; WorkOS for enterprise SSO.
Data and privacy
Team secrets are stored Fernet-encrypted and injected server-side; requests and responses are relayed to the provider unchanged and every call is audited. The CLI sends anonymous usage to PostHog unless TREG_TELEMETRY=0. No retention policy or SOC 2 report published.
Cost at scale
Provider price per call with what the homepage calls a 0% fee; your own keys are unmetered. Costs follow volume, so a heavy enrichment job can exceed a flat subscription.
Limits
An endpoint without a published price is refused; out of balance returns HTTP 402; server-side CLI execution is disabled; licence forbids reselling it as a hosted service.

What’s good

  • 4,100+ endpoints from 127 providers on one token, priced per call
  • Keys are injected server-side, so agents never hold them
  • Your own keys always win over treg's and are not metered
  • Self-hostable, with CLI, HTTP proxy, MCP and Claude Code plugin access

What’s not

  • Hosted mode concentrates every team secret on a third-party server
  • Custom licence bars offering it as a service to others
  • Beta, with 311 open issues and pull requests
  • Anonymous telemetry on by default; no retention policy published

Best for

Growth, sales and research teams whose agents need occasional calls to paid data APIs they would not otherwise subscribe to.

treg alternatives

treg: common questions

Is treg worth it?
A clever answer to the subscription wall around agent data, if you are comfortable handing a young service both your spend and your API keys. We rate it 3.6 out of 5.
How much does treg cost?
Self-hosting is free under a modified Apache-2.0 licence. Hosted treg.to charges per call from a prepaid balance (examples: $0.0018 per Semrush keyword, $0.01 per Crunchbase call), with $1.00 of free credit once per verified account; calls on your own keys are not metered.
What are the downsides of treg?
Hosted mode concentrates every team secret on a third-party server; custom licence bars offering it as a service to others; beta, with 311 open issues and pull requests; anonymous telemetry on by default; no retention policy published.
Who is treg best for?
Growth, sales and research teams whose agents need occasional calls to paid data APIs they would not otherwise subscribe to.
How much does treg cost for a team or in production?
Provider price per call with what the homepage calls a 0% fee; your own keys are unmetered. Costs follow volume, so a heavy enrichment job can exceed a flat subscription.
Is treg safe for company data?
Team secrets are stored Fernet-encrypted and injected server-side; requests and responses are relayed to the provider unchanged and every call is audited. The CLI sends anonymous usage to PostHog unless TREG_TELEMETRY=0. No retention policy or SOC 2 report published.
What are the best treg alternatives?
The closest alternatives we have reviewed are ToolHive, McpMux and Agent Reach.

Answers checked Nov 13, 2026.