Overview
Treg is an open-source tool gateway for AI agents. Its shorthand pitch is "OpenRouter for agent tools": one token gives an agent access to a catalog of provider APIs, with upfront pricing, provider comparison, and bring-your-own-key routing.
The official homepage lists 2,630 endpoints across 47 providers. The catalog spans SEO, keyword research, backlinks, SERP data, analytics, social publishing, lead enrichment, ads, company signals, local business data, and other specialist APIs that agents often need but individual teams rarely want to subscribe to one by one.
That makes Treg useful for agent builders who have moved beyond prompt-only work. A coding agent can write code, but many business workflows require external tools: search data, email lookup, ad metrics, creator analytics, company enrichment, or OAuth-backed account data. Treg gives those workflows a common routing layer for AI agent tools.
Key Features
- Unified agent token - Agents use one Treg token instead of separate credentials for every provider.
- Large tool catalog - The homepage shows 2,630 endpoints across 47 providers, with examples across SEO, ads, sales, social, analytics, and web data.
- Task-based selection - Agents ask for the task, while Treg compares tool providers by price, measured success rate, and speed.
- Upfront per-call pricing - Treg quotes usage-based prices before calls and describes a no-subscription model.
- Bring your own keys - If a team already pays for a provider, Treg can route calls through that key and avoid metered usage.
- Org skills and secrets - The homepage describes turning API keys and
SKILL.mdfiles into callable tools while keeping secrets server-side. - Open-source code - Treg is presented as 100% open source under AGPL.
How to Get Started
Start with one agent workflow that currently fails because it lacks a real external tool. Good examples include weekly SEO reporting, backlink checks, competitor keyword analysis, lead enrichment, Google Analytics summaries, or campaign monitoring.
The official setup path points agents to Treg's llms.txt resource. From there, give the agent a Treg token, pick a narrow workflow, and review which endpoints it selects. For production, decide whether to use Treg's metered provider access, bring your own keys for vendors you already pay for, or mix both.
For teams building internal automation, Treg can sit next to AI productivity systems as the tool access layer. It should not replace governance: teams still need approval rules for sending messages, modifying ad budgets, exporting customer data, or calling paid APIs.
Pricing & Plans
Treg uses a usage-based model. The official homepage says it carries provider subscriptions, bills fractions of a cent per call, shows the price before the call, starts users with free credit, and adds 0% additional markup over provider rate in the examples shown.
| Cost area | What to expect |
|---|---|
| Starting access | Free starting credit listed on the official homepage |
| Metered calls | Per-call pricing shown before execution |
| Existing vendors | Bring-your-own-key routing can make those provider calls unmetered by Treg |
| Subscriptions | Treg is designed to avoid buying every provider seat for occasional agent runs |
The actual cost depends on which endpoints agents call and how often workflows run. Set budgets and approval thresholds before giving agents access to expensive or action-taking tools.
Best For
- Agent builders who need access to many business APIs without separate subscriptions
- Growth, SEO, sales, and marketing teams using coding agents for operational workflows
- Developer teams building internal agents with shared secrets and reusable skills
- Organizations that want one gateway for provider API access, pricing, and key rotation
- Teams comparing tool-routing layers for AI data analysis and agent automation
Treg is most compelling when the agent already knows what work to do but lacks the tools to do it. If your workflow only needs one provider API, direct integration may be simpler. If it needs a rotating catalog of specialist tools, Treg is worth a closer look.
FAQ
What is Treg?
Treg is an open-source tool gateway that gives AI agents access to thousands of provider API endpoints through one token.
Why is Treg called OpenRouter for tools?
Like a model router, Treg gives agents one access layer. Instead of routing to models, it routes to external tools and APIs based on task, price, and measured performance.
Is Treg open source?
Yes. The official homepage describes Treg as 100% open source under AGPL.
How does Treg pricing work?
Treg uses usage-based per-call pricing with prices shown before calls. The homepage also describes free starting credit and bring-your-own-key routing.
Who should use Treg?
Treg fits teams building agents that need SEO, ads, sales, analytics, web, enrichment, or other specialist APIs without managing many provider accounts separately.
