superdesigndev/treg

Treg is best understood as a metered reseller layer between agents and paid data APIs, not as a drop-in replacement for direct provider accounts. It is worth trying for prototyping and internal tooling where avoiding a $99–$139 monthly subscription matters more than contractual certainty.

The problem

An agent that needs backlink data, a person's work email, or a TikTok profile usually hits the same wall: the data sits behind a vendor subscription, a signup flow, or an invite-only API. The user either buys a monthly seat for a one-off run or abandons the task. Treg changes the middle step: the agent searches a catalog by job description ("find a work email"), reads the per-call price, and calls the endpoint with a single registry token. The result is a metered call instead of a new vendor relationship.

What's different

Treg carries provider accounts itself and bills fractions of a cent per call, with anonymous free calls for endpoints that have a verified public route. A second mode registers your own keys, OAuth connections, vendor CLIs, and SKILL.md files so every teammate's agent can call them without holding the credential; own-key calls win over Treg's and are not metered. Sharing is deliberately low-friction: treg scan previews what treg upload would register from .env files, skills, and installed CLIs, encrypted server-side. The README is explicit that these are two different products sharing a token, and the distinction matters, since only the catalog carries the legal and availability questions.

The trade-off is that reselling access is the core mechanism, not an incidental detail. A commenter on the launch thread raised the provider contract question directly, saying the terms of those providers do not legally permit this, and another asked why; the reply chain does not resolve it comment. Treat the catalog as convenient and the provider terms as unverified by this review. Another commenter asked whether the site will stay up because providers may object comment, and the implementation of x402 payment support referenced by a third commenter comment is not confirmed in the supplied README excerpts.

Who should try it

Good fit: a developer prototyping an agent that needs several heterogeneous data sources, who wants to test the workflow in an afternoon before committing to vendor contracts. Also a team that wants internal keys usable by every agent without copying secrets around, since the self-registered tools path is independent of the catalog's disputes. Poor fit: anyone shipping a product that depends on a specific data vendor's uptime and terms, or anyone who needs contractual clarity before building. If the dashboard matters, one commenter described the hosted site as heavy and unlike OpenRouter comment; the self-hosted path avoids that UI but shifts operational work onto you.

Requirements and limitations

Setup is a CLI install from a shell script, then GitHub login or an email code, with a token option for agents and CI install. There are three documented on-ramps: the treg CLI, a Claude Code plugin that installs without a token, and an npx skills add path for other agents Claude plugin docs; a Claude.ai connector at a separate MCP surface exposes only curated non-generative endpoints connector. Ongoing upkeep includes prepaid balance, per-call pricing checks via treg catalog get, encrypted credential storage, and provider terms that may change. License is Apache 2.0 with an added restriction on redistributing the code as a competing hosted registry license.

HotRepo's take

HotRepo recorded 2,054 stars on 2026-09-22 and 6,332 on 2026-10-27, with five daily-board appearances in a 103-day-old repository; the samples are too sparse to judge trend direction. Before adopting, verify one thing the README does not settle: whether the specific provider you need permits resold access under its terms.