Treg Review (2026): Pricing, Features & Honest Verdict

Treg is a pay-per-call gateway giving coding agents 2,630 API endpoints across 47 providers behind one key, at each provider’s rate with zero markup. The economics are excellent. The open-source claim on its homepage contradicts its own licence file. Best for: developers whose agents need paid data. Price: from $0.004 per call (free plan: no). Rating: 7.5/10.

What is Treg?

Give a coding agent a task like “find the keywords my competitor ranks for and draft outreach to their top backlink sources” and it will fail on economics, not capability. Doing that job properly means a Semrush seat at $139 a month, a Moz seat at $99, and a Hunter seat at $34. That is $272 a month in subscriptions for maybe forty API calls. Nobody buys three SaaS seats so an agent can run once a week.

Treg is the arbitrage on that. It carries the subscriptions and resells individual calls at fractions of a cent, with a single token that authenticates against every provider in the catalog. Keyword volume from Semrush runs $0.006 a call. Backlinks and anchors from Moz are $0.012. Funding and investor data from Crunchbase is $0.020. Verified work email from Hunter is $0.004. The price is quoted before the call fires, and Treg states plainly that it takes 0% on top, earning instead on the volume rates it negotiates with vendors.

It came out of Superdesign, the company behind superdesign.dev, and the makers listed on Product Hunt are Jason Zhou, Unclecode, and SToneX. The repository at superdesigndev/treg opened on 15 July 2026 and has 459 stars and 37 forks. It launched at #7 on Product Hunt’s 17 August board with 148 points.

What are Treg’s key features?

One credential for the whole catalog

The practical win is not the pricing, it is that you stop managing keys. A single treg token covers every provider, so there are no per-provider signups, no API keys scattered across machines and CI environments, and one place to revoke when someone leaves. Credentials are injected server-side and never touch the machine the agent runs on. For anyone who has audited an .env file and found six keys nobody can account for, this alone is worth the setup.

The agent asks for the task, not the vendor

Treg’s catalog is organised by job rather than by brand. You ask for “backlinks and anchors” and Treg shows you which of the nineteen providers selling that data will answer, what each charges per result, and what Treg has measured them doing: success rate, response speed, and the last time they actually returned data. The agent picks on evidence rather than on whichever vendor it happened to memorise during training. You can also pin a vendor and keep it pinned.

Bring your own keys, and they win

If you already pay for Semrush, point Treg at your key and those calls route through it unmetered. Treg’s own wording is that your key always beats the metered one. This is the feature that makes the pricing believable, because it means Treg cannot quietly become the expensive option for anything you already own. It also means the migration path in is reversible, which is not usually true of a gateway.

Your own keys and skills become callable tools

The half that gets less attention on the launch page is the private catalog. Treg scans a project and turns your own API keys and SKILL.md files into tools sitting on the same shelf as the public ones, called the same way. Teammates’ agents use them by token and the key itself never leaves the gateway. A brand-voice skill with no key and a Google Ads report bound to a token look identical to the calling agent. Rotating a credential becomes one action instead of a Slack thread.

How much does Treg cost?

Treg has no subscription and no plans. You pay per call at rates published next to every entry in the catalog, starting around $0.004 for an email lookup and running to $0.020 for company funding data. New accounts start with $1.00 of credit, and during the Product Hunt launch an upvote added $5 more. There is no free tier that renews, so once the credit is spent you are paying.

The comparison that matters is against provider seats, and Treg makes it for you on the homepage: about $371 a month of seats reduced to cents per call. For an agent making forty calls a week that is not a marginal saving, it is a different order of magnitude. Against the closest gateway competitors the picture is more even. Composio gives you 100,000 tool calls a month free and charges $29 a month on Pro with $29 of usage credit included, then $0.0003 per call. Arcade.dev gives 2,000 auth events and 2,000 tool calls free, then $25 a month plus $0.10 per auth event and $0.01 per tool call.

Those two are cheaper per call because they are mostly routing you to APIs you already have access to. Treg’s per-call rate includes the underlying paid data, which Composio and Arcade do not sell. Comparing $0.006 for a Semrush keyword lookup against $0.0003 for a Composio tool call is comparing a subscription you did not have to buy against a connector.

Here is the gap. Treg has no pricing page. We tried /pricing and it returns a 404. The rates live on the homepage and inside the catalog, which is fine for reading a single rate and useless for planning. There is no published top-up ladder, no stated minimum, no volume discount table, and nothing that answers “how do I add $50 and what does $50 buy”. For a product whose entire pitch is transparent per-call economics, not having a page that states the economics is an odd omission.

The second question nobody has answered is what happens to 0% if the vendor deals change. Treg’s margin is the spread between its negotiated volume rate and the list rate it charges you. That is a real business model and a common one. But it means the 0% markup promise is structurally different from Vendo-style published rates: it is a promise about the relationship between two numbers, only one of which you can see.

Is Treg actually open source?

The homepage says “100% open source · AGPL” in two places, and the footer repeats it. The licence file in the repository says something else.

