Treg

Treg

Open-source API gateway giving AI agents access to 2,800+ endpoints across 57 providers through one key, with transparent per-call pricing and zero markup.

🔗 Visit Treg
📁 AI & Machine Learning🗣️ English📅 August 22, 2026

Description

Building an AI agent that needs to check SEO rankings, post an ad, or pull CRM data usually means signing up for a dozen different services, each with its own API key and billing. Treg collapses that into one login: agents call Treg, and Treg routes the request to whichever provider actually handles it.

Treg is an open-source, AGPL-licensed API aggregation gateway that unifies 2,800+ endpoints across 57+ providers — including Google, Meta, TikTok, and Semrush — behind a single authentication key. It bills per call at the provider's actual rate with zero markup (for example, $0.006 per Semrush keyword call), gives new users $1 of free credit, and also supports bringing your own API keys for providers you already subscribe to. It has 567 GitHub stars and is community-driven, with new tool integrations added by contributors.

💬 Our review

The short version: if you're building AI agents that need to touch a lot of different marketing, sales, or SEO APIs, Treg's single-key, zero-markup model is a genuinely useful shortcut — but you're trusting a young, community-run project to keep 57+ third-party integrations working.

The 'OpenRouter for tools' framing is accurate and useful: OpenRouter solved the problem of juggling multiple AI model providers behind one API, and Treg is doing the same thing for task APIs (marketing, SEO, sales, data enrichment). Zero markup on provider rates is a meaningful commitment — most aggregators add a margin, and Treg's transparency here (you see the exact per-call cost, like $0.006 for a Semrush call) is unusual and developer-friendly. The real risk is operational: managing 57+ third-party integrations means Treg's reliability is only as good as its weakest upstream provider, and with 567 GitHub stars this is still a small, young open-source project rather than an established piece of infrastructure. Best fit: developers building AI agents for marketing, sales, or SEO workflows who want to avoid managing a dozen separate API subscriptions. Weaker fit: teams needing guaranteed uptime SLAs or enterprise support — this is a community project, not a vendor with support contracts.

💰 Pricing

Pay-per-useTarif par appel selon fournisseur, 0% de marge, 1$ de crédit gratuit.
Pay-per-use variable selon fournisseur

📊 Global score

53Average
🌐Availability15/100Faible

1 language · 0 platform

📄Profile90/100Excellent

Profile completeness

🤖 AI-enriched data

💰 Pricing model
💳 Pay-per-use (paiement à l'appel)

Tarif par appel selon le fournisseur (ex. 0,006 $ par appel Semrush), 0% de marge. 1 $ de crédit gratuit au démarrage. Option bring-your-own-key pour utiliser des abonnements existants.

👥 Target audienceDéveloppeurs IA et agents construits pour le marketing, la vente, le SEO et l'enrichissement de données
🗣️ Languagesen
🌍 Target countriesMarché anglophone / mondial
👍

Pros

Catalogue massif : 2 800+ endpoints sur 57 fournisseurs

Tarification transparente à l'appel, 0% de marge

100% open source (AGPL), ajouts communautaires

Authentification unifiée (une seule clé)

Option bring-your-own-key

👎

Cons

Communauté encore petite (567 stars)

Dépend de la stabilité des APIs des fournisseurs en amont

Complexité opérationnelle de gérer 57+ intégrations

Documentation et support encore limités

❓ Frequently asked questions

What is Treg in one sentence?
How much does Treg cost?
Is Treg open source?
Can I use my own API keys?
What kind of APIs does Treg cover?
Is it worth the money compared to alternatives?
Which tool should you pick for your case?