Agents don't care about vendors - they want the best API for the task. treg gives your agent 2,600+ tools (SEO, social, leads, ads, scraping) behind one URL and one token. Search by task, see price/request/response, pay per call at 0% markup. Open source.
We started Treg as our internal tool, out of a simple frustration: the data & system an agent needs for real work - keyword volume, backlinks, ad libraries, enrichment - either sits inside SaaS bundles priced for humans. $139/mo, and you don't even know what's in the box OR requires days of OAuth app setup & verification.
Instead we think future should be task-based instead of vendor-based - agent just ask the task, it knows all endpoints with request/response/price, decide the best API for the task - and to pay for the result.
So: • 2,600 agent-friendly tools across ~40 providers: SEO/GEO, social, leads, ads, scraping • Search by task ("backlinks for a domain"), see price / request / response, call it • Pay per call, no subscriptions - 0% markup. Same unit price as the subscription; BYOK if you already pay and those calls are never metered • It also handles the painful OAuth setups (Google/Meta ads, social posting, Business Profile) - connect once, every teammate's agent can act • The proxy relays the real upstream request and injects credentials server-side - your agent never holds a secret, and we never model the upstream API, so we survive provider changes
Open source (AGPL), self-hostable.
Tell me what your agent does with it - and what's missing from the catalog. I'm here all day.
About Treg on Product Hunt
“OpenRouter for tools with 2,600 APIs, 0% markup”
Treg launched on Product Hunt on August 17th, 2026 and earned 96 upvotes and 2 comments, placing #10 on the daily leaderboard. Agents don't care about vendors - they want the best API for the task. treg gives your agent 2,600+ tools (SEO, social, leads, ads, scraping) behind one URL and one token. Search by task, see price/request/response, pay per call at 0% markup. Open source.
On the analytics side, Treg competes within API, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how Treg performed against the three products that launched closest to it on the same day.
Who hunted Treg?
Treg was hunted by Jason Zhou. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Treg including community comment highlights and product details, visit the product overview.
Jason Zhou
Hey Product Hunt 👋 Jason here
We started Treg as our internal tool, out of a simple frustration: the data & system an agent needs for real work - keyword volume, backlinks, ad libraries, enrichment - either sits inside SaaS bundles priced for humans. $139/mo, and you don't even know what's in the box OR requires days of OAuth app setup & verification.
Instead we think future should be task-based instead of vendor-based - agent just ask the task, it knows all endpoints with request/response/price, decide the best API for the task - and to pay for the result.
So:
• 2,600 agent-friendly tools across ~40 providers: SEO/GEO, social, leads, ads, scraping
• Search by task ("backlinks for a domain"), see price / request / response, call it
• Pay per call, no subscriptions - 0% markup. Same unit price as the subscription; BYOK if you already pay and those calls are never metered
• It also handles the painful OAuth setups (Google/Meta ads, social posting, Business Profile) - connect once, every teammate's agent can act
• The proxy relays the real upstream request and injects credentials server-side - your agent never holds a secret, and we never model the upstream API, so we survive provider changes
Open source (AGPL), self-hostable.
Tell me what your agent does with it - and what's missing from the catalog. I'm here all day.