What is actually there is the Apache License 2.0 with Additional Terms bolted on top, and the additional terms take precedence wherever they conflict. Term one is a hosted service restriction: you may use, modify and redistribute it freely, including commercially inside your own organisation, and running your own registry for your own team is expressly encouraged. What you may not do is use it to provide a hosted, managed or embedded service to third parties without written authorisation from the licensor. Term two assigns the licensor commercial rights over contributions, including in its own hosted offerings.

That is a source-available licence. It is not AGPL, which is a copyleft licence that permits exactly the hosted competition Treg’s terms forbid, and it is not open source by the OSI definition, which does not allow field-of-use restrictions. GitHub’s own API refuses to classify it and reports the licence as “Other”.

None of this makes Treg a bad deal. The restriction is narrow, it is aimed squarely at somebody cloning the registry and reselling it, and it explicitly protects the thing most readers would want to do, which is self-host for their own team. Plenty of good infrastructure ships under terms like this. The problem is the label. Calling it AGPL on the homepage tells a developer they have rights they do not have, and that developer finds out at the point where they have already built something on it. Change the badge to “source available” and the product loses nothing.

While we were checking, one smaller inconsistency: the header badge says 47 providers, the copy in the first feature section says forty-two. The catalog says 2,630 endpoints and the meta description agrees. Small, but on a page selling precision it stands out.

What does Treg’s catalog admit it cannot do?

This is the part we did not expect and it is the strongest trust signal on the site. Roughly a quarter of the catalog rows on the homepage are not products for sale, they are entries marked with why the data is unavailable.

Brand mentions in AI answers, cited-source tracking, creator analytics and Google Trends are all marked “no official API”. TikTok trends are “API: invite-only”. Instagram posts and the follower graph are “API: app review”. Reddit posts, local business data and where LLMs source their answers are “rate-limited”. LinkedIn posts and pages are “partner-only”. Company news, buying signals, hiring and headcount are “enterprise-only”. YouTube and channel analytics are “quota-capped”. The Meta Ad Library, Google Ads Transparency and the LinkedIn ad library are “manual research”. The TikTok ad library is “EU-only UI”.

A marketing page that lists what it cannot sell you, next to what it can, at the same visual weight, is rare. It also happens to be the most useful part of the catalog, because it tells you which parts of an agent workflow are going to need a human regardless of what you spend. Anyone building an AI visibility or social listening agent should read that column before writing a line of code.

Who is Treg best for?

Use Treg if you run coding agents that need paid data occasionally rather than constantly. SEO agents, lead enrichment, ad monitoring, competitive research: anything where the per-seat cost of the underlying tool dwarfs what one agent actually consumes. The break-even is obvious. If you would use less than a tenth of a Semrush seat, Treg wins on arithmetic alone.

Use it if key sprawl is a real problem for you, or if you want teammates’ agents sharing skills and credentials without the credentials leaving a gateway.

Skip Treg if you already pay for the providers at volume, because the bring-your-own-key path reduces Treg to a routing convenience you could get free elsewhere. Skip it if you need the tools you already own connected rather than data you do not, which is Composio’s job and not this one. And skip it if you are building a product on top of it that you intend to sell as a service, because the licence says no and you should read it before, not after.

Best Treg alternatives

Composio is the general tool and auth layer for agents, covering 1,000-plus toolkits with OAuth handled for you. Free gives 100,000 tool calls and 50,000 trigger events a month, Pro is $29 a month including $29 of usage credit, and overage is $0.0003 per tool call. Composio connects the apps you already have accounts for. Treg sells you access to ones you do not. Most teams doing serious agent work end up needing both.

Arcade.dev is the tightest comparison on the auth story specifically, with a runtime built around agents acting as an authorised user. Free covers 2,000 auth events and 2,000 tool calls monthly, Team is $25 a month plus $0.10 per auth event and $0.01 per tool call, and Enterprise adds VPC or air-gapped deployment. It is more expensive per operation than Composio and more focused on doing things correctly on a user’s behalf.

DataForSEO is the honest alternative for the SEO half of Treg’s catalog: buy the data directly, pay as you go, no seat. The minimum payment is $50, which is the trade. You get a direct billing relationship and no gateway in the path, and you give up the unified key, the cross-provider comparison, and the ability to switch vendors without changing code.

Final verdict: is Treg worth it?

The core idea is right and the pricing is close to unarguable. Selling fractions of a cent of Semrush to an agent that needs forty calls a month is a service that should exist, and doing it behind one revocable token with the option to swap in your own keys is the correct shape for it. The catalog’s admissions column is better documentation of what is actually possible in SEO and social data than most vendors publish anywhere. At five weeks old with 459 stars, this is one of the more useful things to come off a leaderboard this month.

Two things need fixing and neither is hard. Publish a pricing page with a top-up ladder, because per-call transparency that you have to reconstruct from a catalog is not transparency. And change the open-source badge to match the licence, because “AGPL” on the homepage and a hosted-service restriction in the LICENSE file is the kind of mismatch that costs a company far more trust than the restriction itself ever would. Fix those and this is an easy recommendation. As it stands, use it, self-host it if you want, and read the licence before you build a business on it.